Here's the deal: I have a home built system with two hard-drives. One has Windows 98 and runs perfectly. The other has Windows NT 4.0 server and runs like a dog in the desert at noon. With NT: I cannot see or access the a: drive. I cannot load any drivers for my monitor, so I have a screen size of max 800X600. A lot of the devices cannot be started and I cannot set up the boot.ini file to allow me to choose which OS (98 or NT) to load. Any help is greatly appreciated!

Post with actual HD details: partitions (sizes), formats. Also how you installed '98 on its HD and how you installed NT on its HD... and which was installed first? For a standard dual/multi-boot NT/'9x (even DOS) system you require a FAT16 C: system (active Primary) partition - which is where all the installed M$ OS's will install their respective boot/start-up files. If you don't have this then that's your first problem to resolve... If C: = FAT32 (active Primary) there are a couple of workarounds... but post back first with above info and more help can/will be proffered.

Primary Master Hard Drive: 30GB partition (C:) - FAT32 - Windows 98. Primary Slave Hard Drive: 4GB partition (D:) - FAT16/NTFS - 36GB partition (E:) - NTFS - Windows NT 4.0 Server FLOPPY: (A:) - cannot be recognized in NT. Can be recognized in 98 CDROM: (D: in 98), (F: in NT) - no problems. Cheers!

As already advised above, dual boot '9x/NT preferrs (requires) a C: system FAT16 (active Primary) partition, which is where all installed M$ OS's will install their respective boot/start-up files. The actual system files (the OS's themselves) can go wherever you point them - another HD or into a logical-drive. You have C: system = FAT32 - how are you managing to boot to NT??? Usually there's no way NT will boot with a FAT32 system partition (active Primary) - unless you employ the workaround for this problem; or utilise a third-party add-in boot-manager to utilise separate Primaries for each OS. FAT32 system work-around available at John Savill's FAQ's: http://www.windows2000faq.com - specifically Installations section - and then to: http://www.windows2000faq.com/Articles/Index.cfm?ArticleID=13902 Also presumably you have addressed the 'NT and larger than 7.8/8gig HD's issue'? This too is dealt with in John Savill's FAQ's. When you set it up the 'text-book/standard' way the boot.ini is automatically configured/established to include all available M$ OS's.; equally via the workaround for FAT32 system area the same result. Possibly using an add-in third-party boot-manager will be the quick 'n dirty fix to allow you to set up the NT side properly; also to access A: drive from within NT??? (Each OS would be condsidered unique and in its own Primary, with Extended partition(s) available to whichever Primary is 'active' when using an add-in boot-manager.) http://www.xosl.org http://osloader.com are two freebies. And there's PM???