Computer Hope

Microsoft => Microsoft Windows => Windows Vista and 7 => Topic started by: php111 on August 15, 2011, 09:20:18 AM

Title: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 15, 2011, 09:20:18 AM
Why did Windows 7 go on drive C when I specified it to go on drive D, and let DOS 6.22 go on drive C? I have DOS on, but it's not only on the wrong default drive, but I don't have a boot loader, so I can't see, access MS-DOS.

I also have another question. When I installed DOS, and it was successful. I have an LCD Monitor. It's not an older monitor. I can't see, or even look at the command responses. How can I fix everything? Thank you!
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 15, 2011, 09:42:08 AM
One question at a time.
Windows 7 goes on the partition you specify. Unlike Windows XP, it will  assign the drive letter to be C:. This is by design. It is an improvement. Some many applications insist on installing of the C: drive, so this lets them.
I just now did a install of Windows XP and had the hardest time getting the drivers right, The installer kept wanting g to put stuff o n C: while my XP was o n D:. Hard to double check everything and install by hand until it was right.

Here it is from the horse's mouth:
Why Windows-7 always install to Drive C: ? (http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/why-windows-7-always-install-to-drive-c/5bf22c97-061b-4ce7-bb1b-119e4f7173d6)

The article suggest that you could install 10 instances of Windows 7 on 10 partitions and each would be drive C:. Go figure.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Allan on August 15, 2011, 09:51:19 AM
Did you have anything plugged into a usb port when you installed Windows?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 15, 2011, 10:29:12 AM
I am trying it again.

How come I can't see the commands on an LCD screen? I remember when I did had an older screen there was no problems at all. Are there anyway to adjust the settings?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 15, 2011, 10:54:21 AM
It went on the different drives again. I tried everything.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Allan on August 15, 2011, 12:02:35 PM
Did you have anything plugged into a usb port when you installed Windows?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: patio on August 15, 2011, 02:42:18 PM
DOS has to reside on C:...however you need an earlier version of Windows installed on C: as well to prevent 7 from overwriting the C: partition...and having the boot option present and recognised by 7...Win2K is a good choice for a newer machine.
The other option would be to install DOS in VM and use it from there.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Computer_Commando on August 15, 2011, 03:19:56 PM
...The other option would be to install DOS in VM and use it from there.
That's how I do it.  Runs faster on Win7, than it ever ran native on any machine.
I use Virtual PC 2007, even though it's not supported on Win7-64.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Salmon Trout on August 15, 2011, 03:46:18 PM
That's how I do it.  Runs faster on Win7, than it ever ran native on any machine.
I use Virtual PC 2007, even though it's not supported on Win7-64.

I have MS-DOS 6.22 on VMWare Player on Win7 64
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 18, 2011, 04:48:17 AM


Thank you for all the replies.

No, I had nothing plugged into the USB ports.

I don't want to use VM. I don't have Win2k either. I prefer a dual of MS-DOS, and Win 7. Are there any other options let, or a work around this, so that Win 7 doesn't overwrite the MS-DOS partition?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: patio on August 18, 2011, 05:21:08 AM
Another physical HDD...
Unplug the DOS HDD when installing 7 to the 2nd HDD.
Then you can use the boot menu to choose which to boot to.

For the monitor you will need native DOS drivers for the vid card...
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 18, 2011, 05:35:15 AM
Another physical HDD...
Unplug the DOS HDD when installing 7 to the 2nd HDD.
Then you can use the boot menu to choose which to boot to.

For the monitor you will need native DOS drivers for the vid card...

I have two HDDs. One I don't use which is my external. I am technically trying to install DOS first, and then Win 7 as a dual boot all on my one internal HDD. Win 7 is keep overwriting drive C.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: patio on August 18, 2011, 05:51:12 AM
The 2nd drive would need to be an internal HDD.

Or you could use System Commander...not Free though.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 18, 2011, 06:17:56 AM
The 2nd drive would need to be an internal HDD.

Or you could use System Commander...not Free though.

I can't put both DOS, and Win 7 both on my internal HDD? That's how I use to do it with XP.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 18, 2011, 09:37:16 AM
I can't put both DOS, and Win 7 both on my internal HDD? That's how I use to do it with XP.
You got it. Vista and Windows 7 both use a new boot  scheme. You have to use a third-party boot manager to workaround this if you want DOS to see the first partition as its own boot partition.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 18, 2011, 09:44:14 AM
You got it. Vista and Windows 7 both use a new boot  scheme. You have to use a third-party boot manager to workaround this if you want DOS to see the first partition as its own boot partition.

So, let me get this right.

1. Install DOS first?

2. Install Windows 7?

3. Get a third party boot manager?

Is that what your saying to do that in that?

What would be the best, and free boot manager?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 18, 2011, 11:10:52 AM
Really, I have not done this myself.
Here is plan I am going to try just to see if it works. Using a plain 40 GB ATA drive, partition it it thus:

