jaclaz

OK, the -o switch is present, but 4.2 Gb seems to me too much, as from what you list a lot of files should be "in common" You may want to try -oc or -oci or -ocis: If you can have the image smaller than 4 Gbytes, it could eliminate part of the possible causes. I guessed it was a bootable .iso , but what it should boot? I mean DOS, Linux, a PE of some kind.... As an example, BCDW is said to be non-compatible with XPSP2 SETUPLDR.BIN (and probably newer releases too): http://www.collewijn.info/xpe/boot-cd/Make...zard%202.01.php Whatever the .iso is called, try changing it's name to something that goes BEFORE anything else, like AAA.ISO. WHAT error does it give? jaclaz

Care to share what you did here? Or maybe contact Steven Saunderson and tell him, so he can add the info to the page? jaclaz

You may have "fallen" in this: http://www.msfn.org/board/Weird-NTLDR-Error-t119971.html How big are the files already on DVD? Which tool did you use to create the .iso? Did you use the -duplicate-once (or similar setting) when building? jaclaz

I cannot say what is meant by "premier", but yes, it should work allright, of course it is highly advised to burn the downloaded file to a DVD as to re-create a "standard" install DVD and store it safely. Without knowing which kind of file you are going to download I cannot say if file extraction or any other modification needs to be done. jaclaz

Well, it does look like a queer "reference" to the original problem. I read the above much like: Definitely my English (or logic ) needs lots of improvements. jaclaz

Check, re-check, and triple check EVERYTHING. Set the BIOS to use as less "advanced" options as possible, disable in it any device that is not vital, like audio, parallel ports, network card, etc. Boot with /BASEVIDEO and /BOOTLOG http://technet.microsoft.com/en-us/sysinte...s/bb963892.aspx Check the the file %SystemRoot%\Ntbtlog.txt POOL_BAD_DRIVER says nothing to me, post the CODE of the BSOD, and any other reference. http://www.geekstogo.com/forum/Windows-XP-...des-t43519.html http://northtechs.com/blscreen.htm http://www.updatexp.com/stop-messages.html Check the Event Viewer files on a working machine: http://support.microsoft.com/kb/165959/en-us i.e. *.evt under %SystemRoot%\System32\Config\ This app has a FREE personal license: http://www.eventlogxp.com/ A good idea could be that of starting again from scratch. I assume you ALREADY tested the nliting by installing from the modified source on a "normal" HD, didn't you? Use the files I posted, after having re-chacked them. jaclaz

Naah, ...actually attempting to avoid it is too much work.... jaclaz

Your post made me wonder about these two threads: http://www.msfn.org/board/Is-there-any-too...me-t120126.html http://www.msfn.org/board/Can-anyone-help-...ut-t120127.html Are BernardPerry and Steven_Law, ronal and paull playing a similar game? jaclaz

deda, why don't you actually read the previous posts? The problem is about "root system" as you call it, and it si possible to change it, though tricky and not recommended. jaclaz

Just for the record, though I agree that the "storage" where the .iso is built is most probably NTFS, it could well be another partition formatted as FAT32, and however Vista CAN be installed on FAT32. http://www.911cd.net/forums//index.php?sho...181&st=1712 (of course it does not make much sense if not in very peculiar setups, but still it is possible) Back to topic, there are "size barriers" in the actual initial stages of booting, see here: http://www.msfn.org/board/Weird-NTLDR-Error-t119971.html Though the above applies to XP, same thing is most probably true for VISTA. jaclaz

You do not get "a" BSOD, you get a BSOD with an error number. If it is 0x0000007b "Inaccessible boot device", first thing to try is the modified NTDETECT.COM: http://www.msfn.org/board/0x0000007B-Blue-...xt-t112630.html However, besides tutorial 5, you may want to look here: http://forums.ngine.de/viewforum.php?f=4 http://www.ngine.de/index.jsp?pageid=4176 And here, a "less known" page that may clear some points: http://www.nedprod.com/Niall_stuff/BootWinUSB/ And even try the "fully automated" way: http://www.usboot.org/tiki-index.php Just in case I am attaching an archive containing the (supposedly working, UNTESTED by me) .sif and .in_/.inf files. jaclaz USBBOOT_files.zip

