jaclaz

You are welcome. After all it was easier than what I would have thought. jaclaz

WHICH MBR's? Did you run MBRFIX? Start again, run the HP formatting utility and post the MBR and bootsector, extracted with hdhacker, after running it. jaclaz

basically a .inf file is an installer script, that adds the relevant keys to the Registry, copies files to system directories, etc. Read this article (.inf files explained in a simple, effective way ): http://www.wd-3.com/archive/InfFiles.htm You have to browse the said .inf files (Notepad will be enough) and check that you have in your system and/or appropriate source the files mentioned in them, optionally you can use this "specific" experimental app: http://www.boot-land.net/forums/?showtopic=3960 then you simply double-click the .inf file. Be warned that it will be a long and prone to errors procedure.... jaclaz

or simply open it in 7-zip.... jaclaz

The "main" related files should be: ptpusb.dll ptpusd.dll ptppusb.inf sti.inf sti.dll stillcam.inf it's a looong shot, but you can try checking all references in said *.inf files and try installing them. Also you can build TWO nlited .iso's, from the same source, one with NO removed items, and one with ONLY the Digital Cameras support removed, and analyze the differences.... jaclaz

FYI, something can be done with 16 bit apps, too : http://www.boot-land.net/forums/?showtopic=5105 jaclaz

I wouldn't be so "catastrophic". What I would do (assuming that you anyway have a complete and recent backup): 1) Change the drive cable (yes, errors in event viewer about a bad data block can be caused by the cable or contacts) or at least try re-seating it at both ends 2) run CHKDISK 3) run CHKDSK /R But, BEFORE the above: To identify the drive, all you need to know is that first hard disk is \Harddisk0, so the one you have problems should be your second one, but it can also be your CD or DVD drive: http://www.tek-tips.com/viewthread.cfm?qid...6661&page=4 Which drive/partition has letter D:\ in your system? By comparing the output of MOUNTVOL command with that of VLM (part of the DSFOK toolkit): http://members.ozemail.com.au/~nulifetv/freezip/freeware/ you can make sure which is which. But the error could also be due to a "bad" driver, you should use the HD manufacturer utility to check the drive, usually they run from a bootdisk and directly access the drive, so that if the HD pases the check, it means that it is something else (driver or however software) that is causing the problem. jaclaz

Most probably you chose a "wrong direction" when running the batch, in one of the choice menus. Please describe which choices you chose or re-run the batch jolting them down and post them. Also, you could upload the log file. jaclaz

I actually had the feeling you were up to something..... ....good work! Making it a sticky.... jaclaz

MI4C, sorry, but I do not understand what you are trying to do. If what you are asking for is to create Virtual hard disks of given size/geometry or "manually" formatting a USB stick, you may find these batches useful MBRBATCH/MKIMG: http://www.boot-land.net/forums/?showtopic=3191 http://www.boot-land.net/forums/?showtopic=5000 Otherwise, can you re-describe what you are trying to do? jaclaz

Try START "Nero" /DC:\Install\Nero\ /WAIT nero.exe or START "Nero" /WAIT nero.exe http://www.ss64.com/nt/start.html be aware of the "Title" and 8.3 naming with /D option problems. jaclaz

Read here: http://www.msfn.org/board/Integration-of-I...ve-t107504.html jaclaz

See if this helps: http://www.msfn.org/board/Edit-txtsetupsif...o-M-t65541.html jaclaz

Some information can be found here: http://www.911cd.net/forums//index.php?showtopic=16381 http://www.msfn.org/board/Cannot-access-CD...P-i-t91907.html The \I386 folder should not be affected by installing a later SP, checking the dates of the files should be enough to make sure of that, the sp3.cab is to be removed from the build, of course. Your mileage may vary OEM's like Dell, HP or Sony have a knack for making non-standard mods that need lots of time to find and fix. jaclaz