200 GB fat32 | 500 GB FAT16 | 38 GB NTFS| Rest unallocated
Use a partition maker like GPART or early version of EASUS.
Prepare a floppy drive with a fdisk program.
Set first partition active. Install a basic boot loader. Test it
Use floppy to set second partition active.
Install DOS 6.22 thee on the second partition.
Use disk again to swap active partition to see if it works.

Next eat third partition active. Install Windows 7 there.

Next install a partition manager that can switch the partitions. The first partition is a 'sacrificial lamb' used to satisfy Windows 7 appetite for messing the first partition.

I am still doing research on this. I am not sure if System Commander can do this.
Here are two references that are 'in the rough', but are a starting place.

http://en.wikipedia.org/wiki/Multi_boot

http://en.wikipedia.org/wiki/Ranish_Partition_Manager

EDIT:
Possible solution. http://www.plop.at/en/bootmanager.html
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 18, 2011, 01:08:27 PM
I am really confused. I thought that FAT 32 cannot exceed 32GB? I thought that FAT16 is WAY smaller? I am totally confused on how to get this done. Are there any step by step tutorials on dual booting MS-DOS with Win7?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Salmon Trout on August 18, 2011, 01:27:18 PM
I thought that FAT 32 cannot exceed 32GB?

The 32 GB limit is set by the Windows format tool. The actual limit set by the design of the FAT32 file system is 2TB with 512 bytes sector size. Using 3rd party tools you can format larger volumes than 32 GB. Just a few examples:

"Fat32 Format" (GUI)

http://www.pendriveapps.com/format-fat32-larger-than-32gb/

"FAT32format 1.05" (command line)

http://www.softpedia.com/get/System/Hard-Disk-Utils/FAT32format.shtml

"Fat32Formatter" (GUI)

http://tokiwa.qee.jp/EN/Fat32Formatter/



Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 18, 2011, 01:31:47 PM
I got that part. I'm not understanding the dual booting part on setting DOS so it could be visible. Are there any such tutorials on dual booting MS-DOS 6.22 with Win7?



The 32 GB limit is set by the Windows format tool. The actual limit set by the design of the FAT32 file system is 2TB with 512 bytes sector size. Using 3rd party tools you can format larger volumes than 32 GB. Just a few examples:

"Fat32 Format" (GUI)

http://www.pendriveapps.com/format-fat32-larger-than-32gb/

"FAT32format 1.05" (command line)

http://www.softpedia.com/get/System/Hard-Disk-Utils/FAT32format.shtml

"Fat32Formatter" (GUI)

http://tokiwa.qee.jp/EN/Fat32Formatter/
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 18, 2011, 05:09:30 PM
Could someone please post some tutorials for dual booting MS-DOS, and Win7? I tried searching Google, and couldn't find any. They were for something else.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Computer_Commando on August 18, 2011, 05:22:32 PM
...I don't want to use VM...
Why?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 18, 2011, 05:31:50 PM
Why?

I can't explain. I never got into VM. I tried it in the past, but I always done an uninstall. I prefer having a dual boot. That's my opinion.

Could you post a tutorial?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: patio on August 18, 2011, 07:36:15 PM
System Commander...
Worth every penny.

Probably cheaper to add another internal drive as i suggested though...
Up to you.

VM however as CC pointed out is a Free alternative.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 18, 2011, 08:41:15 PM
You can buy a recent version of System Commander for about $20 or even less.

There are a number of free boot managers. The issue is do any  work with Vista or Windows 7.
http://www.thefreecountry.com/utilities/multi-boot-managers.shtml

Tomorrow I am going to try and do it if I can. After I do my chores. Work before play.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: patio on August 18, 2011, 08:45:38 PM
System Commander does it...

Course if you are suggesting an older 20 dollar version i can't guarantee what latest OS versions will work on it.
He will have to research that...
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Computer_Commando on August 18, 2011, 09:20:24 PM
I can't explain. I never got into VM. I tried it in the past, but I always done an uninstall. I prefer having a dual boot. That's my opinion.
Could you post a tutorial?
I used to do the same, but couldn't get Windows 98, etc to boot with more than 1GB RAM.  I run DOS6.22/Win3.1 from an old 512MB Compact Flash Card, which I can move from machine to machine.  Install VM 2007, & set up the container (virtual hard drive) wherever you like, you can copy/move it later.  The VM provides a virtual BIOS, so it will run on any Windows hardware.
http://www.microsoft.com/download/en/details.aspx?id=4580
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: patio on August 18, 2011, 09:45:56 PM
Me personally i do not understand the reluctance to set it up in VM...
But that's just me/
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 19, 2011, 01:06:13 AM
System Commander does it...

Course if you are suggesting an older 20 dollar version i can't guarantee what latest OS versions will work on it.
He will have to research that...

What is System Commander?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 19, 2011, 02:26:08 AM
Patio,

