jaclaz

It is very possible that zoomstorm uses a "proprietary" MBR, like the ones discussed here: http://www.msfn.org/board/index.php?showto...108515&st=0 from what you write it seems like the system is the same as used on Dell's and poossibly what's in the thread may help you. http://www.msfn.org/board/index.php?showto...08515&st=40 It is also possible that in the past some utility, like Partition Magic, MBRFIX, MBRWIZ, or any of the other ones has been (inadvertedly? ) run and the "proprietary" MBR has been replaced by a "standard" one. Each manufacturer/OEM has his own ways to manage the Recovery Partition, some have a tweaked BIOS, some use encrypted files or proprietary formats....it's a mess. If you already re-installed from a "normal" Vista CD/DVD and you repartitioned/reformatted, it is possible that the "proprietary" MBR is gone for good, and your only way out is the manufacturer, or is it possible that they used MS tools only and using the tools mentioned in the given post you can re-create the "good" MBR. jaclaz

NO. F8 is a "windows internal" function. To access a Recovery partition you are generally prompted before and key combo's like ALT+F10 are used. In some cases you have to enter the BIOS to enable the Recovery partition. The link you posted is not valid, please re-post it. Post also EXACT make/model and possibly a link to the manufacturer site. jaclaz

Now that everyone is happy , can I put some "spice" in the thread? May I claim this approach being NOT really new, but simply an evolution/fork of method #2) here: http://www.msfn.org/board/index.php?showtopic=81788&st=6 And still noone actually took the time and hassle to take the challenge : http://www.boot-land.net/forums/index.php?showtopic=644 of making the smallest possible PE buiild capable of installing XP/Server2003 jaclaz

Sometimes I LOVE the English language and it's ability to express understatements: ..and impatient... jaclaz

Hmmm, don't think so: http://aumha.org/win5/a/wpa.htm I underlined the part that both you and Tripredacus seem to have "missed". jaclaz

To put it bluntly, NO. SHELL32.DLL is a "base" system file and is common to ALL USERS on the same install. The only thing you could do is to boot in another OS, temporary change shell32.dll to "your" version, boot XP with your account, then at shutdown re-re-boot on the other OS, and change it back to the original, something that is likely to produce before or late some problems and, if you are not Admin on the PC, the actuall Admin won't let you do if he is in his right mind. If the PC is newish/powerful enough, you could see if it's allowed to run another instance of Xp in a Virtual Machine. jaclaz

@Tripredacus You realize that you are replying to posts over one year old, do you? Which WinpE version are you referring to, WinPE 1.x (XP based) or WinPE 2.0 (Vista based)? 1.x definitely had this limit, for which different workarounds were found: http://www.911cd.net/forums/index.php?show...=7049&st=90 Cannot say about 2.0. @framacomputer It's not the best of ideas to add an unrelated request for help on an unrelated topic. However, at which point of the booting does the XP restarts itself? Does it create a BSOD? Is the PC diskless? jaclaz

This may help too: http://www.msfn.org/board/index.php?showtopic=25365 the GUI tool is not online anymore, but it can be found on the Wayback machine: http://web.archive.org/web/20061207205837/...ADS/BOOTINI.zip Usual "final 00" patching is needed with some zip utilities: http://www.boot-land.net/forums/index.php?...=2681&st=24 jaclaz

Newish app (for Mass Storage): http://www.911cd.net/forums//index.php?sho...c=22523&hl= Driver Import PE usually works allright. Maybe reviewing this thread: http://www.boot-land.net/forums/index.php?showtopic=5213 you may find a step you missed. jaclaz

May I remind all about Rule #1a? : http://www.msfn.org/board/index.php?showtopic=18408 I can see some posts heading in a direction dangerously nearing the border-line.... jaclaz

Definitely Vista/Server 2008, tested and working, cannot say about Windows 7, but since its setup is similar to Vista it will probably work, but really cannot say. jaclaz

You need to the integrate the appropriate Mass storage driver. Easier would be using Driverpacks: http://unattended.msfn.org/unattended.xp/view/web/37/ http://driverpacks.net/DriverPacks/overview.php If your device is supported (but MOST are ). http://driverpacks.net/DriverPacks/DriverPack.php?pag=m jaclaz

