In an ideal start - yes oldest OS in first and progress to newest...; thus '98 in first - which strict adherence the core conditions for the active Primary. And there is no need of add-in boot-utils if approached correctly. However '98 can go in after XP depending on situation etc...; and there is some tweaking/work to do - depending on how... At this stage... unless you are happy/willing to start afresh with the whole routine... yes you can set 40Gig drive as master (and for safety sake - Master with no Slave attached); ensure it is fat32 in the active Primary. If there is only one partition on this drive (i.e. a 40Gig Primary) then fine... First... copy the ntldr, ntdetect.com, boot.ini from the 160Gig XP partition to a floppy; lock that floppy and keep it handy/safe. Install '98 as per norm to this 40Gig drive; either via CD boot or the usual '98 floppy + CD. Next copy the contents of the floppy to the '98 (40gig) drive c: root. Via notepad/wordpad in '98) open the boot.ini file (now on the '98 drive); edit the entries there for XP so that the entry rdisk(0) reads rdisk(1); there will be two lines where you make this change. Save changes and exit edit... Then slave the 160Gig drive to it; ensure you have jumpers correct... At this stage you will see only the '98 system. Now start a an XP installation (usual CD or 6 floppies + CD approach - not from within '98) - to the 4Ogig drive, and install it to the temp folder on that ('98) drive - so its path is c:\temp\winnt (or c:\temp\windows) whichever it goes in as by default. Cancel the whole setup/installation at first reboot. Remove all disks and allow to reboot as per norm. It will come with an XP boot-menu; this will list the cancelled installation - by default; will include the references to the version (on the now Slaved drive) that have the entry rdisk(1); also windows '98... Manually chooose to boot to the XP version on the Slaved drive; set it as default. rebooot to verify it does just that. Presuming so... locate/delete the c:\temp installation on the 40Gig ('98) drive. Also edit out any references to that installation from the boot.ini - that is on the 40gig/'98 drive. Do NOT edit the boot.ini on the 160Gig drive. Also locate/delete any foders/files that start with $ symbol on the '98 drive. These are temp installations usually removed automatically once an XP installation has completed (successfully). You have to do it manually this time. Reboot to verify all is well with both '98 (on the 40Gig drive) and XP (on the 160gig drive). Presuming so... empty the recycle-bin on the '98 drive; defrag that drive to tidy up the mess... Job done. By installing '98 first to the 40gig drive you have established the critical fat32 situation for the active Primary; and by Slaving the 160Gig to to the 40Gig you are preserving that situation. By installing XP as c:\temp etc... to the '98 drive, you are allowing XP setup to automatically detect '98 and create the necessary bootsect.dos - by which '98 will bot from the XP boot-loader. You will also automatically rewrite the 40Gig mbr to the XP version. You can manually create the bootsect.dos - a routine detailed by Doug Knox and others; personally I prefer to let XP do the work for me... By pre-editing the boot.ini copied to the '98 drive, you will have indicated that there is an existing copy of XP on the system - and indicated where... XP setup will modify that copy of the boot.ini to include references the the c:\temp etc. installation (on the 40Gig drive) - and will also add '98...; and create a backup of that that copy (as was before XP went onto the 40gig drive). '98 will boot as c: , and XP will boot as whatever it does now... (d: in your case?). XP will see all of the 40Gig drive; '98 will see only itself and any fat32 areas on the 40Gig drive - if they exist. XP will still boot/behave as now... as all path statements are preserved in the registry - which is read during boot up for XP (and likewise for NT/W2K). All apps/utils will be installed afresh for '98... XP will probably assign a drive letter other than c: to the '98 drive when it see it via Explorer etc... This will not be an issue to worry about; will cause no problems. If the 40Gig is not formatted as fat32, use the '98 SE bootdisk to do just that... But be aware that any given floppy may/may not have the format util enabled... There are versions with some CDs that came with it expanded/enabled; some not so. There are images of for '98SE bootdisk at boootdisk.com that have the format util enabled...; also include CDROM drivers too. Useful to have that floppy... If the drive was wiped - no partitions... then use Fdisk routine to configure the drive and then the format util to format (as fat32). If you go the above routine... at any time you can simply reset the current 160gig as Master and boot to XP as now...; If '98 drive is Slaved at this time it will NOT boot - but will be accessible from XP. Note too that any common/shared data must be in a fat32 partition (or fat16 - but 2Gig limit for each partition). You can put this shared area on the XP drive if you wish, or use the available space within the single partition on the 40gig...? If you want to start afresh (with 160Gig as Master...) - post back for a different approach...