Will you please make an exception by removing the post made by Jason over in the DOS section? It makes me not want to come here anymore. It had the techguy link in his reply. This is how I feel. If I'm posting on one forum then it should stay on that forum. Am I right or wrong? If you don't want to remove the whole post then can you edit the post, and remove the link? Thank you. I really like this forum.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Salmon Trout on August 19, 2011, 10:29:12 AM
I say Patio should leave it exactly as it is. You should learn that actions have consequences.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 19, 2011, 12:40:33 PM
System Commander does it...

Course if you are suggesting an older 20 dollar version i can't guarantee what latest OS versions will work on it.
He will have to research that...
I am working on it. I am slow, but I will keep at it.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 19, 2011, 02:06:43 PM
I am working on it. I am slow, but I will keep at it.

Are you trying it with a free boot loader such as Ranish?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 19, 2011, 02:13:48 PM
Yes, I am using free stuff first. I think I have something that works, but I have to prove it to myself first, then I will post it .

As a rule, if a boot manage and do both Vista and an old OS. then it will do Windows 7. But I want to make sure. These type of managers have to intercept the BIOS call to the MBR loader and use their own boot loader. Not endorsed by Microsoft.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 19, 2011, 02:21:57 PM
Yes, I am using free stuff first. I think I have something that works, but I have to prove it to myself first, then I will post it .

As a rule, if a boot manage and do both Vista and an old OS. then it will do Windows 7. But I want to make sure. These type of managers have to intercept the BIOS call to the MBR loader and use their own boot loader. Not endorsed by Microsoft.

Thank you for the info.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: BC_Programmer on August 19, 2011, 03:11:30 PM
http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/7e52b1b9-0e72-40ff-958c-e688427bfa94

Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: php111 on August 19, 2011, 03:27:32 PM
http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/7e52b1b9-0e72-40ff-958c-e688427bfa94

Thank you. I'm not understanding on what bootsec.dos has to do with it? I haven't had DOS on my PC in a couple of years, so I don't have an old bootsec.dos to use.

I'm sorry about that.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 20, 2011, 01:34:06 AM
RE: Windows 7 and DOS 6.22 on the same hard drive.
A brief report.
Most often the 'experts' say use a Virtual Machine.
You might install DOS 7.1 and Windows 7 on the same disk
You  might boot DOS 6.22 from a USB. BIOS dependant.
DOS 6.22 can not be installed above the 7.5 GB mark.
DOS 6.22 must be on an active  primary partition.
Once source says GPART has to be used.
Another says EasyBCD needs to be used.
Others claim GRUB will do it.
I am testing two different third party boot managers the promise to do the job. They are FREE. Will report back later.
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 20, 2011, 05:13:06 PM
I have go to a dead end on this project. Here is how far I got.
Found a good copy of MS-DOS 6.22 which does NOT support FAT32 file system and can not be located beyond about 7.7 GB on a hard drive.
Now I have Windows 7 and DOS 6.22 on the drive and both working. But I can not make a valid boot menu for them. I have to use a floppy to go set a partition active to boot either windows 7 of MS-DOS 6.33 on that one drive.

Windows 7 has the first and third partitions. DOS has the second. Yeah, but it works. Just no simple way to make amen All Boot loaders I have tried insist that they have to be in the active partition. Won't work that way.

The DOS partition is just FAT, not FAT32.
Using DOS 7.1 would mean using FAT32, which changes the game.

The objective of the experiment was to see if both DOS 6.22 and Windows 7 could be on the same hard drive in  each his own partition and boot either from a menu.

Using a USB or floppy is not fair. Just the hard drive. And no fair using smoke and mirrors. One product recommends putting a patch in the BIOS. No, I won't go that fa'.

I will quit here. :(
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Computer_Commando on August 20, 2011, 05:33:41 PM
Which tool did you use?
BCDedit?  http://www.sevenforums.com/tutorials/2676-bcdedit-how-use.html
BCD Editor?  http://www.boyans.my3gb.com/
Or something else?
Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 20, 2011, 06:21:38 PM
I used Easy BCD. Could  not get it to work. I will try those.

Title: Re: Why did Windows 7 go on drive C when I specified D?
Post by: Geek-9pm on August 28, 2011, 08:37:23 PM
The OP wants to put D OS 6.22 and Windows 7 on the same hard drive.
Dos can be started from a floppy, but OP wants it on the hard drive.

Windows 7 does NOT destroy the DOS drive. Rather, it creates its own partition and refers to it as the C drive, although it is in fact the second partition.

This is want works for me.

Erase a drive and prepare it so tat there is a FAT partition at the start of the drive. It must be under the 2GB limit. A 200 MB is lots for DOS applications.
After installing and testing DOS 6.22, install  Windrows 7.

To get back into DOS, boot from a CD  that allows you to switch  the active partition and reboot from the hard drive.
This could be the same CD used to install MS-DOS to the hard drive.

The OP can do a Google for
Build DOS 6.22 install CD
And find out how to make a bookable DOS CD.
A simple solution.