🚀 go-pugleaf

In article <1992Oct26.153117.13818@cs.utwente.nl>, ahoekstr@cs.utwente.nl
(Andre D. Hoekstra) writes:
> In article <m637sB3w165w@mindvox.phantom.com> ricky@mindvox.phantom.com
(Richard Velez) writes:
>>dbasinge@bronze.ucs.indiana.edu (Mike Basinger) writes:
>>> I just upgraded a machine from MS-Dos 4.01 to MS-Dos 5.0, everything
>>> work fine except chkdsk. Whne I try to use chkdsk, I get the following
>>> error.
>>> 
>>> Incorrect DOS Version  
>>> What causes this problem.
>> 
>>its possible that you still have the system files from 4.01 on disk, that 
>>same thing happened to me, what I did was reformat my whole system ( at 
>>the time I didnt have nothing in there ) the system files are hidden from 
>>all the other files. Hope this help, I'm not really a smart person with 
>>companys but I learn from my mistake.. :), later
> 
> While you said everything works fine BUT chkdsk, probably your old
> chkdsk is left on the disk (not overwritten by the 5.0 one?)
> The proper way to upgrade from 4.01 to 5.0 is to use the Install program
> on your upgrade disks. reformatting is a bit crude.

Agreed !

> If you don't have install (not a legal copy?) you can boot from a 5.0
> (floppy)disk and issue the sys command:
> sys c:
> which then will copy two hidden files (IO.SYS and MSDOS.SYS or IBMBIO.SYS
> and IBMDOS.SYS or something like that) and COMMAND.COM to your C: drive.
> Now copy all your 5.0 stuff to a subdir (DOS5, say) and amend CONFIG.SYS and
> AUTOEXEC.BAT to fit your needs.
> From that point on you can boot from C: 

But this isn't the problem he was trying to solve -- I suspect that the
DOS 4 CHKDSK is still lurking earlier in his path than the DOS 5.0 one
--OR-- the DOS 4 CHKDSK was/is a .COM and the DOS 5.0 one is a .EXE. 
DOS normally executes .COM's ahead of .EXE's, so if my -guess- is right,
the DOS 4 CHKDSK could even be in the same dir as the DOS 5.0 one. 
(Sorry, I don't have easy access to a DOS 4.x system to check this.)

Use the "dir /s chkdsk.*" command from the root dir of your HD to find
where all copies of any CHKDSK executable are, suss out from your PATH
variable setting, and the fact that .COM's are fired up in preference to
.EXE's, which is being executed and delete that one.

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 Nick FitzGerald, PC Applications Consultant, CSC, Uni of Canterbury, N.Z.
 n.fitzgerald@csc.canterbury.ac.nz  (64)(3)  364-2337 Voice,  364-2332 FAX