0

Hi trvlr! After a long strugle I was able to reformat the 40 GB drive and install Windows 98 successfuly. Then I setup the cables so the 40 gb drive would be the Master and the slave on the 160 gb which has Windows XP. I checked the jumpers and changed the 160 to . . . . it was set with the jumper on the first prong on the left = line drive capasity to 32 gb. and i left the 40 gb drive alone which was set . . 0 . third prong on the right = enable cable select. Then I started up but it would not boot into the Windows 98. I read the instructions on the 40 gb Segate which said 2 - drives designate one as master and the other as slave. Configure & run Bios setup or system setup program. Select the Auto-detect option & enable logical block addressing (LBA) save Bios setting and exit. To access the drive's full capasity use (LBA) mode or disk manager. Even says boot to disk manager and follow instructions. partition & format, insert your win setup & run FDISK. This is very confusing to me, how do I do this when I can't boot into anything? Can not figure this out at all. Neither can I understand your instructions - they are too complicated for me. I was thinking just to install Partition Magic 8.0 which I have, on the windows 98, then partition to install the WinXP on the same 40 GB disk. What do you think?

0

Avoid PM... For a few unfortuate souls XP and PM has not been a happy event.. I emphasise - a few unfortunate souls, not everyone... You can do it all without that or other similar utilities... You say you have managed to install/boot '98 on the 40Gig... Good - you're a third of the way there... Whenyou attach (Slave) the 160gig you lose access (cannot boot) to the 40Gig drive? More than likely you do have a jumper incorrect... You use either "cable-select" on both drives - or do not use it at all. If you do NOT use cable select.. then ensure (be absolutely certain) you set the jumpers on the 40Gig drive to reflect it as Master "with" Slave, and the 160Gig to be a Slave. At present your post seems to suggest one drive is cable select (the 40Gig), and the 160 is in non-cable select (i.e. Master/Slave jumpers) mode. Again either use cable select for both drives, or the "tradditional" jumpers approach. If you use cable-select then the 40Gig drive will go at the end of the ribbon cable; the 160Gig in the middle. This presumes you are using a current 80 wire/conductor ribbon cable. http://www.pcguide.com/ref/hdd/if/ide/confCS-c.html details this a little more for you. When... you are able again to boot to '98 (with the 160Gig Slaved to it)... you will still not see the XP installation, and any area of that drive that is ntfs. At this stage post back for more help...? Again you are already a third of the way there; you have very little to do... and all without the use of PM...

0

Hi trvlr! Checked the Jumpers and sure enough you were right. The 2 drives had a different location for the "cable-select" so I made them the same. I was deliberating on making the 160 slave on the jumber, but followed your advice. Closed up and restarted and Bingo! right in into Windows 98. Inspected My computer to check the Drives, C: was 40gb and the D: drive was 85 gb, obviously the XP was hidden. There was a problem, on the D: drive someone told me to copy the win98 folder there, before I got the 40 drive running. Thought that was a crazy idea! The problem is tried to drag them into the trash all at the same time it hung. Tried to use ctr alt del but that would not work so shut down manually. It was working fine and though about using Menu/File to Format the D: drive but I changed my mind until I would hear from you.

0

