jaclaz

You may want to review Offline Sysprep. Are we talking of XP, right? Here: http://www.911cd.net/forums//index.php?showforum=43 jaclaz

A word of warning. RMPREPUSB is a "generic" tool (works with any USB stick). (and is quite known - a good two thirds of the "install Windows from USB" apps use it ) UFD-Utility (Usb Flash Disk Utilities) © 2008 Ao-LAB (USBest) @ TAIWAN is a "Manufacturer tool" and will ONLY work with sticks that use USBest controllers, and most probably only the UT163 and UT 165. More details here: http://www.911cd.net/forums//index.php?showtopic=14564&st=14 http://www.911cd.net/forums//index.php?showtopic=14564&st=17 DO NOT EVEN THINK to use that utility on a non USBest controller. jaclaz

Wait a minute. It is possible that the problem has NOTHING to do with the BIOS. It may well be connected to the SMART (? ) battery itself (I like to call these DUMB batteries). http://www.technologyquestions.com/technology/mobile-pc-hardware/37706-dell-inspiron-8100-battery-not-charging.html Unfortunately this other possibility goes through a Commercial Software (+DIY hardware): http://sbworkshop.com/ http://be2works.com/ jaclaz

It looks like a nice tool. And it shouldn't be dedicated to "USB only", if I am not mistaken. Let's hope that whoever tests it will be so kind as to (please read as "anyone testing it please do") provide - for the benefit of the less expereinced users - some details on the various available options, and their usage. Usual bothering request to the developer : Any chance that it will ever support command line? (or provide a pre-set in the form of a .ini file?) jaclaz

It seems like that one is an "old" version: http://www.paragon-software.com/home/db-express/ http://www.paragon-software.com/home/db-express/comparison.html jaclaz

The 0xc0000142 seems a lot like an unregistered DLL. A good ol' trick has been in the years to re-register all DLL's. http://registrysnacks.blogspot.com/2008/07/reregister-all-dll-files-with-registry.html It costs nothing, and doesn't make any harm since non-registrable DLL's will simply throw an error. procmon, try this: jaclaz

You must be joking. I was ALREADY there when BOTH IDE and SCSI came out. And yes, we're talking of 1986... the 80's: http://en.wikipedia.org/wiki/1980s http://en.wikipedia.org/wiki/1980s#Electronics_and_computers And yes, I was ALSO already there when the PC came out, my first IBM-compatible PC had two floppies (real floppies, 5.25") and after some time I bought a 20 Mb (yes twenty megabytes) hard disk. jaclaz .

Naah. No conspiracy, They are NOT after you, rest assured. Most probably MS simply "convinced" OEM's that they could give the same kind of money they used to give to the Symantec (Ghost) or PCAngel guys to them instead, having a "native" recovery solution. Most probably the batch is written to be run from the booted system and not from the PE on the Vista DVD. You in the happy bunny basket now? That's good. jaclaz

