jaclaz

Direct link to the home page of the app: http://www.softarch.com/EN/Product/ReadDVDWin.html Interesting info! jaclaz

And I was the one accused to use pipster as a guinea pig! jaclaz

Basically 2K/XP/2003 use a "ControlSet". When booting one of the available ControlSet's is chosen, based on the value of the Select key. The chosen ControlSet is then "mirrored" (actually it is a kind of redirection/hard-link, but the effect is the same as it was a mirror) as CurrentControlSet and the latter "mirror" is actually used. Your Select key : [HKEY_LOCAL_MACHINE\SYSTEM\Select] "Current"=dword:00000006 "Default"=dword:00000006 "Failed"=dword:00000005 "LastKnownGood"=dword:00000007 A "normal" Select key : [HKEY_LOCAL_MACHINE\SYSTEM\Select] "Current"=dword:00000001 "Default"=dword:00000001 "Failed"=dword:00000000 "LastKnownGood"=dword:00000002 In normal operation, ControlSet001 is always used, in case it fails due to corruption or whatever reason, you are given when booting the option to choose "Last Known Good" (or "Ultima configurazione sicuramente funzionante"), if you choose that, then try again booting normally and it doesn't boot, the key changes to: And a new ControlSet, ControlSet00n+3, copy of the "last known good" or n+2 is created. Usually when the above happens, it is time to understand what caused the failure and fix the Registry. However his would be outside the scope of the thread, check these if you are interested: http://www.pcreview.co.uk/forums/thread-3161118.php http://support.microsoft.com/kb/102984/ http://support.microsoft.com/kb/302829/ http://www.geocities.com/nafiton/l_m_sys_set_services.html Back to your guinea pig duties : You can delete allright the keys: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}\##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b} HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\##?#STORAGE#RemovableMedia#8&141a0a73&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} in each 00n ControlSet you can find them. DO NOT delete the whole: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\ DO NOT delete the whole: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}\ DO NOT delete the whole: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00n\Control\DeviceClasses\{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}\ jaclaz

Rest assured , I rarely post incorrect information. Of course 7-zip IS NOT intended as a "virtual ROM emulators and the software that are able to open and edit image files", but if you just need to extract (or peek at) either the El-Torito floppy Emulation image or to the no-emulation bootsector it's the easiest way. FYI, check Peazip directories.... Yes, you ALREADY have 7-zip (command line version) on your PC, and you don't even know that! Peazip is simply a "collection" of various compression/uncompression tools, and while having some nice features is not, like the full 7-zip, also a (dual pane) file-manager. jaclaz

Coming from a guy that installed 2K in March 2003 and ran it 24/7/365 since without EVER reinstalling it may sound brutal, but you have some problems on that PC. ControlSet005 ControlSet006 ControlSet007 A "normal" Windows has just ControlSet001 and ControlSet002, in some rare occasions of failure of one ControlSet I have seen ControlSet003 and ONCE in my life ControlSet004! Please check/post contents of key: HKEY_LOCAL_MACHINE\SYSTEM\Select jaclaz

A couple of additions: Datarescue ddrescue: http://www.boot-land.net/forums/index.php?showtopic=7783 Homepage: http://www.datarescue.com/photorescue/v3/drdd.htm SILinux dd for windows: http://www.boot-land.net/forums/index.php?showtopic=7786 Homepage (Japanese): http://www.si-linux.co.jp/wiki/silinux/ind...hp?DDforWindows Via Google Translate: http://translate.google.com/translate?u=ht...en&ie=UTF-8 jaclaz

Or, as said two posts before, with "normal" Freeware 7-zip. jaclaz

We have plenty of BOTH. Right questions , wrong place to ask : http://www.msfn.org/board/index.php?showforum=157 Basically your approach WON'T work, but there are several alternate methods: http://www.msfn.org/board/index.php?showtopic=111406 http://www.msfn.org/board/index.php?showtopic=120444 http://www.msfn.org/board/index.php?showtopic=121446 and if you have a U3 stick: http://www.msfn.org/board/index.php?showtopic=121502 (the error 18 is probably due to \I386\ vs. \minint\ path, but it won't work anyway even if you fix it, whilst all the above are tested and working, just choose the one that suits you better) jaclaz

