jaclaz

Well, you cannot just rename them to .png. The 89 50 4E 47 0D 0A 1A 0A in the header is first 8 bytes, you have an "excess header" of 24 bytes: http://en.wikipedia.org/wiki/Portable_Network_Graphics#File_header You need at least to cut it out. jaclaz

The more (or less) probabilities to recover deleted data are pretty much OS independent (and have no real connection with "security" or "reliability") but quite heavily filesystem dependent. Assuming that you use NTFS on both there won't be ANY difference. If - by any chance - you used that "third party utlity" installing it on the actual OS that was running when the files were deleted, you did it wrong , those tools needs always to be used when booted from another OS (possibly also booted from another disk), and you can use the SAME "third party tool" under another XP install to recover files on BOTH a Windows 7 and a XP without any difference worth of note. jaclaz

What will the real programmers (of which there are plenty) drink then? http://uranus.chrysocome.net/ http://uranus.chrysocome.net/coke.htm I assume there are bottles, and no cans. jaclaz

Hey, it 's you that have those programs, personally I would use isoinfo, some info (pardon the pun ) here: http://reboot.pro/12406/ and mkisofs (or oscdimg) to create the .iso. To maybe better clear what I am guessing is that some of the early accessed files are "beyond reach", compare with this: http://www.911cd.net/forums//index.php?showtopic=20248 jaclaz

Wouldn't you also need a cam pointed to each screen? I mean if the number of machines is so big, are you really sure you won't be forcing a resolution, color depth or refresh rate that is not suitable with a video card or monitor among the machines? If I were you I would look into nirsoft's nircmd (setdisplay command+remote or multiremote): http://www.nirsoft.net/utils/nircmd.html jaclaz

You have a queer way of presenting problems, (presuming that people on the board all have a crystal ball to know among the few tens of possible ways and tools you used and choices in them, which exact part is the problem and point you to it by sheer magic..) You particularly do not detail how you actually create the .iso. The NTLDR has limited capbilities when accessing a CDFS filesystem, and as well in the intial phases of SETUP, some LBA addresses might be "unreachable". From your other post I presume you are using MagicIso, a Commercial tool that since 2005: You might want to check the actual LBA addresses of NTDETECT.COM (and of all files it cannot find). About runonce.cmd, even my crystal ball cannot list it properly, so you mught want to post for review. jaclaz

Yep , the idea is that you need NOT download 1.7Gb to read a lousy EULA 10 Kb in size. Expecially if you have a slow connection .... ....and a hard disk filled up to the brim..... Thanks for the basket, I am sure that it will prove useful. jaclaz

Good. jaclaz

What you report is the output of the LBA0 fix. If the drive is not detected, you have a BSY problem (and the "cure" you applied for LBA0 won't work). If the drive is detected BUT with "0 capacity", you have a LBA0 problem (and the "cure" you applied should work) It's just like you had a cold and instead of taking an aspirin and going to bed you bandaged your left little finger: NOT really effective in the case of a cold, but not that bad in case of a cut in left little finger. BSY problem->BSY cure LBA0 problem->LBA0 cure jaclaz

Easy Instructions: get the WAIK open the downloaded .iso with 7-zip find in root file WAIK_License.rtf open it in Wordpad read it Easier , download the attached, coming from the KB3AIK_EN.iso I have. Cannot say if it has changed in the currently downloadable version: http://www.microsoft.com/downloads/en/details.aspx?familyid=696DD665-9F76-4177-A811-39C26D3B3B34&displaylang=en If you want to check without downloading the whole .iso, see here: http://reboot.pro/13049/ jaclaz WAIK_License.zip

I don't really want to prove you wrong , when dealing with the good MS guys there is always something that is simply inexplicable. Have you ever read the actual ImageX/wim related dll's license (yes, the one everyone has broken, one time or the other) http://www.911cd.net/forums//index.php?showtopic=19355&st=132 and my carpenter's comparison? http://www.911cd.net/forums//index.php?showtopic=19355&st=134 I'll need to upgrade to a bigger basket.

Yep, but WHICH version is it? Just for the record, the "normal" way is to download the FULL Redist : http://www.microsoft.com/downloads/details.aspx?FamilyID=886acb56-c91a-4a8e-8bb8-9f20f1244a8e&DisplayLang=it this one is version 9.25.1476 and from it get the dxsetup.exe (italian): http://microsoft-it.confusenet.com/showthread.php?t=280435 This one: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=04AC064B-00D1-474E-B7B1-442D8712D553 is version 9.27.1734 It has to be cleared whether this 9.29.1962: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=3B170B25-ABAB-4BC3-AE91-50CEB6D8FA8D is true: And if consequently the fact that in this 9.28.1886: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0cef8180-e94a-4f56-b157-5ab8109cb4f5 Windows 2000 is not mentioned does NOT mean that it isn't supported. And/or which exactly is latest version supporting Win2K. jaclaz

Well, it's not that difficult (the base concept I mean). You are whining about not being able to image because you have an image (actually a set of images) that is/are hardware dependent.. Offline Sysprep promises: http://www.911cd.net/forums//index.php?showtopic=22064 Doesn't it look a lot like a solution to the problem? jaclaz

Guess why grub4dos was developed? Here: http://reboot.pro/forum/66/ Get a grasp of the whereto: http://reboot.pro/14/ And of the guide: http://reboot.pro/5187/ http://diddy.boot-land.net/grub4dos/Grub4dos.htm First thing. jaclaz

Well, kids today, my first one was a ZX-80 which you had to solder components yourself.... ...why, in my day ..... http://reboot.pro/1908/ .... and we LIKED it! jaclaz

See also this approach: http://forums.pcper.com/showthread.php?t=444831 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