I beg to disagree , EXACTLY because it may be difficult (or someone would say it's impossible) installing XP on that would be fun. jaclaz

But quite a few deers and a whole lot of inflatable elks decoys (in other words balloons) - that's behind what those d@mn ferrets were hiding , together with many, many other little mammals . jaclaz

Heck , the first rule of " What is behind the green glass door?" is: you DON'T talk about the zoo! And I can see only raccoons and no ferrets in it. jaclaz

No you don't. The code you posted (which maybe you also additionally mis-typed) is NOT the same as the one cuudulieu had. This thread is for 7200.11 ONLY . The above info is written ALL OVER the place, and EXPECIALLY on the read-me-first: The fact that cuudulieu thoughtlessly posted in this thread does not mean that you can do the same. BTW, had you actually read the advice given him at the time, you would have followed it directly: And maybe you could have found this thread: Start a NEW thread, posting the DETAILS of what you did. DO NOT assume that your problem is the same cuudulieu (or anyone else) had or has or will have. If you are lucky, and I mean REALLY lucky, someone will give you (hopefully) a solution. jaclaz

You may want to try the UNofficial SP5. http://www.msfn.org/board/forum/130-hotstream/ http://www.softpedia.com/get/System/OS-Enhancements/Microsoft-Windows-2000-Unofficial-SP5.shtml jaclaz

No. The general idea is that you have a valid source as .iso and the programs "transforms" it for USB usage. If the source misses the drivers, the target also will. (there are other ways/utiluties/whatever to do this) If you are making a "specific DELL (model xy)" USB stick, ONLY meant to install windows XP on the given make/model, you just integrate the specific drivers, otherwise you integrate the Mass Storage section of the BTS driverpacks: http://driverpacks.net/ http://driverpacks.net/docs/beginners-guide-windows-xp (BASE+Mass Storage) so that you will cover most (if not all) common hardware. jaclaz

You don't pay a fee to post links. When giving a reference Post a Link, so that noone has to guess WHAT the heck you have been following. This is the topmost sticky in the Forum (currently): This is the bottommost sticky in the Forum (currently): This is the USB_multiboot.cmd thread: that you are NOT allowed to abbreviate to "MD" or "MB", it is called USB_multiboot.cmd (since you have your new fingers, you have to train them ,and a little exercise in typing FULL names will do them good ) I won't risk finding within the latter thread the "bottom most sticky on the list" WHATEVER have you attempted, forget it. (temporarily). Just get RMPREPUSB here: http://sites.google.com/site/rmprepusb/ http://reboot.pro/7739/ (or from within the WinSetupFromUSB with GUI): and run it as Kelsenellenelvian showed you (if you behave, we will arrange to allow you abbreviating it to Kel ) jaclaz

Have you integrated the SATA drivers for that Dell (if it has a SATA disk)? jaclaz

I take it back , it was a goof, a miss and a misstep (like there are many), but still no guilt nor remorse. jaclaz

There must be something "wrong" with the post counter, you are still at 1. (as it was yesterday, that's why I posted asking, a new user with one post saying it was his second post is "strange" ) Most probably posts made in this Introduce yourself! section do not count. Now I see your "actual" post: jaclaz

Yep, human nature is very similar at all latitudes . You are welcome. jaclaz

you mean no fools ? jaclaz

...and peeps with too much free time, but no noobs... jaclaz

If I were you I would (provided that you have FULLY imaged that drive and have thus a "way back"): unhide the now hidden partition (so that it gets a drive letter) verify that it is first partition of first hard disk verify that i tit there are the \sources\boot.wim and boot.sdi files run the SetAutoFailover.cmd ]with command (provided that the unhidden partition is D:\ ): SetAutoFailover.cmd /target D: /wim /nohide as seen in the given link: http://blogs.msdn.com/b/winre/archive/2007/01/12/how-to-install-winre-on-the-hard-disk.aspx jaclaz

Any source for this procedure? Hot swapping PCB's is not something "usual". See if anything in here: http://files.hddguru.com/download/Datasheets/Samsung%20Service%20Manuals/ can be of use. jaclaz

Good. One more happy bunny in the basket: http://www.msfn.org/board/index.php?showtopic=128727&st=10 I would like to give you an explanation (if there was one). Problem is that I do not know. (or don't know for certain). Possible causes: whatever a different way the BIOS interrogates hard disks (as compared to the way the USB controller does - piloted by the protected mode WIndows driver) a timing problem with spin-up (that could be caused by "sticky" bearings or by something "wrongly set" in the drive firmware) a failing (or partially failing) PC PSU that simply cannot get enough "juice" to the HD motor or PCB at the exact fraction of second it is needed (or again here "sticky" bearings) a failing (or partially failing) PC on-board SATA controller (or other parts of the motherboard) a (partially) botched windows install a defective SATA cable The usual troubleshoot path is to test the device on ANOTHER PC, and see how it "behaves". It is also possible that it was a "transient" problem that once the drive spinned up and was connected through the USB "vanishes" and doesn't happen again.... See above, likely and easyness of fix depends on cause the above are in (supposed) decreasing difficulty/complexity of solution/fix. Actually in these cases the real bad news are that the idea of living next (hopefully ) 50 or more years with someone beside you daily reminding you the time you destroyed all the family's photos and how you were so d@mb and did not make a safe backup on another disk, etc. is really appalling. The good news are that I will tell you only once the THREE golden Rules: BACKUP Backup again on another media While considering the above - and the implications of them, do BACKUP your data jaclaz

Which one is the query? Whatever it is, I can hereby certify that your post above has been read by at least one (human) being. Welcome to the forum. jaclaz