Solved Boot with an MS-DOS drive

January 25, 2015 at 04:56:31
Specs: Windows 7, i7 2600/24 GB Quad
Hi There,
I had an old laptop with a "valuable" MS-DOS system installed on it.
Years back I cloned this and was able to boot it in a 32bit PC without problem.
I now have a 64Bit machine and when I try to boot to the drive I get the usual "Starting MS-DOS" then the usual "HIMEN is testing extended memory.....done" but then it hangs there without booting up.
Put the disk back in a 32bit machine and it works great.
I'm sure I have had this working before on my 64 bit machine and I think I did something, who knows. I recall some time ago going into the BIOS to check some performance settings but I don't think I did much really.
The BIOS is American Megatrends Inc 0502, 31.8.11. SMBIOS version 2.6,
Any help would be much appreciated.
Regards
Paul


See More: Boot with an MS-DOS drive

Report •

#1
January 25, 2015 at 08:19:13
http://thpc.info/dual/7/db_ms-dos62...

Note the part stating "...MS-DOS 6.22 device drivers are not available for 64-bit hardware devices so expect those devices not to work on 64-bit computers when DOS 6.22 is running."

Likely that's why it's hanging after the HIMEM.SYS file.

If the drive is valuable, best to install it on something with 16/32 bit hardware (and make an image of it in case something happens to the drive later).

"Channeling the spirit of jboy..."

message edited by T-R-A


Report •

#2
January 25, 2015 at 09:36:26
✔ Best Answer
Make an image of your DOS hard disk using WinImage Professional (shareware with a limited free trial) then run DOS inside a virtual machine booting from the vhd image created. MS Virtual PC or VirtualBox are both free and very effective in running under the most up to date operating systems and 64 bit hardware.

Report •

#3
January 25, 2015 at 14:39:06
Thanks for that TRA and yes I have put it into an old 32bit machine but it's not networked etc and eventually it will fail I guess.
Yes, I have two cloned drives of it as well as the original laptop drive, as well as an image! Backup on backup on backup!
Im not sure im up to that dual boot though lol.
I'll review further, IVO's solution seems like an easier option.
Cheers

Report •

Related Solutions

#4
January 25, 2015 at 14:40:20
Thanks for that IVO and I think I will give that a go when I get a few hours spare.
One question though, it's the whole drive that I have to run I think as the program i was using on the disk is embedded within the operating system if you know what I mean. I recall that it was written this way so that the program ran in a controlled environment and the individual programs not stripped away from the computer. Does that make sense?
Maybe it works as long as the igave is run via the solution you have suggested I don't know.
I know enough to be dangerous!
Cheers

message edited by buster953


Report •

#5
January 25, 2015 at 20:29:34
Hit CTRL C when you get the 'himem is testing. . . '. I think you can exit config.sys (which called himem.sys) by doing that.

Also, when it's connected to the 32 bit machine you can rename config.sys and autoexec.bat to something else so they don't load. Then on the 64 bit machine they won't run and cause any problems.

Edit Just read your # 4. It wouldn't be 'embedded' in dos but the original installation of the program may have modified config.sys and autoexec.bat so don't delete them. Just rename them and then see if it boots and if so, see if the program runs.

Are you sure you need to run the program in order to recover whatever files you're looking for?

message edited by DAVEINCAPS


Report •

#6
January 25, 2015 at 22:13:46
HI Dave,
Thanks for the advice and I'll try the CTRL C at start up and see where that gets me.
I'm very reluctant to rename the config.sys and autoexec.bat to something else so they don't load as I might stuff things up!
I don't need to recover files off the old drive, I want to run the software on it.
Cheers

Report •

#7
January 25, 2015 at 23:01:24
Hi Dave,
The CTRL C didn't work so I'll try MS Virtual PC or VirtualBox next I think.
Cheers

Report •

#8
January 25, 2015 at 23:10:31
Hi IVO,
OK I have an a VHD image but it seems that my machine is not hardware-assisted virtualization is not enabled. I'll search online for a solution but maybe you know how to solve that one?
Cheers

Report •

#9
January 25, 2015 at 23:57:17
Guys,
I have solved my problem thanks to IVO!
I created a VHD image, allowed virtualization in the BIOS, loaded VirtualBox which then did it's thing and now I can operate the old disk this way.
Thanks for all your help guys, especially IVO.
Cheers
Paul

Report •

#10
January 27, 2015 at 03:01:05
Guys,
Sadly I spoke too soon!
The program ran a couple of times successfully then I think I did something to it, maybe a screen dump but not sure and now it fails to start up with the following errors:
- Error In SupR3HardenedWinRe Spawn
- Error relaunching VirtualBox VM Process: 5
- Failed to open a session for the virtual machine BEANS.
- The virtual machine 'BEANS' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Paul\VirtualBox VMs\BEANS\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

I have also just loaded Windows Virtual PC and that worked fine until I went and attached the VHD in computer management so that I could read output files on the VHD. I think I did the same with VirtualBox.
Does this help?

Any advice please?
Thanks

message edited by buster953


Report •

Ask Question