Name: dboy Date: March 6, 2005 at 15:22:43 Pacific Subject: Hard Drive Transplant OS: DOS 7.10 CPU/Ram: 66 Mhz/7808 Kb
Comment:
hi, On my really old computer, me and my brother have desperately been tyying to install Windows 3.11. I think I finally know how to do it. I can do a hard drive transplant. this is what I mean:
1)Format the hard drive on computer 1(the computer I'm trying to install windows 3.11 on)(I'm not quite sure if that's nesescary.) 2)Put it in computer 2(another computer which I use for expirements). 3)Install on C2 4)Take out hard drive And put it back in C1.
If anyone knows if this can cause an error, please tell me before I possibly ruin my computer forever(but not quiiiiiiiiite forever) thanks
There are 3 types of people in this world, those who can count and those who can't.
Normally you would boot with a DOS diskette, FDISK the drive to create a Primary Partition if necessary and make it Active. Then you would reboot and run FORMAT C: /S to format the drive and install the boot files for DOS.
Then you would install at least a minimal set of DOS files, including the WINA20.386 module in the root directory. And then boot from the disk drive to the DOS C:\ prompt.
From there, you would run the SETUP program on the first Windows 3.11 install diskette, disk drive directory, network drive, or CD. The Setup program would then prompt you through the install of the Windows 3.11 files.
Windows 3.11 requires DOS to be installed first. However, I have no idea if it will install and run with DOS 7.10 which is really the WinDOS from Windows 9x.
Well for anyone wondering, these are the specs of Computer 2:
500 mhz Windows 95 16 mb RAM 15 gb hard drive And just to amaze you people who think your computer is slow, it takes 2 Minutes, 23 Seconds to boot up. A New Record!!! (whereas my even older computer only 66mhz loads in 30 seconds on average)
The hard drive already has a perfectly working DOS 7.10 OS. I think this would work unless Windows Setup reads specific files from ROM.
I'm sorry for those of you who are confused.
There are 3 types of people in this world, those who can count and those who can't.
Yes it's possible, no it won't damage anything, "unless you zap it with static electricity" and yes you may get errors as the install would be for the hardware of the computer in which you installed dos and windows. Yet dos & 3.11 isn't as picky as 95&98 and should still boot.
Sounds like you need to hunt down msconfig, and winMEdefrag for that old 95 computer and do some registery cleaning too.
16mb of ram? lol I'd up it to 32 or even 64mb.
I have a old p2 333mhz w/128mb ram and 7gig hd. Windows 95 almost boots faster then the monitor takes to warm up! lol.
ASUS A7V8X AMD XP 2700+ 2.17ghz 768mb ddr 2700 nVidia 128mb FX 5200 WD 80gb SE DVD R/RW
I concur with name's assessment as to the 'real' question.
We often see posts where the OP has devised some convoluted scheme in order to achieve some vaguely stated goal. These are usually doomed to failure and are typically a huge waste of time - not much gets accomplished until the true problem is stated (as opposed to the OP's interpretation of the problem).
As long as your drives are set up in your BIOS, reponse #3 outlines all you should need to do to get Win 3.1 installed on that machine. There is no reason whatsoever (based upon what you've outlined) to remove the drive and put it in another machine.
Y'know, your attitude here leaves much to be desired.
Members are under no obligation whatsoever to answer anyone's questions - we're volunteers.
Ordering folks around is pretty much a guarantee that you won't get help. You're wasting everyone's time and causing aggravation. If you don't modify this behaviour, the webmaster will be brought into the picture, and he will deal with you accordingly.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE