Dogway

GREAT, done! I never thought things would go as smoothly. On your third step I supposed you meant XP x64, so i got in and removed letter. Then back to x86, wiped the files and edited back boot.ini. Thanks a lot! edit: the boot took a bit longer than usual, and a small window rapidly popped up and faded away on the loading configuration blue screen, but it works.

GREAT, flawless! All went as expected, installed XP x64, drivers, software, etc, in C:, Now I can boot with default Windows boot manager on x86 or x64, I could remove x64 letter (T:) from x86 disk management, but couldn't do the same from x64 , it says L: (my XP x86 partition) is boot partition or something of that sort.

I'm not qualified enough to touch that, not at least if I pretend to do the install today. There are more questions than answer if that was the case, for instance they all talk about setting or changing device letters. I think that for my needs removing letter in Disk Management would be enough. But thanks a lot for all the help. I will reply back in a few hours with the outcome.

"...(or a direct Registry editing, whatever suits you)." sorry, I thought "NoDrives Manager" was an indirect way of editing the registry you commented as an available option. I could do it myself, but I need to know exactly what entries to edit, especially after knowing that the NoDrives key is not the one you refer to. I used your linked 0.4.5 version in google code and linked version of mkisofs from your posts from the very begginning, the only thing I borrowed from that randome page was the command call for the ISO creation, which happens to be the correct one described in the diddy.boot page. I already tested the CD and boots fine on grub. I will do the thing later on, after I finish an ongoing encode.

"by using Disk Management or Diskpart (or a direct Registry editing, whatever suits you)." Ok, so indeed I can use anything. Actually I was using a simple tool called "NoDrives Manager", I believe it just edits registry, but is handy so I was a bit worried when you mentioned "complex" stuff as dealing with Diskpart or Disk Management, because I was wondering if removing the letter in Disk Management wouldn't compromise partition data, guess not, right? I already did the MBR backup as I said in my previous post, now I only need an application that allows me to restore it when necessary (MBRwizard?), will look on the same page I found the backup utility. I also made the grub4iso following this page, and burned onto a CDRW (edit: actually it didn't work, I finally made the iso using the matching call of this page and worked): http://www.rmprepusb.com/tutorials/makegrub4dosiso I will anyway test it on a VM to play it safe and assure it works. It really annoys me to deal with things I don't know as you described is common among Dell environments. I guess I should live with it, and restore MBR given the moment. That's precisely why I was so scared to touch this computer that I had a bit abandoned, now at last I could get into my hands most if not all the updated hardware controllers (Dell Support refused at the moment to even give me a component list of the system, to search drivers by myself), managed to reinstall windows and integrate the **** RAID controllers, and now backup the important stuff and know a little more about this heavily customised system by Dell. Now I know what I have and what to do with it, and in extension, take the most of it. I am greatly annoyed I can't run SeaTools DOS because my HDD's are under RAID, and I care a lot about HDD's integrity, when the time comes that the hard drive dies, I will need to replace it with another, I guess then I will know for real if I need the backed up MBR or not, right? I hope to do the multiboot thing tomorrow and let you know how it went.

I was referencing a line of this post "Later you can remove the drive letter from the "other" partition from each of the two XP's from Disk Management." What is this for, "hide" my partition, unmount it? What should I do then, the above Disk Management procedure, or the Disk Part one by setting a +10 new ID? I remember having issues with DiskPart on XP before, being unable to format a drive with custom block size. I will backup the recovery partition right away in those explained 3 ways, but to clear things up yesterday I made a video of my system booting that you might have missed. I made it so you could tell me exactly if what I have is a recovery partition or a Utilities partition (I read that Utilities normally go first, and recovery last in partition order). And in case that's not enough to know, ask you how can I know it (what exactly to backup, if any). FYI my system came installed with XP x64, if that helps. Either way, I'm gonna backup those three meanwhile, so rather than "what to backup", "what to delete" (or replace, when a fix is called) edit: backed up the MBR, and whole first head. Rel sectors showed 63, so only backed up those two. submixc8: Is it risky to test that what you say? I already have the backups, anyway I will follow jaclaz guidelines in case there's a better way to know what kind of partition/booting mechanism I have.

Ok, I got some time. It's a bit hard to grasp, but let's see. First, thank for explanation on the "EISA" partition, guess it shouldn't be called like that, but still, it applies as a partition right? so I assume partition orders don't change. -Since I will be booting grub4dos from CD I guess I can skip the first code block (hd maps). -So to start, I delete everything on my x64 partition, that is T:, and put inside a "tag file" (what file?). -make x64 partition (third partition, right?) the root partition with: root(hd0,2) ls -make the partition active (as in C:), while hiding current C: (my second partition after Dell diagnostic tools partition) makeactive (hd0,2) hide (hd0,1) -reboot, and install XP x64 (I guess that at this stage on the Windows Install blue console x86 partition will be now hidden, true?), let it do the unattended, etc. reboot and load again grub4dos from CD to unhide XP x86 partition, make it active (default OS) by typing: unhide (hd0,1) makeactive (hd0,1) -reboot again, it will boot into the only available OS at the moment that is XP x86. Change boot.ini to allow XP x64 to be accessed through default XP boot manager. Hide T: partition (C: on the XP x64 install) from Disk Management. Hide x86 partition from x64 OS as well. FINISH Well, correct my process if something is wrong. Also I have many questions: 1. what tag file do I place onto the empty third (x64) partition? 2. Can't I hide each other partitions by using the hide commands? or is it because 3. in the end we are not installing grub4dos right?, but only using them as an indirect way of managing the migrate file from the command line. And the reason for that is due to -> an unusual "recovery partition", which I called EISA, and contains the "Dell Diagnostic Tools" (this is actually a Precision 690 Workstation), so not recommended to rewrite MBR with grub4dos. 4. I would ask you then, how to hide them with disk management?, but I don't think that's too critical to know by now (probably well documented around?), more importantly, how to backup MBR? This should be the very first thing to do, true? You are a master, have all the variables covered. Let me know if you need any info on my system. edit: I access the Diagnostic Tools by pressing F12 at the very start of the boot process, in the same panel I am to press F2 to enter BIOS. Later it takes me to a similar panel to that of F8 with certain entries (Boot from each disk, load from CD, Reboot, Recovery, Diagnostics, etc) Youtube link

I will answer you in detail later when I got some time, but wanted to a quick feedback before it. I forgot to say I have a working BartPE I made a few months ago. I tested it this morning and it works (explore files etc). What I tried to test a few days ago was booting windows from USB (in order to install a nlited OS with integrated RAID drivers), I couldn't make it work, I also used it to install the drivers at F6 previously, tested with 2 USBs and BIOS didn't like any. I have for these things instead a CD-RW, and a DVD-RW I bought a few days ago that currently has burned this mod of my unattended XP x64 with the integrated RAID drivers, this one I will use. I read also earlier today all the pages from grub4dos, skipped the few pages that had nothing to do with my case. I'll read your help throughly and ask later. My hard disk is as follows: - EISA - x86 - x64 - Unpartitioned 8Mb (doesn't show in disk management)

ok, I see, what you suggest is to interrupt the installation (when the Windows performs the first reboot after copying files) and boot from a Live CD, look for migrate, change letters, reboot and finish install of XP x64? Here I will want to set x86 drive letter C: as a far letter, X: for example, so it doesn't displace my other known drive letters, D: (Data), E:, etc For my current XP x86 I don't care, second partition (where x64 will be installed) is already T:. Then I hide them, with disk management? is it possible? I also didn't correctly understand your last sentence about boot.ini, mmm no I think I do, if I were to edit BOOT.INI isn't enough to boot to x86 and change it? I'm not very concerned about that I think. Tell me if I missed something, actually I want the method that is less risky, about difficulty I funnily find this last one easier although (despite not being as straightforward). I think the risk here is to not miss the first reboot, otherwise the XP install continues. For the grub4dos way I need to know more things I'd need to ask, specially for the menu.lst file, commands like norootverify, makeactive, etc I'll do what you suggest me to. Thanks for help.

