I thought of that possibility, but I had fixed one once before. I'm not
sure but I think scandiskw.exe was damaged along with some other system
file. I just wanted some ideas.
Thanks
> I thought of that possibility, but I had fixed one once before. I'm not
> sure but I think scandiskw.exe was damaged along with some other system
> file. I just wanted some ideas.
Actually if it is the DOS scandisk that is running when the computer starts
(the one with the blue screen) that has nothing to do with scandiskw.exe.
Make sure there is nothing in the Autoexec.bat file asking Scandisk to run.
Wayne A Lewis - 06 Feb 2004 05:25 GMT
Yes, I meant scandisk.exe, and it would be enabled in msdos.sys under
AutoScan. (=1 is on, =0 is off)
Thanks
> x-no-archive: yes
>
[quoted text clipped - 5 lines]
> (the one with the blue screen) that has nothing to do with scandiskw.exe.
> Make sure there is nothing in the Autoexec.bat file asking Scandisk to run.
Haggis - 06 Feb 2004 12:13 GMT
if you want to turn that off ..edit msdos.sys and set "autoscan=0"
> x-no-archive: yes
>
[quoted text clipped - 5 lines]
> (the one with the blue screen) that has nothing to do with scandiskw.exe.
> Make sure there is nothing in the Autoexec.bat file asking Scandisk to run.