For the record, there is a Commercial application said to be capable of "fixing" these kind of problems: http://www.tamedos.com/tame/tamehome.htm I was never able to find a Freeware/Open Source alternative to it. jaclaz

Well, no, it should be additional. @fusan Why don't you try the Reg key on a "normal" XP?, it has always worked. If you use XP SP2, that is. Could it be some KB update? It is definitely documented to work with BartPE, try using this .cmd: http://www.911cd.net/forums//index.php?showtopic=19422 or, another idea, maybe the thereby referenced app?: http://www.joeware.net/freetools/ http://www.joeware.net/freetools/tools/writeprot/index.htm jaclaz

This reader? http://www.pcworld.com/downloads/file/fid,...escription.html Or this reader driver? http://panasonic.co.jp/pcc/products/en/dri...df.html#POINT02 jaclaz

Wouldn't it be easier on the "other PC" to set up (temporarily) an admin account with same login and password as the "dead" laptop? jaclaz

That's very strange. One of the given links specifiy that this Registry entry is a SP2 feature. Maybe you are running Gold or SP1? Or SP3 and the feature has been removed? jaclaz

(bolding/underlining by me) Hmmm, just for the record: http://www.msfn.org/board/usb-drivers-prob...te-t112812.html http://www.msfn.org/board/Petition-to-Nuhi-t119463.html jaclaz

....and bugs, remember the bugs.... ...though most of the ones we all have are not pertaining the animal world.... jaclaz

Maybe that's it, "00010001" is the "code" for DWORD, the actual value of the key in Registry must be either 0 (write protect disabled) or 1 (write protect enabled). Some reference: http://www.everythingusb.com/writeprotect_registry.html http://www.accessdata.com/media/en_us/prin...otect.en_us.pdf jaclaz

I will , if you tell me what the heck did you use to fdisk/format the stick this time. The MBR code is NOT a standard NT/2K/XP/2003 nor Vista one. Open the stick in beeblebrox, and try setting the "Boot" to 80 (currently it is 00, i.e. you have currently NO partition active). Then, your geometry is once again "gone beserk"! You have: 0B-00-0-1-1-243-32-63-32-15974368 Should be one of the following: 0B-80-0-1-1-243-254-63-63-3919797 0B-80-0-1-1-243-254-63-63-3919797 0C-80-0-1-1-242-254-63-63-3903732 0C-80-0-1-1-242-254-63-63-3903732 SO: 1) Use beeblebrox to write one of the given set of values 2) Eject and reinsert stick 3) Format the stick 4) Run bootsect.exe /nt52 against the stick 5) Copy to the stick NTLDR/NTDETECT.COM/BOOT.INI 6) Try booting from the stick 7) if it does not boot, loop to 2) and try another set of values If it still does not boot, Use MBRFIX: http://www.sysint.no/nedlasting/mbrfix.htm http://www.sysint.no/Download/tabid/162/la...NO/Default.aspx MbrFix /drive <num> fixmbr to fix the MBR code and loop back to 1) Report. jaclaz

Reference is here: http://www.msfn.org/board/How-to-boot-inst...html&st=111 Yours should be: [Version] Signature = "$Windows NT$" [Addreg] ;WriteProtect USB HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",%REG_DWORD%,1 [Strings] ;Handy macro substitutions (non-localizable) REG_SZ = 0x00000000 REG_BINARY = 0x00000001 REG_DWORD = 0x00010001 REG_MULTI_SZ = 0x00010000 REG_SZ_APPEND = 0x00010008 REG_EXPAND_SZ = 0x00020000 or [Version] Signature = "$Windows NT$" [Addreg] ;WriteProtect USB HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",0x00010001,1 Then, you have to BOTH add hiveOEM.inf AND add the entry for it in txtsetup.sif as explained in the referenced post. jaclaz

Wouldn't something like these: http://launchy.net/ http://www.nymtec.com/desktop-lite-thingy be handy? Would they run in PE 2.1? jaclaz