Almost, but not quite, completely unlike related to the number of failing drives? http://blogs.barrons.com/techtraderdaily/2...r-was-terrible/ http://blogs.barrons.com/techtraderdaily/2...sets-10-layoff/ http://finance.yahoo.com/news/Seagate-Tech...s-14027067.html jaclaz

ilko was working on the x64 install some time ago, he found a way to have it working using this workaround: http://blogs.sepago.de/nicholas/2008/03/13...on-windows-x64/ Cannot say if the mod has been "ported" to USB_MultiBoot_10. You may want to (momentarily) forget about dual install and USB_Multiboot_10 and restart from scratch with just the x64 install using this: http://www.msfn.org/board/index.php?showtopic=120444 and, if it works, re-use the same to add the x32 soource. jaclaz

Yes, you use single percentage sign % in command prompt and double %% in batches, I assumed you would have scripted it. jaclaz

Again, just for the record, you can also use the & operator and the PUSHD and POPD commands (though unneeded in this specific case): http://www.ss64.com/nt/pushd.html http://www.ss64.com/nt/popd.html PUSHD E:\autoplay\docs\myfiles & copy *.doc C:\ & POPD jaclaz

Sure it has been done. But they are two separate processes: 1) integrate all needed updates/hotfixes 2) install to USB device 1) Besides nlite: http://www.msfn.org/board/index.php?showforum=129 http://www.ryanvm.net/msfn/ 2) See here (given links in various posts of the thread): http://www.msfn.org/board/index.php?showtopic=119963 particularly those here: http://www.msfn.org/board/index.php?showto...19963&st=23 The original thread+various Tutorials in Dietmar's signature): http://www.911cd.net/forums//index.php?sho...=14181&st=0 and the newish service by marv: http://www.911cd.net/forums//index.php?sho...c=22473&hl= jaclaz

For /F %%A in (myfile.txt) DO cd %%A Though it would be easier to write the whole line: cd c:\windows to a file, give it the .bat or .cmd extension and START it. jaclaz

Just for the record, the /Y switch for the copy command is NOT needed from batch: http://www.ss64.com/nt/copy.html jaclaz

Really, you need to read the given thread: http://www.msfn.org/board/index.php?showtopic=61384 (Yes, LOOONG thread ) To understand what you need to do, the error you are having is just the first of a series that you will get, and that have been found and solved or worked around during the troubleshooting of the batrches/method. Again, using this method: http://www.msfn.org/board/index.php?showtopic=121446 would be simpler. jaclaz

Again, the "game" is played this way: YOU post the required info I try and help you In the meantime, read these: http://www.boot-land.net/forums/index.php?...ic=5397&hl= http://www.boot-land.net/forums/index.php?...ic=5315&hl= http://www.boot-land.net/forums/index.php?...ic=5274&hl= jaclaz

There are other apps : http://tokiwa.qee.jp/EN/Fat32Formatter/index.html jaclaz

The article on Inquirer got his first effects, word is spreading : http://www.theinquirer.net/inquirer/news/3...7200-11-failing http://www.electronista.com/articles/09/01...acuda.failures/ http://i.gizmodo.com/5130702/1tb-seagate-b...-gogo-users-say http://gadgetblips.dailyradar.com/story/se...iling_en_masse/ jaclaz

Most probably the e-mail addresses "reserved" for press only, which can be found here: http://www.seagate.com/www/en-us/about/contact_us/ under "media" could be used in this particular case, CCing them to actual News..... in order to make the people in "communication" aware of the size and gravity of the problem, it is also possible that Seagate officials from the Support did not mention the matter with them.... jaclaz

You simply cannot expect NTLDR and a BOOT.INI pointing to \I386 to load a Windows SETUP. You need to load SETUPLDR.BIN in the \I386 directory to start an XP install. Your best bet is to use grub4dos to do that, and also to exchange the mapping of drives in order to keep the "normal" drive lettering and/or use a migrate.inf file. There are already a couple of related topics: http://www.msfn.org/board/index.php?showtopic=108515 http://www.msfn.org/board/index.php?showtopic=121567 You will need to read the info within the "Install XP from USB" forum: http://www.msfn.org/board/index.php?showforum=157 going through the "historical" thread: http://www.msfn.org/board/index.php?showtopic=61384 Most probably using a PE on the Recovery partition: http://www.msfn.org/board/index.php?showtopic=121446 would be easier and faster to achieve successfully. jaclaz