Which one? The hacked bootsector or the chainloading of grldr.mbr ? However, happy it worked. jaclaz

Next time, open the .iso with 7-zip and check the contents of the [bOOT] folder you will see. Thanks for making that page. Besides being very clear, I like the use of large, friendly letters. jaclaz

Doesn't IMDISK work normally on a WinPE 1.x? http://www.ltr-data.se/opencode.html http://www.boot-land.net/forums/index.php?showforum=59 http://www.911cd.net/forums//index.php?showtopic=20203 jaclaz

Which means obviously that the proggie did not remove the "something" that makes it get the "wrong" ParentID. Can you do a Regedit search on that machine Registry for string: And post results, or better yet, get Regfind.exe http://www.petri.co.il/download_free_reskit_tools.htm and run: regfind "8&141a0a73&">foundreg.txt You should get something similar to this (I used "7&2c889678&"): \Registry Machine SYSTEM ControlSet001 Control DeviceClasses {53f5630a-b6bf-11d0-94f2-00a0c91efb8b} ##?#STORAGE#RemovableMedia#7&2c889678&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b} DeviceInstance = STORAGE\RemovableMedia\7&2c889678&0&RM # SymbolicLink = \\?\STORAGE#RemovableMedia#7&2c889678&0&RM#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b} {53f5630d-b6bf-11d0-94f2-00a0c91efb8b} ##?#STORAGE#RemovableMedia#7&2c889678&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} DeviceInstance = STORAGE\RemovableMedia\7&2c889678&0&RM # SymbolicLink = \\?\STORAGE#RemovableMedia#7&2c889678&0&RM#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} Enum USBSTOR Disk&Ven_Generic&Prod_USB_CF_Reader&Rev_1.01 058F312D81B&1 ParentIdPrefix = 7&2c889678&0 It is possible that the tool only clears the \USBSTOR\? jaclaz

The DMF and "1.68" floppy format was one of the really pesky ones. Winimage can handle both: (through wayback machine as "real page" is giving problems to me right now): http://web.archive.org/web/20080111111608/...lp/wini1a1y.htm A suitable app to format them properly is DCOPY: http://users.telenet.be/jbosman/applications.html There is a "vfloppy" floating around: http://www.911cd.net/forums//index.php?showtopic=7281 http://www.911cd.net/forums//index.php?showtopic=10878 which I seem to remember was loosely connected with the app you can find here: ftp://ftp.symantec.com/public/english_us_...s/pq/utilities/ ftp://ftp.symantec.com/public/english_us_...vfd_folders.exe Which is actually a virtual floppy disk driver for 9x. Please understand that the above has NO docs/instructions and it's licensing status is UNKNOWN. (your mileage may vary :whistling:) Cannot say if it is compatible with DMF format. jaclaz

drivecleanup -t (list all devices that will be "affected" by the command - just to be sure) then drivecleanup (without parameters), that will get rid of: jaclaz

Do you normally chainload the loader or a 2048 bytes CD bootsector invoking the loader? I mean, what happens if you follow loosely the flyakite's guide: http://flyakite.msfn.org/xpprosp1.htm and change: SETUPLDR.BIN ->GRUB4DOS.BIN (or any 8+3 name) I386->GRUB (or any 4 letter name) And you place a copy of grldr renamed to GRUB4DOS.BIN in directory \GRUB\ ? Do read also the issues that may happen when renaming grldr: http://diddy.boot-land.net/grub4dos/files/grldrmbr.htm Or try chainloading grldr.mbr instead of grldr directly from CDSHELL. BTW, just for the record, grub4dos is CaSe SeNsItIvE on CDFS. jaclaz

So by detecting the latter we may know that migrate.inf drive lettering may not be applied and by putting in it multiple entries for RemovableMedia#7 , 8 (any others used for USB mass storage devices?) we might get around similar issues. Yep, but the "ID" is not the "ParentIDPrefix". I would say that the issue at hand is not related to Serial (or lack of it) or maybe by something connected to it but not really "it". There are a number of entries in the USB_rep.txt that look suspicious, as they have no "ParentIDPrefix", some have "autogenerated-second-letter-&" ID's, some don't. Thanks for the reminder. We also learned something new, so I guess we are even. jaclaz

