you can't convert ntfs to fat32, you'd have to format it. or you could partition it into 2 drives, install win2k on c: and then in win2k format the d: as fat32, boot the system with the win98se cd and install to the d: win2k will make changes to the boot.ini and let you dual boot, but i reccommend having both partitons fat32 and installing win98se first on the d: (it will still boot, then install win2k, win2k will make the proper changes to the boot.ini and allow you to dual boot, you CAN install win98se and win2k on the same fat32 partiton, but don't!

Personally, I'd do it the other way around.
 
I'd setpu a FAT32 C drive, and install Windows98 on it.
 
I'd then setup a FAT32 D drive and install Win2k onto it.
 
By doing it that way, you can share files between the 2 operating systems.
 
If you put Win2k on an NTFS partition, Win98 won't be able to read it. This may or may not be important to you, but it's worth bearing in mind.

Eddie,
 
Why 'not' put both OS's on the same partition.
Just wondering..
I used to have separate partitions, for each OS, but now, I just install onto the same one.
Is there a disadvantage to this?
 
Cheers
 
Yak
 
--

first of all, do you know how cluttered it would be? Second of all, think about, two windows os's on one partition...i tell you what, go ahead and do it, it will work fine but after awhile you'll understand why you shouldn't have them both on one drive. I found out the hard way, this is the only way that you can learn.

Yes, it can be cluttered, but I reimage every 4 mnths or so. It's like having a full service ;-) Highly recommended. I haven't noticed any performance hits using this method. But, I honestly think the time has come to ditch W98se and just use W2k, as I haven't booted up into Win98se for months and months now. It just means that conflict freespace and carmageddon2 will just sit on my shelf collecting dust
Starlancer makes up for one of them tho..hehe.
 
Yak
 
--

Yakkob, if you format and reinstall all the time then, yea, its a good idea and i have no problems with it, just saying, its not recommended. I do the same thing to my computer because i download and install so much crap and i'm a pack rat who never deletes anything, so i just format and get it over with.

yeah i hear that i just finally archived over 4 gigs of Mp3s. I wish i had a DVD-RAM disk so i didnt have to put em all on 9+ CDs

I saw a DVDburner the other day that can burn 5.4 gigs in llike 30 mins. 270 bux
 
I also wouldn't recomend to ver of windows on the same partition. BAD IDEA
 
------------------
My System
Dell Demension XPS T500
Triple Boot Windows 2000 Pro 2195 (allways reliable) / Windows Whistler Pro 2250 (cool but buggy) / Windows Millennium Final (waste of disk space)
PIII @ 500 Mhz (with after market heatsink and dual fan)
256 Megs Ram
TNT2 Ultra Graphics Card (with the core and memory overclocked by 20 Mhz and dual voodoo coolers)
Matrox Millennium PCI (for second monitor)
3Com 10/100 Ethernet Card
3Com 56k Modem
12.6 Gig IBM HD
40X CD Rom Drive
100 Mb Zip Drive

Quote:Originally posted by yakkob:
It just means that conflict freespace and carmageddon2 will just sit on my shelf collecting dust
Starlancer makes up for one of them tho..hehe.
Yak

I play Carmageddon 2 almost daily on Win2K Server. Did you try installing it in Win2000?
-bZj

Ai, I installed in W2k pro.
Keep getting the message (can't remember exactly) 'Not NT Supported' or something along those lines.
I even tried installing it in W98se and then mapping a shortcut form W2k, which you can do with HL and a few other apps etc.
But to no avail ;(
 
If you have a solution, I would be glad to hear it, and to try it out.
 
Cheers
 
Yak
 
--

That's weird. I had no install problems in Pro, and have since formated that partition, installed Server instead, and just used the same shortcut, without reinstalling the game. I guess I just got lucky.
 
Sorry I can't be of more help,
-bZj

Preparing for Dual Boot
 
Although Windows 2000 has recently moved to Release Candidate stage (this usually indicates that Microsoft believes the code is ready to ship), you may find that all your hardware isn’t supported yet. The big difference between RC1 and Beta 3 is that the number of devices supported out of the box has increased. This means that checking the Windows 2000 Hardware Compatibility List (HCL) to see if your devices are supported is even more important.
During the prerelease phase of Windows 2000, checking ftp://ftp.microsoft.com/services/whql/win2000hcl.txt will be your best indication as to whether your particular collection of hardware will work. At some point, this list will probably be integrated into the main HCL found at http://www.microsoft.com/hcl/. If you don’t see your device listed here, you can check with the vendor to see if it has Windows 2000 drivers available (you can try using the Microsoft Windows NT 4.0 drivers, but don’t expect them to work) or when it plans to have the drivers available.
Installation Options
 
You will need at least two partitions on your hard disk to be able to boot from the OS that is currently on your machine, as well as from Windows 2000 Professional. One of the strengths of Windows 2000 is that it supports FAT32, which means you won’t have to perform a substantial remake of your system to change how a partition is formatted in order to use it. The easiest method for setting up a dual-boot situation is to have an extended partition on which to install Windows 2000 Professional. The Windows 2000 files will be installed on the extended partition. The boot files for Windows 2000 will be installed on drive C. The only remaining task will be to get the drivers needed for your video card, network interface card (NIC), and so forth to work in case your devices aren’t detected or supported by Windows 2000.
Before you believe that you can perform a dual boot using a single partition for Windows 2000, read what follows closely. Microsoft has publicly stated that it will not support this configuration—which means that if you decide to proceed, you will be on your own. Microsoft Tech Support won’t be able to help you fix the problem if things go awry.
The main reason dual booting on a single partition isn’t supported is that Windows 2000 also uses the Program Files directory. This means that some of the same filenames used by Windows 9x are also used by Windows 2000. What may happen is that when you install Windows 2000, Windows 9x will be rendered nonfunctional. This problem seems to be particularly acute when you’ve installed Windows 98 Second Edition prior to Windows 2000. Microsoft has acknowledged the problem and has indicated it will attempt to have the problem resolved by the time Windows 2000 ships.
Enter PartitionMagic
 
The safest option for installing Windows 2000 on a machine and dual booting between operating systems involves the use of a primary partition. The primary partition is the first one created when you partition your hard disk. It’s also the one from which you will normally boot. However, with FDISK—whether it is from one of the later versions of MS-DOS or from Windows 9x or Windows NT—you are allowed to create only one primary partition. Freeing up space is another problem you’ll encounter when you want to set up an additional partition after the hard disk drive has been running for a while. This is where PowerQuest’s PartitionMagic 4.0 and a companion product known as BootMagic come into the picture.
When you purchase your copy of PartitionMagic, make sure you find a package with a notice printed on the outside that a copy of BootMagic is installed. You will want to install PartitionMagic first to prepare your system for the installation of Windows 2000 before installing BootMagic. The installation from CD takes just a couple of minutes. Please take time to read through the manuals to familiarize yourself with the product. This will save a lot of time later when you start installing Windows 2000. I glanced through the manuals but didn’t really read them in detail. Since I rushed through the manuals, I didn’t pick up on certain details that caused me to spend over two hours trying to get PartitionMagic to create a second primary partition instead of an extended partition.
Before you begin, I recommend that you create a Windows startup disk, if you don’t already have one. This gives you a chance to get the hard disk back to a booting condition in the event that something goes wrong. During the PartitionMagic installation (and later during the BootMagic installation) process, you will create a series of “rescue” floppy disks. Do not bypass this process, and be sure to put the disks in a safe place. One of these disks may be your only hope of getting back to a working situation if you experience a problem.
The manuals accompanying PartitionMagic offer several good examples of how the product can be used. In my case, I wanted to install Windows 2000 Professional on a Compaq Armada portable that already contained Windows 98 Second Edition and a 4-GB hard disk. The configuration I hoped to achieve was to split the hard disk, as evenly as possible, into two partitions. I also wanted to isolate the two operating systems from each other so that if Windows 2000 caused some type of irreversible problem, I would still be able to boot Windows 98 to try to figure out what happened. This would require the use of a second primary partition—something that FDISK in MS-DOS, Windows 9x, and Windows NT wasn’t able to do. To make it easy to boot directly to that partition from the Windows Recovery disk if needed, I also chose to use the FAT32 format type. A scenario very close to what I wanted to do was found on page 47 in the Scenarios section of the Creating Partitions chapter of the PartitionMagic 4.0 User’s Guide.
Before starting the partitioning process (and probably the backup of the hard disk drive), it’s a good idea to erase any unneeded files, clear out the Windows Temp directory, and defragment the hard disk using a utility such as Symantec’s Norton Utilities. This will help clear up as much space as possible on the drive you’ll repartition. When this has been done, you can start PartitionMagic to resize the primary partition. You can then create the partition for your Windows 2000 installation. Once you’ve decided how you want to resize the partition, the workstation you’re using will reboot and the operations will be performed in what appears to be MS-DOS mode. Then, the system will reboot and you can start the process of formatting the partition and installing the desired operating system.
You can start the setup process in one of two ways: You can select the Prepare For New Operating System icon on the main PartitionMagic screen for a wizard-based approach, or you can proceed manually by selecting the Operations pull-down menu and then selecting the Create option to begin a similar process. The difference between these two approaches is that with the latter, you will have the ability to choose a FAT32 partition type. When using the manual approach, you will need to make sure that you select a primary partition instead of a logical partition type. This will enable Windows NT to boot on its own partition and not place any files on the initial partition that came with your hard disk. Before starting the Windows 2000 Professional installation, you may want to use FDISK to mark the partition you plan to use for Windows NT as the active partition. That way, it will be installed to the correct location.
Installing BootMagic
 
BootMagic enables you to easily switch between operating systems when you boot instead of having to boot to the last operating system you used, run FDISK to change the active partition, and then reboot to use the operating system you want. As with the installation of PartitionMagic, you will want to create a BootMagic rescue disk in case BootMagic unexpectedly stops running.
BootMagic will automatically detect any additional partitions you create and list them in the boot options menu. You can set the delay time to expire before your computer boots to the default operating system, and you can change the default operating system at any time. And as you add hard drives to your system, BootMagic can keep up with you.
BootMagic supports booting operating systems from drives other than the first. This is something that Windows 9x and Windows NT aren’t able to do. You may not need this option all the time, but when you do, it is nice to know it’s available.
Installing Windows 2000 Professional
 
Begin the installation process for Windows 2000 by booting from a floppy disk and following it with three other disks. If you can’t find these disks, go to the Bootdisk directory on the Windows 2000 Professional CD and run the Makedisk program. You will want to have four newly formatted floppy disks when you start the Makedisk program.
For those of you used to installing Windows NT 4.0, Windows 2000 is a very different install. In one word: quiet. Although you have all the progress indications of prior releases, Microsoft has done a good job of perfecting how well plug-and-play detection works. From start to finish, you can expect the installation to take between 30 and 45 minutes.
Booting Windows 2000 for the First Time
 
If all has gone well during the installation process, you are now ready for your first reboot. Watch carefully as Windows 2000 boots up and displays the logon screen to see if there are any video driver-related problems. When I booted my Windows 2000 configuration initially, I had a hard time seeing the logon screen. All I could see was a partial red screen with some black lettering. At that point, I elected to boot Windows 2000 using the VGA boot option.
With Windows NT 4.0, you selected Windows NT 4.0 VGA Mode. With Windows 2000, you will do it a little differently. When the Boot Manager screen appears, you will first press [F8] to display a secondary screen, where you will select Enable VGA Mode. This will be your best option for resolving video-driver-related problems. In my case, I found that I was using the correct driver but had to reduce the number of colors to 256 in order for everything to work correctly. This may be a driver problem that I hope will be corrected in the final release of Windows 2000 or by the manufacturer of the hardware.
The next place to check to see if all your hardware was identified and your drivers were installed is Control Panel. Double-click the Network And Dial-Up Connections icon and you’ll see the current network status of your machine. If you see a Local Network Connection icon in addition to the Create Network Connection icon, this means the network card in your system was correctly identified. In my case, using only an ADSL (asymmetric digital subscriber line) connection with my network card, I found that the Microsoft Client, IP Protocol, and the Network Card driver for my NIC were loaded.
The first time I booted the workstation, this additional icon didn’t appear in the Network window. If this happens to you or you want to see if other hardware wasn’t installed or identified by the Windows 2000 installation process, double-click the Add/Remove Hardware Wizard. Using the default option, you will see a list of all devices that have been identified in your system. By double-clicking each item that’s identified with a yellow exclamation point, you can see exactly what the problem is with each device. In my case, I found that there was a problem with the Netgear FA410TX 10/100 PCMCIA network card. After a quick call to the Netgear support folks, I found that no driver was planned for Windows 2000 in the foreseeable future. After a quick view of the Windows 2000 HCL, I purchased a PCMCIA (Personal Computer Memory Card International Association) NIC that was on the list and voila, Windows 2000 Professional saw the Internet the next time I started it up.
Setting up for a dual-boot configuration isn’t as hard as I had initially thought, thanks in large part to PowerQuest’s PartitionMagic 4.0. The resizing of the partitions on the hard disk hasn’t caused any problems with the applications that were already on it. This dual-boot setup now enables me to test how things will work under Windows 2000 Professional and compare them to what I know will happen under Windows 98 SE. The cost of PartitionMagic ($69 at a local computer store) is far cheaper than the cost of a duplicate machine. With this configuration, you can start learning Windows 2000 and discovering how it will impact your users without having to invest in a duplicate system.
For more Information
 
PartitionMagic/BootMagic
PowerQuest, Inc.
1359 North Research Way, Bldg. K
Orem, UT 84097
1-800-379-2566
1-801-437-8900
magic@powerquest.com http://www.powerquest.com/partitionmagic/index.html
Windows 2000 Hardware Compatibility List (HCL)
ftp://ftp.microsoft.com/services/whql/win2000hcl.txt
Ronald Nutter is a senior systems engineer in Lexington, KY. He's an MCSE, Novell Master CNE, and Compaq ASE. Ron has worked with networks ranging in size from single servers to multiserver/multi-OS setups, including NetWare, Windows NT, AS/400, 3090, and UNIX. He's also the help desk editor for Network World. You can reach Ron at rnutter@networkref.com. (Because of the large volume of e-mail that he receives, it's impossible for him to respond to every message. However, he does read them all.)
The above article is courtesy of TechRepublic http://www.techrepublic.com/.
We at Microsoft Corporation hope that the information in this work is valuable to you. Your use of the information contained in this work, however, is at your sole risk. All information in this work is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Microsoft Corporation. Microsoft Corporation shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages. All prices for products mentioned in this document are subject to change without notice.
International rights.

/me votes for ras for the, "Windiest Post In The NT Compatible Message Forum" award.
 
Not that he didn't provide an answer...he definitely did!

I'll second that vote if there is such a reward.

I've just read somewhere else about a utility that comes with Win2K that is supposed to be able to fool programs into thinking that they are running under Win98 or whatever. I'm afraid that I didn't note what it was called but it was somewhere on here. Maybe that would help.

apcompat is the name of it. Its not the best program but it works