|
#1
|
|||
|
|||
|
If I have to run SCANDISK during boot up I get the following message:
"You may need to remark some device drivers from your config.sys file. Or in your config.sys you may need to load the EMM386 driver to load your other device drivers into Upper Memory Blocks using DEVICE HIGH= Statements." I have an entry in the SYSTEM.INI in SYSEDIT added to the 386Enh as follows: "LoadLocalHigh=1" This doesn't seem to be doing the trick for the error message for SCANDISK (in DOS) during bootup. Don't seem to be finding any troubleshooting suggestions that I "can follow" in GOOGLE. Can anybody relate to this issue? Your assistance is gratefully requested. Thanks!
__________________
There is no "TRY".....only "DO". |
|
#2
|
||||
|
||||
|
Hi jayro...locate config.sys in C:, then open it in NotePad (just click on the file and you will be given a program list). Edit > Select All > Edit > Copy, then right-click/paste in your reply.
<Second thoughts> Actually, the LoadLocalHigh=1 line in system.ini is likely the problem. From another site: Quote:
Post the contents of config.sys anyway.
__________________
Sign the ONE Declaration |
|
#3
|
|||
|
|||
|
Hi *.Ed, (LOL)
Thanks for your response. Firstly... doing a "Find/Files or Folders" in C: for config.sys, I got four (4) returned folders, as follows: 1. C:\WINDOWS\TEMP - Modified Aug 03/02, contents as follows: DEVICE=HIMEM.SYS DOS=HIGH,UMB BREAK=ON FILES=30 BUFFERS=5 2. C:\UNZIPPED\WINDOWS SYSTEM SETTINGS - Modified July 21/02, contents as follows: REM DEVICE=C:\SAMSUNG\SSCDROM.SYS /D:SSCD000 /v REM device=c:\samsung\sscdrom.sys /d:cd001 DEVICE=C:\SAMSUNG\SSCDROM.SYS /D:SSCD000 /v 3. C:\ - Modified July 21/02, contents as follows: REM DEVICE=C:\SAMSUNG\SSCDROM.SYS /D:SSCD000 /v REM device=c:\samsung\sscdrom.sys /d:cd001 DEVICE=C:\SAMSUNG\SSCDROM.SYS /D:SSCD000 /v 4. C:\PROGRAM FILES\RESCUE DISK - Modified Aug. 23/00, contents as follows: device=ifshlp.sys I don't know if it's normal to have multiple config.sys files but that's what I found. The first being a ".temp", I wouldn't expect it to be to important but haven't deleted it yet. The second being an "unzipped" file strikes me as odd, but what do I know really. The third one, seems most likely to be relevant based on your request to copy and paste the C:\config.sys file, but again, what do I know, really. LOL The fourth one...... I didn't even own this computer in Aug of 2000. I bought it used in Dec of 2000 from my employer. Somewhere in what I've pasted here I do hope is what you were asking for. Secondly, as for adding REM and a space before the line LoadLocalHigh=1 so as to make it read as follows: REM LoadLocalHigh=1 in the 386Enh, SYSTEM.INI file, I have done that and I'm about to reboot. I'll post the result momentarily........ brb
__________________
There is no "TRY".....only "DO". |
|
#4
|
|||
|
|||
|
HkEd
Well........ I'm back. Added REM to the 386Enh, SYSTEM.INI file & no difference. BTW, the message I originally entered as the SUBJECT in my original request for assistance post, appears during any improper shutdown of windows (resulting in a SCANDISK, which can't be completed) as well as a proper shutdown/startup or shutdown/restart. Your further thoughts? Thanks!
__________________
There is no "TRY".....only "DO". |
|
#5
|
||||
|
||||
|
Well, jayro...I'm a little stumped. What the heck is config.sys doing in the Temp folder? I'd do a virus check ASAP. You never know.
Config.sys should be in C:, and it typically should look like this: Code:
device=C:\WINDOWS\Himem.sys DOS=High,UMB device=C:\WINDOWS\EMM386.EXE This sounds to me like you need to have me (or any of the other helpers here) sitting in front of your screen (BTW, I only travel 1st Class )
__________________
Sign the ONE Declaration |
|
#6
|
||||
|
||||
|
<Further thoughts> Scandisk on improper shutdown can be disabled, but I can't for the life of me remember which file it's in ( msdos.sys?...scandisk.ini?). Sorry...it's late here in Hong Kong. Time to slump in front of the TV and get bombarded by soporific subliminal messages. I'll check in again in the morning....zzzzzzzzzz </Further thoughts>
__________________
Sign the ONE Declaration Last edited by HKEd; August 5th, 2002 at 02:58 PM. |
|
#7
|
||||
|
||||
|
Hi
can you also post content of C:\autoexec.bat ? you can repost content of C:\config.sys as well. (it gets drowned in the others) the way I see this, HKed is right C:\config.sys misses lines you should have
__________________
Kind regards, Jaak.Setup methods for Windows, NT, DOS and XP. FAQ Site Help Forum Rules |
|
#8
|
|||
|
|||
|
Hey!
HKEd.... Hey ! Jaak...... Ok.... 1. Copied and pasted that text to NotePad and saved to "All Files Config.sys" in C:\ 2. The search for config.sys in C: returns the following: REM DEVICE=C:\SAMSUNG\SSCDROM.SYS /D:SSCD000 /v REM device=c:\samsung\sscdrom.sys /d:cd001 DEVICE=C:\SAMSUNG\SSCDROM.SYS /D:SSCD000 /v 3. The search for autoexec.bat in C: returns the following: SET CTCM=C:\WINDOWS SET SOUND=C:\PROGRA~1\CREATIVE\CTSND SET MIDI=SYNTH:1 MAP:E SET BLASTER=A220 I5 D1 H1 P330 T6 rem - By Windows Setup - c:\windows\command\mscdex.exe /d:cd001 C:\SAMSUNG\MSCDEX /D:SSCD000 SET PATH=C:\PROGRA~1\SAPP;%PATH% BTW, my search for autoexec.bat returns multiple files as well. Five (5) in total. One of which is the above information. I hope this provides the requested information and that it helps the situation. Thanks again.
__________________
There is no "TRY".....only "DO". |
|
#9
|
||||
|
||||
|
hi
small wonder you have that issue it looks like a leftover for a cdromdriver and sound installer (sometimes done by DOS based games...) and the installer that did it, did it more than once, make your new config.sys look like this [C:\config.sys] device=C:\windows\command\himem.sys device=C:\windows\emm386.exe NOEMS files=60 buffers=20 dos=high,umb stacks=9,256 lastdrive=z REM DEVICE=C:\SAMSUNG\SSCDROM.SYS /D:SSCD000 /v =================== [C:\autoexec.bat] SET PATH=C:\;C:\windows\command\;C:\PROGRA~1\SAPP;%PAT H% SET CTCM=C:\WINDOWS SET SOUND=C:\PROGRA~1\CREATIVE\CTSND SET MIDI=SYNTH:1 MAP:E SET BLASTER=A220 I5 D1 H1 P330 T6 REM C:\SAMSUNG\MSCDEX /D:SSCD000 ========= and if that don't fix it (scandisk ought to finish now) well, the entry for scandisk is in msdos.sys which is a hidden and read only system file I think it's better to let scandisk finish the job at least once. (edited the path to include windows command in path... which is gonna be easier later on)
__________________
Kind regards, Jaak.Setup methods for Windows, NT, DOS and XP. FAQ Site Help Forum Rules Last edited by jtdoom; August 5th, 2002 at 08:20 PM. |
|
#10
|
|||
|
|||
|
Ok jt....got your latest post, thanks.
I copied and pasted the information you provided to my config.sys and autoexec.bat files and they now read as per the text that was provided. Nothing more, nothing less. The original problem is no longer happening (about SCANDISK and there not being enough conventional memory), but...... ....... now, when I am booting up, the DOS screen(s) that appear during this process state as follows: 1. The following file is missing or corrupt. C:\WINDOWS\COMMAND\HIMEM\SYS There is an error in config.sys line 1 2 Windows Expanded Memory Version 4.95 3. EMM386 is not installed XMS Manager is not present. Press any key to continue...... C:\>SET PATH=C:\;C:\WINDOWS\COMMAND;C:\PROGRA~1 SAPP;%PAT C:\>H% Bad Command or File Name At this point there are some more " C:\ " entries and the machine proceeds to finish the boot up and make it to the desktop and everything seems to be ok, as far as I can tell, but I haven't worked much with the machine in this state so who knows for sure yet. Right? Now what?
__________________
There is no "TRY".....only "DO". Last edited by jayro; August 6th, 2002 at 08:36 AM. |
|
#11
|
|||
|
|||
|
Not that it made any difference but I noticed the reason I was seeing the "C:\>H% Bad Command or File Name" line while the DOS screen(s) were appearing during boot up. When I copied and pasted the text you mentioned in your last post, the "H%" from "%PATH%" auto scrolled onto it's own separate line (in your post) and ended up in my autoexec.bat file that way too. I have since corrected the autoexec.bat file accordingly. I still get all the error messages mentioned but the "C:\>H% Bad Command or File Name" message line doesn't appear any longer. WooHoo..... LOL
__________________
There is no "TRY".....only "DO". Last edited by jayro; August 6th, 2002 at 07:29 AM. |
|
#12
|
|||
|
|||
|
You have a typo in your CONFIG.SYS file. The line should be:
DEVICE=C:\WINDOWS\COMMAND\HIMEM.SYS just like jtdoom layed it out for you - you're providing directions (the path) for the file you wish to equate to a DEVICE. HIMEM.SYS is a device driver that is used to manage extended memory on your system. The EMM386.EXE won't load without it. This routine is also a device driver and is used to simulate Expanded Memory or to provide access to the Upper Memory Area. The NOEMS switch is used to identify that you don't want any Expanded Memory. Use Notepad & ensure that the file looks EXACTLY as given to you by jtdoom. |
|
#13
|
|||
|
|||
|
Thanks for your keen observation Alphons,
However, that was a typo on my part. A direct copy and past from my config.sys for that line is as follows: device=C:\windows\command\himem.sys My post that showed it as "device=C:\windows\command\himem\sys" was just a typo. Oops! The rest of your post was above my head though. I don't grasp your explanation on terms that mean anything for me. :-s
__________________
There is no "TRY".....only "DO". |
|
#14
|
|||
|
|||
|
Jayro, are you still getting an error relating to that line in CONFIG.SYS? If yes, have you checked in the C:\WINDOWS\COMMAND directory to see if you've got HIMEM.SYS there? If it's not there, do a search to find where it is - you seem to have a mixup in your file locations for some reason.
|
|
#15
|
|||
|
|||
|
Thanks again Alphons for the reply :-)
I still get the error message when booting up that says: "The following file is missing or corrupt: C:\WINDOWS\COMMAND\HIMEM.SYS There is an error in config.sys LINE 1 Is that what you were asking? I think so. I checked for the himem.sys file in C:\WINDOWS\COMMAND and it isn't there. I searched for himem.sys and it located here in C:\WINDOWS There are many "folders" in C:\WINDOWS and after the last folder listed there are many files there too, that are not in a folder. One of these "many files" in the WINDOWS folder is himem.sys. Am I assuming correctly that is shouldn't be a file in the WINDOWS folder but rather a file in the C:\WINDOWS\COMMAND folder instead? thanks again!
__________________
There is no "TRY".....only "DO". |
![]() |
| Bookmarks |
«
Previous Topic
|
Next Topic
»
| Topic Tools | |
|
|
All times are GMT +1. The time now is 08:00 PM.
[
RSS ]




)
Kind regards, 