NO, if you are OK with XP on D:\ all you need to do is to check you have NTLDR + NTDETECT.COM + BOOT.INI on the Active partition and edit your BOOT.INI to reflect where XP is. See here: http://www.msfn.org/board/index.php?showtopic=25365 http://www.msfn.org/board/index.php?showtopic=33030 The DX21 GUI app can still be found through the Wayback Machine: http://www.boot-land.net/forums/index.php?...ic=210&st=1 If you don't want it on D:\ you will need to reinstall. jaclaz

I am not familiar (anymore ) with CDSHELL. You should be able to add it as you would add SETUPLDR.BIN or NTLDR. grldr should be chainloadable exactly like them. Otherwise, try chainloading from CDSHELL NTLDR and add to BOOT.INI a line C:\grldr="grub4dos" jaclaz

I guess we could have saved a lot of bandwith if pipster just listed the only USB device available in a 2.43 Km radius from the PC he NEVER connected to it. 23rd October 2008 must have been a busy day. I would try to disconnect all USB devices and delete all keys under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USBSTOR\ Then try reconnecting one stick and see what happens. Maybe something made the 7& being available and start with 8& and 9&.... jaclaz

As expected. the .cmd runs allright, but it cannot find any file and closes without doing anything. A more suitable .cmd: for /f "tokens=3" %%i IN ('reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v "SourcePath" ^| findstr "REG_SZ"') do set SOURCE=%%i ::Adjust following to your actual path SET RelPath=\$OEM$\$1\INSTALL ::Adjust the above to your actual path "%Source%%RelPath%\SVCPACK\IRFA.EXE" "%Source%%RelPath%\SVCPACK\MP3D.exe" "%Source%%RelPath%\SVCPACK\QIP.EXE" "%Source%%RelPath%\SVCPACK\MPUI.EXE" "%Source%%RelPath%\SVCPACK\Skype40.exe" "%Source%%RelPath%\SVCPACK\GIMP.EXE" "%Source%%RelPath%\SVCPACK\XNVF.EXE" "%Source%%RelPath%\svcpack\OpenOffice.org3.0.1.exe" "%Source%%RelPath%\SVCPACK\PAIN.EXE" "%Source%%RelPath%\SVCPACK\AV9_Silent.exe" "%Source%%RelPath%\SVCPACK\PDFC.EXE" EXIT jaclaz

Didi you try the "usual" troubleshooting steps, using other filesystems? FAQ #10: http://home.graffiti.net/jaclaz:graffiti.n...SB/USBfaqs.html Try using the newish app by wimb: http://www.boot-land.net/forums/index.php?...5306&st=196 and/or the one by steve6375: http://www.boot-land.net/forums/index.php?showtopic=7739 IF nothing of the above works: Choose one, and only one of your sticks. Get Hdhacker and save the MBR (first sector of PhysicalDrive) and bootsector (first 16 sectors of Logicaldrive if NTFS, just one if FAT16 or FAT32): Compress the two files together and attach the archive. jaclaz

Good catch! I have a Desktop with a multicard reader and everything is #7 type. @pipster You may want to try running this thingie: http://sourceforge.net/projects/usbhistory/ as follows: usbhistory.exe>C:\USB_rep.txt and post the USB_rep.txt jaclaz

@nai22 How do you know if the .cmd is not executed? The whole .cmd is dependent upon a "conditional" variable definition (depending of a string in Registry) and has no error control, thus if the for loop returns an empty string and the SOURCE varaible is not defined it won't ever work. Edit it as follows: and see what happens. Whatever value SOURCE may get, the resulting path will be: <whatever>I386\SVCPACK\ which can NEVER be the right value: U:\$WIN_NT$.~LS\$OEM$\$1\INSTALL jaclaz

Who isn't? Seriously, your choice: Maximum Decim's nusb: http://www.msfn.org/board/index.php?showtopic=43605&hl= Another way: http://www.msfn.org/board/index.php?showtopic=99220&hl= http://www.boot-land.net/forums/index.php?showtopic=2411 jaclaz

Sure , there isn't any. Open a Console Window, (Start->Run->cmd.exe-> click OK or Start>Programs->Accessories->Command Prompt) and type in it: and press [ENTER]. A C:\dir.txt file will be created containing the output of the command dir /a /s i.e. a complete listing of files and directories on the stick. jaclaz