I should ask then if with the MENU.LST file, do I still need PTEDIT32 as suggested? Also I don't know if renaming ntldr to ntldr.bin, and naming grldr to ntldr is legit, sfc can detect and replace it back or lead to some troubles, or not? Shouldn't I install grub4dos with the grub installer or bootice first? Also if I were to load NTLDR.BIN (upper case?) I would need to edit my boot.ini to only one entry, so I avoid the XP boot manager from popping up. XP x64 would load from the grub4dos boot manager (namely grldr named as ntldr by the "chainloader +1" call), is that right? edit: finally found the holy page that explains mostly everything. There is one thing still, they explain how to hide boot partitions from each other, but I bet they will still be named after consecutive letters because OS install is done prior to GRUB4DOS, just as my current situation.

duplicated

No I don't want to argue, your quote doesn't state it doesn't work outside Linux, I also went to wikipedia and didn't read anything about it, that's why I asked you why I can't use GRUB 2. I will use what's more convenient and does the job. Does your MENU.LST avoid the need of gparted?

Don't I need gparted with that MENU.LST? For simplicity I omitted that I have also an EISA partition on first disk, it's the first partition, XP x86 second, XP x64 third. I'd need to change that, right?: [[hook1]] title Microsoft Windows XP Professional x86 unhide (hd0,1) hide (hd0,2) chainloader /NTLDR.BIN [[hook2]] title Microsoft Windows XP Professional x64 unhide (hd0,2) hide (hd0,1) root (hd0,2) chainloader +1 Then what, reboot and reinstall XP x64? is that all?

I don't have problems in using Grub4DOS, but why not GRUB 2? it's much newer and probably a bit easier to use. The "hiding the partition" trick, I heard it from a video in youtube but for other reasons (not override boot loader from one OS to another). I know how to do that, the guy used gparted from a live CD so no risk there, if that's ok. The part I'm 100% lost is about the boot manager, I will be full read on the tuto and videos when you confirm me I can't use GRUB 2.

I was very lost because this is the first time I do this. I already have a dual boot but managed by windows. I installed first XP x86 on first partition of first disc, that is C:, and later XP x64 on the second partition of the first disc, designated as J:. Now for me that is a problem, is it possible to convert that J: to C:? And then make those partitions not see each other? I went reading a bit and figured out I need a boot manager, then wondered which out of the many should I choose, finally decided that GRUB 2 could be a safe bet, but I don't find information about it, all I see involves Linux which I'm not interested. If ultimately it is not possible to convert J: to C:, it's not a big deal either, I can reinstall XP x64 in the second partition from scratch, but I'd like to keep C: untouched by all means. Any help is welcome. Thanks!

Unbelievable, that tiny thing did the trick! It was already after lsi_sas so I removed it. So x86 needs symmpi.sys, whereas x64 needs lsi_sas.sys... strange... I'm going to investigate now how to hide partitions from certain OS, I have x64 in J:\ if I move it to C: will I need to reconfigure all the paths? Also I read about some boot manager that needs to be in a small partition. I don't know why but I always have a small residual partition of 8Mb I think, is it usable? It's a bit of a pain if I had to format again this partition and install x64 again just for that. HDD 1 1: EISA partition 2: C: XP x86 3: J: XP x64 4: no partitioned edit: I will ask in a new thread!, thanks for all the help

