MS DOS booted from Hard drive does not execute any .exe file even from outside

[strollin]

In an earlier post you reported that the machine had 128M of installed RAM.

If you have multiple sticks of RAM that makeup the total whether it is 128M or 512M you could try to remove 1 or more sticks to reduce memory. DOS can't use anything above 1M, not sure if Foxpro can use the extended memory or not.

[strollin]

Originally Posted by logamuthu Hi Strollin, Intel Live chat told me " I apologize but this motherboard has reached its End of Interactive Support and in the other hand MS-DOS is not longer supported ". QUE VE LA?!

Just means you are on your own with regards to support. That's one reason sites like PC Mech exist.

[glc]

I'm sorry - by "pull" I meant reduce the amount of ram. If it's a single 512mb module, don't bother.

Strollin, the 128mb figure was for the dead HP Brio that the hard drive came from.

I just looked it up - MS-DOS 6.x can access up to 64mb ram. Of course, this requires an extended or expanded memory manager be used, which it is in this case. That explains why DOS was only reporting 64mb in that Brio with 128mb installed.

[edfair]

Although you've reloaded DOS, you probably haven't touched the boot stuff. That would require fdisk and remove partition then fdisk and add it back in followed by format and load of the OS.

You could also change the attributes of IOSYS, msdos.sys, and command.com on both floppy and hard and on the next floppy boot compare the files between the drives.

Something is suspicious if it booted correctly once and not again. Seems like something may run after boot to corrupt command.com