question bout dual booting.....

[AndyWelch]

planning to try win2k as win98's memory handling is getting on my nerves.
I understand the usual way to do this is to partition the drive, but Ive got a blank hard drive that I want to install to. To avoid confusion, my setup is
MOTHERBOARD:
Primary ide1----------Maxtor (win98se)
Primary ide2----------DVD
PROMISE IDE CONTROLLER CARD:
Primary ide1 (I think, using cable select)-----------IBM (want win2k!)
Secondary ide1 (I think)--------Stuff drive (keep in fat32 for win98)
Primary ide2------------ Cd writer

I dont think the standard dual boot method will work for this, as the dual boot prog will have to switch between hard drives, not partitions on a single hard drive.
I tried linux years ago and this had that LILO boot strap program that looked like it could cope with this, does win2k have a similar thing?
Any advice appreciated

 

[sohcrates]

win2k can install on any drive in a dual boot

i dual boot with win98 on my "c" hard drive and win2k as "e" on a completely different drive

edit: note, if you're installing off the promise card, you need to have the promise drivers on floppy disk and RIGHT at beginning of install you hit F6 when promped to install third party drivers. then, later on, it will prompt you for the driver disk, which will then allow win2k to "see" the drive on that controller and allow you to install it there

 

[AndyWelch]

erm, not sure I understand the tip you gave!!
If win2k cant see the drive on the promise ide card i want to install to, how do i start off?
Im paranoid about messing up my win98 installation!
also, the drive i want to install to is currently fat32, will the win2k install routine convert to ntfs for me, or do i use an "fdisky" program?

 

[sohcrates]

<< erm, not sure I understand the tip you gave!!
If win2k cant see the drive on the promise ide card i want to install to, how do i start off?
Im paranoid about messing up my win98 installation!
also, the drive i want to install to is currently fat32, will the win2k install routine convert to ntfs for me, or do i use an "fdisky" program? >>



basically, win2k does not ask "where should i install to" until a ways into the install process

BUT, if you have an ata100 controller card, win2k does not natively support it...therefore, in order for it to see the drive to install on, you need to basically give it the Promise drivers during the install. and in order to give the install the drivers, you need to hit F6 VERY early on in the install (almost right at the beginning)

during the install, it will then as you to select "S" or something similar to that, and you will select your promise card....

at that point, you will see all your hard drives show up, including the ones on the promise controller...you pick the one you want to install 2k on, and then you will have options such as installing, formatting in NTFS, etc.

does this make anymore sense? basically 3 steps

1) get promise drivers for WIN2k on floppy
2) press F6 during beginning of install (when prompted)
3) insert disk when prompted, and proceed

 

[AndyWelch]

cheers, I understand now!
not installed an nt based os before, seems to be a bit different to win98, that copies all the stuff to the hard drive straight away!
might give it a go tonight

 

[sohcrates]

<< cheers, I understand now!
not installed an nt based os before, seems to be a bit different to win98, that copies all the stuff to the hard drive straight away!
might give it a go tonight >>



well , i don't want to freak you out or anything, installing win2k is really pretty simple

this quirk is really only applicable for those running ata100 controllers such as your promise card.

good luck, and post if you have more questions

 

[AndyWelch]

dont want to cause any moral dilemmas, so reply to this if you want!
A mate of mine has "lent" me a copy of win2k, but he put it together himself with some odd batch files that are supposed to ease the installation i think!
Anyway, here's the contents of one batch file:
smartdrv 4096
attrib -r -h -s io.sys
attrib -r -h -s msdos.sys
attrib -r -h -s drvspace.bin
del io.sys
del msdos.sys
del drvspace.bin
del attrib.exe
del himem.sys
del smartdrv.exe
del config.sys
del autoexec.bat
del command.com
c:\i386\winnt /s:c:\i386 /u:c:\i386\unattend.txt


Cant for the life of me figure out what its supposed to do. I dont want to run it as the last one nearly formatted my win98 install as thats on c:\!
Any light you can shed would be helpful, and as a weak excuse i am a poor student who is fedup with win98 crashing on assignment deadline day!!

 

[sohcrates]

<< dont want to cause any moral dilemmas, so reply to this if you want!
A mate of mine has "lent" me a copy of win2k, but he put it together himself with some odd batch files that are supposed to ease the installation i think!
Anyway, here's the contents of one batch file:
smartdrv 4096
attrib -r -h -s io.sys
attrib -r -h -s msdos.sys
attrib -r -h -s drvspace.bin
del io.sys
del msdos.sys
del drvspace.bin
del attrib.exe
del himem.sys
del smartdrv.exe
del config.sys
del autoexec.bat
del command.com
c:\i386\winnt /s:c:\i386 /u:c:\i386\unattend.txt


Cant for the life of me figure out what its supposed to do. I dont want to run it as the last one nearly formatted my win98 install as thats on c:\!
Any light you can shed would be helpful, and as a weak excuse i am a poor student who is fedup with win98 crashing on assignment deadline day!! >>



don't get me wrong, i'd be glad to help, no matter how "immoral" aka "illegal" it is

but the sad truth is that i have no clue what that batch file is, and frankly, i would be frightened of installing it as well

perhaps the dude who made it can help?

 

[stirling]

smartdrv 4096

loads smartdrive. why, i don't know. maybe the following commands wouldn't work without it

attrib -r -h -s io.sys
attrib -r -h -s msdos.sys
attrib -r -h -s drvspace.bin

changes the attributes of these files from read-only, hidden, and system so it can...

del io.sys
del msdos.sys
del drvspace.bin
del attrib.exe
del himem.sys
del smartdrv.exe
del config.sys
del autoexec.bat
del command.com

delete them...

c:\i386\winnt /s:c:\i386 /u:c:\i386\unattend.txt

and do an unattended install (details in unattend.txt). you probably don't want that since you're doing something specialized (i.e. Promise controller, dual-boot, etc.)