A good start point is this bootdisk: http://johnson.tmfc.net/dos/usbdrv.html There is a "better"/"newer" Iomega driver floating around, see here: http://www.boot-land.net/forums/?showtopic=4260&st=10 Read this too: http://www.boot-land.net/forums/?showtopic=4462 jaclaz

Hmmm, still something is strange... The three bootsectors are IDENTICAL (exception made for volume serial that is irrelevant). The three MBR's are ALMOST identical: Bad_MBR_HardDisk1.dat and MBR_HardDisk1.dat are identical. Win_XP_MBR_HardDisk1.dat, instead has partition type set as 0E instead of 06. The non-booting of the couple Win_XP_MBR_HardDisk1.dat+Win_XP_BootSector_DriveH.dat can be attributed to the partition type change (it should mean that your motherboard BIOS does not like LBA addressing on USB stick). But there is NO reason why the couple Bad_MBR_HardDisk1.dat+Bad_BootSector_DriveH.dat does not boot while the couple MBR_HardDisk1.dat+BootSector_DriveH.dat works, as they are IDENTICAL. Maybe in the haste of testing you "mixed" versions? Or a "cold" or "warm" reboot was needed? Just in case I am attaching a "fixed" MBR that implements the same "hack" the HP USB formatting utility uses, see here for reference: http://www.boot-land.net/forums/?showtopic=2246&st=15 It should be "more" compatible and hopefully let you boot with both 06 and 0E as partition type. jaclaz MBR_HardDisk1_fixed.zip

@PROBLEMCHYLD Sorry, I do not get it, is it a "declaration" or a request for assistance? If the latter, which are the specific problems you need help with? jaclaz

If I may, it seems to me that this thread is taking a "strange" turn. Volatus asked something, i.e. if anyone knows a way to have Windows XP on HD to get drive letter C: even if some other devices are connected. So far there were TWO valid replies: 1) install the XP on whatever drive letter it gets and later change it. (tricky) 2) install the XP "pre-mapping" the hard disk (tricky as well) Then a number of replies, saying more or less that he should dis-connect all other devices before installing, which I am sure was a "trick" Volatus already thinked of, and that probably caused in first instance the question. What is the point to post that kind of info? The original question does not appear to be a poll of the type: So, taking as granted that disconnecting all devices is the most popular and possibly simpler way, are there alternatives? jaclaz

Uniextract should help: http://legroom.net/software/uniextract to get you the files inside the installers/exes. jaclaz

Well, the good news is that we found a replicable way to make the stick bootable. I need to know EXACTLY which steps you took for "starting" the installation, or if you prefer, a link to the tutorial you are using/trying to follow. Since this "peculiar" machine (or couple stick/motherboard) appear to behave weirdly, ANY step that involves re-formatting or re-partitioning the stick should be avoided, if the stick is booting and after the whatever-you-do it is not booting anymore, it means that the procedure changes something. For the record, a blinking cursor is usually connected to a problem with the bootsector, whilst the "Non system disk, replace and press any key" is usually connected to a MBR problem. You should repeat the steps that made the stick bootable, I would try also - before formatting - to experiment in beeblebrox changing the 06 (FAT16 CHS mapped) to 0E (FAT16 LBA mapped). Once you have a booting stick, simply use hdhacker to save both MBR and bootsector, then, once the stick fails to boot, simply restore those two sectors with hdhacker. Please save your current (NOT BOOTING) MBR + bootsector, then repeat the procedure for making the stick bootable and save the (GOOD, BOOTING) MBR + bootsector, post the four of them, maybe I can find by looking at them what is wrong. jaclaz