At present... if you were to reset the 160Gig as Master (for safety sake with no '98 drive attached as Slave) will it boot OK to XP? If so - and you are able to... locate/copy the three files I detailed earlier to a floppy - and lock it; those files being: ntldr, ntdetect.com, boot.ini. The thinking here is to avoid unecessarily having to reformat the d: drive and re-install XP entirely; also to avoid losing the option to reset the 160Gig drive as Master and boot to XP directly, at a future time... If you're using cable-select mode then simply remove the '98 drive, connect the XP to the Master posn - where the '98 drive is currently... Once you have those files to a flopppy... reconnect drives as they are now; '98 Master with XP as Slave. Then copy those three files to the '98 (40gig) drive c: root. This having done... reread my earlier post and edit the boot.ini (copied to the '98 drive) - as advised... Post back at that stage? If you cannot boot to XP on the 160Gig - when it's Master again... post back. Likewise if you really want to rejig/re-install XP afresh to the 160Gig drive post back. Personally if it works OK on the 160Gig as is... I'd leave it be and continue with the exercise (above) to complete the dual-boot with the '98/40Gig drive as Master...

0

Hi trvl! Went to the 160 drive WinXP and copied the ntldr, ntdetect.com but could not find the "boot.ini" Is that boot.ini a thing, not a file nor document? I searched another computer and so did a friend, then went on the net but was not able to download such a file. Even searched Sys. & invisible files no luck. I re-read your responce in #7 how to edit the "boot.ini", but this is as far as I can go without that file. You also said to "copy those three files to the '98 (40gig) drive c: root" Are you refering to the Windows folder or System 32 for the "root"?

0

C: root refers to the actual c: partition/drive – on the ’98/40Gig drive in this case. ************************* Can’t find the boot.ini… There are occasions when XP setup will not create a boot.ini… and there are at least two ways to create one afterwards… Using the bootcfg command (from within recovery console) is one way… But you may find that approach more of a pain to follow than the route I outline below… Useful to have some idea/understanding of what the boot.ini looks like and what it means…? A typical boot.ini is given below (courtesy of M$-KB land…) [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect This is an XP-Pro installation. The details say it’s on the first physical drive – rdisk(0) and in the first partition – partition(1). It is set as default OS too boot (logically in this case as it’s the only OS present…!) If there was a second physical drive present, and XP installed there then, rdisk(0) would read rdisk(1); and if XP was installed in say the second partition on whichever drive… then partition(1) would read partition(2) - and so on… You could - having copied the ntldr, ntdect.com files to a floppy already - reset ’98 as Master drive with XP drive Slaved – as recently… Then open notepad/wordpad and copy the above (complete) text therein; save it as a file – boot.ini. Then edit it so as to have the rdisk(0) entry read rdisk(1); partition(1) to read partition(2); save changes. Presumably your XP went in as windows… (but it is Home not Pro?) Presuming so… you will need to edit the latter part of the line (as shown above): multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect to read: multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Microsoft Windows Home" /fastdetect At this stage the boot.ini file you have created on ’98 drive will be: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Microsoft Windows XP Home" /fastdetect Or… save you doing all the work… simply copy the final/example immediately above here into notepad/wordpad, and save it as the boot.ini – located to/on the c: root. Verify you can find/see that file in the c: root on the ’98 drive. Now proceed with the XP c:\temp\windws (or winnt – whichever it offers) installation… as detailed in my earlier post… If you complete it successfully – and you ought to have no issues there… - you will end up with your dual-boot; ’98 booting via the XP boot-loader/bootsect.dos relationship (established on the ‘98/40gig drive), and XP booting (via the boot-files on the ’98 drive) as per norm to the version on the 160Gig drive… And that 160Gig version can still be reset as master – with/without a Slaved ’98 drive) and boot as now…; but in this latter arrangement, ’98 would not boot.

0

Hi trvlr! Got the 3 files, ntdetect, ntldr and boot.ini (with Notepad) from the XP disk and changed over to the 98 disk and copied them into the C: root. Then according to your instructions I changed the boot.ini as below and put HOME instead of professsional and chaged XP (1)partition(2) The boot.ini you gave from (M$-KB..: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating system] multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="microsoft windows xp HOME" /fastdetect Did not connect the 2 drives together as 98 Master. Was not sure this was right

0

Hi trvlr! NOTE ADD-ON TO ABOVE. I corrected the boot.ini to read: default=multi(0)disk(0)rdisk(1)partition(2)\WINDOWS [operating system] where I had rdisk(0)partition(1) Then connected the 2 drives. In the D: drive (160) there are a folder Cabs (empty) and a file Autoexce. Here you tell me to proceed with the XP c:\temp\windws (or winnt – whichever it offers) installation… as detailed in response 7, which you say "At this stage you will see only the '98 system. Now start an XP installation (usual CD or 6 floppies + CD approach - not from within '98) - to the 4O gig drive, and install it to the temp folder on that ('98) drive - so its path is c:\temp\winnt (or c:\temp\windows) whichever it goes in as by default" Are you telling me to Install the XP to the 40 gig drive c:\temp\windows? It is alread installed on the 160. Is there any way to swithch over to the 160 at startup, like PM?

0

bear with me here... been away/off-line a few days... will get across your latest message/query in the next 24hrs...

0

Hi trvlr! Thanks again for getting back! I have followed all the instructions, as far as the 2 ntldr, ntdetect.comfiles & boot.ini I created & edited and put in the C:root. on 40bg drive win98 & a Cabs folder and Autoexe file went over on the D: drive. I thought the next step was to go into Bios & estabish the Boot Order & re-format the 160 drive then install. So, I just bought a program off eBay WipeDrive: http://www.whitecanyon.com/how-to-change-boot-order.php Now you tell me (Post#7) to start an XP installation (usual CD or 6 floppies + CD approach - not from within '98) - to the 4O gig drive, and install it to the temp folder on that ('98) drive - so its path is c:\temp\winnt (or c:\temp\windows) whichever it goes in as by default". All I am asking is what about the Windows XP that is sitting over on the the 160 drive with another partition. Would like to know how this all blends together.

0

You have '98 Master to XP drive; that's correct... Also you have adjusted/edited the boot.ini (as detailed across posts 15/16) correctly... To boot to XP via the '98 drive set as Master requires the '98 drive's mbr be set/changed to the XP version - the '98 drive's mbr is the dos/'9x version at present...; you already have the necessary (XP) ntldr/ntdetect.com and the (edited/adjusted) boot.ini present. But then you would not be able to boot to '98 - because there is no bootsect.dos... bootsect.dos is a copy (created via XP setup) of the dos/'9x/ME mbr info that is stored by the NT family, and is dumped back (replaces the NT/W2K/XP version) when you opt to boot to dos/'9x/ME via the b NT/W2K/XP boot-loader (boot-menu options)... You would have to either manually create the bootsect.dos file, or allow XP to create it for you. As stated in an earlier post..., unlike NT/W2K, the XP repair routine does NOT create a bootsect.dos if it find a dos/'9x mbr... Thus one cannot use the "simpler" repair approach (used with NT/W2K) - one has to use the installation approach - or create that bootsect.dos manually... Doug Knox details (as do several others) a manual routine to create the bootsect.dos etc. when effectively adding '98 to an existing XP system; and in a roundabout way you are adding '98 to an existing XP system... The reason I advise the c:\temp XP installation routine (temp installation of XP to the '98 drive) is that it will: automatically create the bootsect.dos (the essential file to allow '98 to boot via the XP boot-loader) for you; and (after making a backup of the current boot.ini on the '98 drive) add '98 to the boot.ini (already on the '98 drive), retain the edited entries for the XP version on the 160gig drive and thus give the dual-boot - all without using PM. It will install fresh copies of the ntldr/ntdect.com files...; useful bonus if one of those two files (if present) were to be damaged/suspect etc... The c:\temp routine does it all for you - painlessly...? It's also one routine suggested (after a fashion by M$...). Using PM "is" a viable way to go... - with the usual caveats re' XP + PM. I just don't see the need to use it... Personally I feel the less there is present in the boot-path the better... Which having said for many it's the easier option? PM essentially allows you to select which drive/partition/OS to boot; there will be no XP boot-loader etc. on the '98 drive, but the PM util will be present/installed on the '98 drive (set as Master)... If I was to opt for an add-in boot-util... I'd be more inclined to favour BootIt - although I haven't used it... it gets excellent (trouble-free) reports here. You're almost there - without recourse to PM; and at this stage it's your call as to which way to go...

0

Hi trvlr! Fine, it seems that I'm ready to go, so I will install the WinXP on c:\temp on the 98 40gb disk. But what I don't understand is: "(after making a backup of the current boot.ini on the '98 drive) add '98 to the boot.ini (already on the '98 drive)," Where do I ADD the backup of the boot.ini? Also, not clear "retain the edited entries for the XP version on the 160gig drive" And when I am installing, I'm sure it will ask me to choose between the Fat32 or NTFS.

0

"(after making a backup of the current boot.ini on the '98 drive) add '98 to the boot.ini (already on the '98 drive)," "retain the edited entries for the XP version on the 160gig drive" Sorry - badly presented snippets in that paragraph... Must do better next time... What I was explaining in that paragraph... is that during setup XP will initially make a backup of whatever boot.ini it finds on the active Primary partition, then adds an entry for any dos/'9x OS it finds (and also makes the requisite bootsect.dos); and naturally will add it self to the "new" boot.ini. It will also retain the edited entries (in that boot.ini on the '98 drive) for XP already installed on the 160gig drive. Similarly if there was an NT and/or W2K installation present and references to them/it already in that boot.ini (on the '98 drive), it would retain those references to those too. In effect (and this applies to XP/W2K and, in most circumstances, NT) if setup finds a reference to something in the boot.ini it recognises... it keeps it, and makes any other additions necessary. If there was no boot.ini present at all it would create one; and if it found dos/'9x present add that to it etc. and make the bootsect.dos. Off the top of my head... I can't recall if it will prompt for which file format to use on this occasion (to c:\temp)...; memory is that on this occasion it will accept the current format for the target partition as is...? Regardless ensure it goes in as fat32. Also - do "not" accept any offers to repartition, reformat etc... This c:\temp installation is simply to create the bootsect.dos and install the XP versions of ntldr/ntdetect.com (if they're not already present, as well as making necessary changes to the boot.ini.

0

Hi trvlr! I deceided to leave the 40gb Win98 as is. Partition the 160 & format as FAT32. This is info. that I got when you were away for a few days from a post "Dual boot xp win98" Response Number 12,13 Name: jam. Did not want to take a chance as another major setback, which could cost me several weeks or more. Thanks for your help, but I don't know a lot of things yet, especeially DOS. Just picking the easy way out.

0

Reconfiguring the 160Gig afresh and then installing XP again there ('98 as the Master) is perfectly viable and effectively follows the usual recommened approach - oldest OS in first (on Master drive, active Primary partition) then add the other(s) accordingly... (As you were (not so obviously) willing to start afresh... would have been useful to know that initially; you did appear to be rather keeen not to go that route? The reconfig etc. of the 160Gig would have been the obvious route to which to send you along.) The route we had been pursuing meant that the 160Gig version would have survived intact, would/could have been easily reset as Master and still boot OK. In your new/current arrangement, if you remove the '98 Master, or lose the XP boot-files thereon..., then the (new) XP installation (on the 160Gig) will not boot in any circumstance, even if reset as Master... (although it's a relatively simple matter to get it working again in that situation). You were almost there; had less effort to make to complete it all... Horses for courses I guess (one picks the trail/route one feels most comfortable with for most/all journeys...)? Main thing is that finally you have your dual-boot, and without, I presume, using PM... I suggest you keep the notes/posts in this thread for future reference... If when/you feel inclined to pursue it all again you may find it a useful guide and be able to understand how it all works etc., and apply it; also perhaps to help others too...? viel gluck/bon chance etc...

0

Hi trvlr! I will definitely keep the notes/posts in this thread for future reference. I am sure someone will find them very helpful. Thanks again for your support

0