More misterious things. Now that I have XP x86 installed configured and running, I'm going to install x64 on the third partition of the same drive. As I did with the other OS I integrated the SAS drivers and run from CD, then promptly an error message: “The device associated with following device driver will not work correctly on this computer:/symmpi.sys. The device driver is not compatible with the x64-based version of Windows your computer is running. This device driver may be required to complete Windows setup. Please contact the device manufactor to obtain driver compatible with the x64-based version of Windows.” Seems I integrated the wrong drivers?! I doubt, how do I check? this is my TXTSETUPfile, looks fine I would say... [SCSI] lsi_sas = "Dell SAS 5x and SAS 6x Adapter Controller Driver (Windows XP x64)" My OEM XP x64 says: [SCSI] lsi_sas = "Dell SAS 5x Controller Driver (Windows 2000/XP x64)" The most relevant thing is that the OEM TXTSETUP file says: lsi_sas.cat = 1,,,,,,,303,0,0 lsi_sas.inf = 1,,,,,,,303,0,0 lsi_sas.sys = 1,,,,,,4_,4,1,,,1,4 lsi_sas.x64 = 1,,,,,,,303,0,0,lsi_sas.sys whereas the one I integrated the drivers are: lsi_sas.cat = 1985,,,,,,,1985,0,0 lsi_sas.inf = 1985,,,,,,,1985,0,0 lsi_sas.sys = 1,,,,,,4_,4,1,,,1,4 lsi_sas.sys = 1985,,,,,,,1985,0,0 lsi_sas.tag = 1985,,,,,,,1985,0,0 I did another test. I thought the differences were because wrong drivers, but they are both right it's just that the OEM are a previous version. What is wrong is the nlite integration, even using the exact same drivers as the OEM the above differences persist. I think I'd be better off by manual slipstreaming with the allen2 mini-guide, probably just copying the lines from one TXTSETUP to another, out of TXTSETUP I'm pretty much lost...

DETAILS were given along the string of events, which is the best way of explaining things. But since this thread is long lost due to submixc8 smartness, I made a new one. I suggest you to stick to OP question always, It's hard to follow conversations once submixc8 throws the ball, he is already reported, I hope a moderator would come in and do some cleanup.

Finally managed to install through the nlite method. I did a.quick format now since I had done a full format yesterday trying out with the OEM XP x64. Then something strange happened, I got the typical dual boot showing xp x86 and xp x64, and then that Windows couldnt start because a wrong.disk configuration. I then rebooted and chose xp x64 and finally xp x86 started. (?) I inspected boot.ini and both entries point to partition 2 (C: after eisa partition), but there's no track of the old x64 install on hard drive. Also on the default line and the first OS line (the non working XP x86 entry) there's written "signature(c4946615)" [boot loader] timeout=30 default=signature(c4946615)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] signature(c4946615)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /pae /fastdetect /noexecute=alwaysoff multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional x64 Edition" /noexecute=optin /fastdetect

no sorry, 2 different builds, 32bits gets 32bits drivers, and same with x64. I had to create a bootable USB with flashboot, because my DVD-RW had to fail in the right moment! (it-s detected as DVD-R booktype, so it can-t be erased, and can't change booktype in imgburn by some reason). I added it as boot from C: instead of A: since I'm not doing F6 or anything, is that right?

ok, I just finished integration with both x86 and x64, will try again now, i just clicked on Driver, and Make ISO buttons, so it should work. I cross fingers.

tomasz86, are you sure that re/running nlite won't screw my unattended? allen2, I will try that if this method fails, it would be too many hit and miss concerning what to write on the files...

if that's true, you can save my day, or rather my week TBH, I'm gonna try right away.

I have an already nlited ISO, so I can-t run it again to integrate the SAS RAID drivers I think. I don-t have a floppy drive to run F6 from, and the USBKeyPrep F6 method is not working for me with 2 USB pendrives. I-m thinking whether it-s possible to edit some files in the ISO and integrate manually the RAID drivers, so I can burn again and install Windows. Or another option is to use a so named "mass storage CD" described here to preload drivers. Any help is welcome. Thanks

Man, I don-t know what the... what the hell happens with you but you just flood my threads with nonsense and I think that-s the problem, no one else will help me because they-d think I-m at good hands... so wrong! You just say google this google that, trying to look smart but I-m telling you, I dont give a crap about nlite or slipstreaming, I want to integrate drivers at F6 and I have problems with it. I ALREADY HAVE THE EFFIN DRIVERS DOWNLOADED. No RAID Intel on a PowerEdge, DELL RAID SAS 5/iR on a Precision 690.