Migrate.inf is dependant from the MBR hard disk signature, so, it is somehow "hardcoded". Something you may want to experiment with (untested by me) is to write a "conventional" hard disk signature to the first drive MBR - matching the entry in migrate.inf - before installing. Then after system has booted, change it with a "random" one. Would the system "sense" automatically the signature change and "keep" the drive letter? Cannot say, but if you use a batch to call (for example) MBRFIX to change the signature, the same batch could directly modify accordingly the Registry entry in DosDevices..... jaclaz

Quite hard to run since I don't have the DVD, I bought a cheap laptop with preinstalled Vista and I did not get a DVD with it, so I can't run it. Anyways I skipped that step and posting the .dat files here. Strange. I thought bootsect.exe wass installed by default, have you tried opening a command prompt and running it? http://support.microsoft.com/kb/919529/en-us However the MBR you posted is simply "crazy", cannot say what may cause this behaviour. Get beeblebrox here: http://students.cs.byu.edu/~codyb/ and use it to access your stick, you'll see values: 06-80-0-2-3-248-254-63-128-4013568 "Right" values should be: 06-80-0-1-1-248-254-63-63-4000122 Try correcting them, save changes, extract and reinsert USB stick, re-format it. Still we need to find a way to correct the bootsector to invoke NTLDR if you do not have bootsect.exe, Vistabootpro should have a feature for it: http://www.pronetworks.org/forum/viewtopic.php?t=77547 http://www.vistabootpro.org/ See if it works... jaclaz

I am not sure to have understood completely your setup or what you want to do. Did you check this site? : http://www.depicus.com/wake-on-lan/ jaclaz

deploymentgeek You may want to read Rules, expecially #4: http://www.msfn.org/board/Forum-Rules-Upda...ead-t18408.html And you might want, anyway, to check the spelling on your site, I would never buy anything from people that write "Avaible" instead of "Available". jaclaz

Are you "another" west117wolf? http://www.msfn.org/board/deleting-t76927.html ...or is it just a kind of memory shortage? jaclaz

Colinr, there is no need to double post: http://www.msfn.org/board/WinINSTALL-LE-t1...html&st=169 You realize hat this post is from 2003? Have you checked that link to the homepage does not work? That: http://www.ondemandsoftware.com/ redirects to: http://sup.scalable.com/ The direct link works because the company, that in the meantime changed hands/name keeps under the same name a Commercial product, which in their simplicity, they sell for more than 1,000 Euros: http://www.scalable.com/ http://store.scalable.com/ You may want to try if you can find an old copy: http://www.filewatcher.com/m/wininstallle....765064.0.0.html jaclaz

I don't see the point since your BIOS cannot boot from USB. However, you may want to try the PLOP bootmanager: http://www.plop.at/ http://www.plop.at/en/bootmanager.html http://www.plop.at/en/bootmngrusblog.html Win95, win 98 and Me DOS, i.e. DOS 7.x and 8.0 are 16 bit, exactly as MS-DOS 6.22 were. There is normally no problem whatsoever in booting/installing these systems, including MS-DOS 6.22 from USB, since ALL DOSes rely on BIOS, they work allright if the BIOS support booting from USB. Of course you cannot install (no matter from what media) install MS-DOS on a non FAT12 or FAT16 partition, (the latter filesystem has a limit of 2 Gb), but you can pretty well use an .img and boot it through grub4dos. jaclaz

The files you sent are invalid. WHY did you save them as .txt? They are filled with 2E's What did you use to 00 fill the drive? You didn't open them in NOTEPAD (or other non-binary-enabled application) and saved them, didn't you? Since you are working with Vista , try using it's DISKPART utility as follows: list disk (to make sure that the USB stick is disk 1 below, if not change accordingly) Remove the USB stick. Reinsert USB stick. Right click on it in Explorer and choose to format it. Run bootsect.exe /nt52 Remove the USB stick. Reinsert USB stick. Use HDhacker to save MBR and bootsector, give to the files the extension .dat, do not open them with any program, just zip or rar them and attach them. jaclaz