lilas

Member
  • Content count

    34
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lilas

  1. @jaclaz Thank you. The referenced tools from Nir Sofer look very good, I will try them.
  2. @jaclaz Thank you for the interesting detailed explanations. For a plain man point of view, the registry entries are really a mess :-). > After a lot of inserting and removing sticks, the Registry gets cluttered and should be cleaned. I believe this is my problem, since I plug/unplug a lot of USB keys and hard disks. Is there a tool for this, or I have to do it manually, and how?
  3. I finally find a bypass to my problem by making all removable USB key into fixed disk, using Hitachi microfilter. http://www.boot-land.net/forums/index.php?showtopic=7512
  4. I found this problem which is for me related to my original problem. Strange problem with MountedDevices, drive letter not memorized I have two USB keys of same manufacturer, same model, same capacity. I partitioned them and formatted them with FAT32. USB_key_a and USB_key_b are removable USB keys. Each has its own disk signature (seen with mbrfix /drive n readsignature), different volume lables, and of course different serial numbers. 1) USB_key_a plugged in USB_port1 : drive letter set to M: 2) USB_key_b plugged in USB_port1 : drive letter seen as M: ! So I changed to N:. Unplug it. 3) USB_key_a re-plugged in USB_port1 : drive letter seen as N: (instead of M: as set in step 1) !). Reset drive letter to M:. Unplug it. 4) USB_key_b re-plugged in USB_port1 : drive letter seen as M: ! So I changed to N:. Keep it plugged. 5) USB_key_a plugged in USB_port2 : drive letter seen as E:, set to M:. Good, so I have both M: and N: active at the same time. So USB_key_a = M:, and USB_key_b = N:. OK, unplug both USB_key_a and USB_key_b. 6) USB_key_b plugged in USB_port2 : drive letter seen as M: ! So it looks like XP depends also on the USB port number for assigning drive letter? Other quesions: 1) What are the meaning of the entries in MountedDevices? It looks like non removable disk has shorter GUID values (disk signature + checksum in boot sector?) than removable devices? What are the meaning of values stored for GUID for removable disks? Same question for DosDevices data for removable disk (like M: and N: are much longer). 2) Why there is a confusion between M: and N: drive letter? I also experience XP disk management hang (MMC) at opening when there are seemingly confusion on the drive letters. And in some cases a BSOD with stop code 0x0A IRQ_NOT_LESS_OR_EQUAL on plugging these USB keys. Thank you in advance. Following is sample of my MountedDevices. G: is CD-ROM, M: and N: are removable USB keys, C: D: F: are internal fixed disks, the other are USB HDD. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices] "\\DosDevices\\C:"=hex:3a,19,a2,c3,00,10,10,71,02,00,00,00 "\\DosDevices\\D:"=hex:3a,19,a2,c3,00,a0,96,3a,0f,00,00,00 "\\DosDevices\\F:"=hex:3a,19,a2,c3,00,d4,1f,02,0a,00,00,00 "\\DosDevices\\H:"=hex:85,51,9f,ed,00,7e,00,00,00,00,00,00 "\\DosDevices\\J:"=hex:67,74,b7,24,00,cc,4d,51,13,00,00,00 "\\DosDevices\\K:"=hex:67,74,b7,24,00,34,93,43,73,00,00,00 "\\DosDevices\\L:"=hex:67,74,b7,24,00,ac,f1,56,16,00,00,00 "\\DosDevices\\P:"=hex:67,74,b7,24,00,c4,1b,1c,04,00,00,00 "\\DosDevices\\Q:"=hex:67,74,b7,24,00,7e,00,00,00,00,00,00 "\\DosDevices\\R:"=hex:f8,7d,df,dd,00,7e,00,00,00,00,00,00 "\\DosDevices\\S:"=hex:7b,17,c6,1f,00,7e,00,00,00,00,00,00 "\\DosDevices\\T:"=hex:f4,63,90,70,00,82,00,00,00,00,00,00 "\\DosDevices\\W:"=hex:67,74,b7,24,00,de,42,4f,0e,00,00,00 "\\DosDevices\\X:"=hex:9b,ba,df,dd,00,7e,00,00,00,00,00,00 "\\??\\Volume{910999dc-7ba2-11de-95ed-806d6172696f}"=hex:3a,19,a2,c3,00,10,10,\ 71,02,00,00,00 "\\??\\Volume{910999dd-7ba2-11de-95ed-806d6172696f}"=hex:3a,19,a2,c3,00,d4,1f,\ 02,0a,00,00,00 "\\??\\Volume{910999de-7ba2-11de-95ed-806d6172696f}"=hex:3a,19,a2,c3,00,a0,96,\ 3a,0f,00,00,00 "\\??\\Volume{910999e0-7ba2-11de-95ed-005056c00008}"=hex:f4,63,90,70,00,82,00,\ 00,00,00,00,00 "\\??\\Volume{910999e1-7ba2-11de-95ed-005056c00008}"=hex:67,74,b7,24,00,7e,00,\ 00,00,00,00,00 "\\??\\Volume{910999e2-7ba2-11de-95ed-005056c00008}"=hex:67,74,b7,24,00,c4,1b,\ 1c,04,00,00,00 "\\??\\Volume{910999e3-7ba2-11de-95ed-005056c00008}"=hex:67,74,b7,24,00,de,42,\ 4f,0e,00,00,00 "\\??\\Volume{910999e4-7ba2-11de-95ed-005056c00008}"=hex:67,74,b7,24,00,cc,4d,\ 51,13,00,00,00 "\\??\\Volume{910999e5-7ba2-11de-95ed-005056c00008}"=hex:67,74,b7,24,00,ac,f1,\ 56,16,00,00,00 "\\??\\Volume{910999e6-7ba2-11de-95ed-005056c00008}"=hex:67,74,b7,24,00,34,93,\ 43,73,00,00,00 "\\??\\Volume{910999e9-7ba2-11de-95ed-005056c00008}"=hex:9b,ba,df,dd,00,7e,00,\ 00,00,00,00,00 "\\??\\Volume{910999eb-7ba2-11de-95ed-005056c00008}"=hex:f8,7d,df,dd,00,7e,00,\ 00,00,00,00,00 "\\??\\Volume{910999ec-7ba2-11de-95ed-005056c00008}"=hex:7b,17,c6,1f,00,7e,00,\ 00,00,00,00,00 "\\??\\Volume{910999ee-7ba2-11de-95ed-005056c00008}"=hex:f7,7d,40,70,00,7e,00,\ 00,00,00,00,00 "\\??\\Volume{091f4b14-7bf9-11de-95ef-005056c00008}"=hex:25,89,08,6e,00,7e,00,\ 00,00,00,00,00 "\\??\\Volume{f3873349-7d0a-11de-95f1-005056c00008}"=hex:5c,00,3f,00,3f,00,5c,\ 00,53,00,54,00,4f,00,52,00,41,00,47,00,45,00,23,00,52,00,65,00,6d,00,6f,00,\ 76,00,61,00,62,00,6c,00,65,00,4d,00,65,00,64,00,69,00,61,00,23,00,37,00,26,\ 00,32,00,65,00,32,00,33,00,34,00,34,00,35,00,38,00,26,00,30,00,26,00,52,00,\ 4d,00,23,00,7b,00,35,00,33,00,66,00,35,00,36,00,33,00,30,00,64,00,2d,00,62,\ 00,36,00,62,00,66,00,2d,00,31,00,31,00,64,00,30,00,2d,00,39,00,34,00,66,00,\ 32,00,2d,00,30,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,\ 00,62,00,7d,00 "\\??\\Volume{f387334a-7d0a-11de-95f1-005056c00008}"=hex:5c,00,3f,00,3f,00,5c,\ 00,53,00,54,00,4f,00,52,00,41,00,47,00,45,00,23,00,52,00,65,00,6d,00,6f,00,\ 76,00,61,00,62,00,6c,00,65,00,4d,00,65,00,64,00,69,00,61,00,23,00,37,00,26,\ 00,62,00,30,00,35,00,62,00,30,00,33,00,64,00,26,00,30,00,26,00,52,00,4d,00,\ 23,00,7b,00,35,00,33,00,66,00,35,00,36,00,33,00,30,00,64,00,2d,00,62,00,36,\ 00,62,00,66,00,2d,00,31,00,31,00,64,00,30,00,2d,00,39,00,34,00,66,00,32,00,\ 2d,00,30,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,\ 00,7d,00 "\\DosDevices\\G:"=hex:5c,00,3f,00,3f,00,5c,00,49,00,44,00,45,00,23,00,43,00,\ 64,00,52,00,6f,00,6d,00,48,00,4c,00,2d,00,44,00,54,00,2d,00,53,00,54,00,5f,\ 00,44,00,56,00,44,00,52,00,41,00,4d,00,5f,00,47,00,53,00,41,00,2d,00,55,00,\ 32,00,30,00,4e,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,\ 00,5f,00,5f,00,5f,00,5f,00,5f,00,5f,00,48,00,52,00,30,00,35,00,5f,00,5f,00,\ 5f,00,5f,00,23,00,34,00,26,00,31,00,39,00,39,00,61,00,63,00,62,00,61,00,33,\ 00,26,00,30,00,26,00,30,00,2e,00,31,00,2e,00,30,00,23,00,7b,00,35,00,33,00,\ 66,00,35,00,36,00,33,00,30,00,64,00,2d,00,62,00,36,00,62,00,66,00,2d,00,31,\ 00,31,00,64,00,30,00,2d,00,39,00,34,00,66,00,32,00,2d,00,30,00,30,00,61,00,\ 30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7d,00 "\\DosDevices\\M:"=hex:5c,00,3f,00,3f,00,5c,00,53,00,54,00,4f,00,52,00,41,00,\ 47,00,45,00,23,00,52,00,65,00,6d,00,6f,00,76,00,61,00,62,00,6c,00,65,00,4d,\ 00,65,00,64,00,69,00,61,00,23,00,37,00,26,00,62,00,30,00,35,00,62,00,30,00,\ 33,00,64,00,26,00,30,00,26,00,52,00,4d,00,23,00,7b,00,35,00,33,00,66,00,35,\ 00,36,00,33,00,30,00,64,00,2d,00,62,00,36,00,62,00,66,00,2d,00,31,00,31,00,\ 64,00,30,00,2d,00,39,00,34,00,66,00,32,00,2d,00,30,00,30,00,61,00,30,00,63,\ 00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7d,00 "\\DosDevices\\N:"=hex:5c,00,3f,00,3f,00,5c,00,53,00,54,00,4f,00,52,00,41,00,\ 47,00,45,00,23,00,52,00,65,00,6d,00,6f,00,76,00,61,00,62,00,6c,00,65,00,4d,\ 00,65,00,64,00,69,00,61,00,23,00,37,00,26,00,32,00,65,00,32,00,33,00,34,00,\ 34,00,35,00,38,00,26,00,30,00,26,00,52,00,4d,00,23,00,7b,00,35,00,33,00,66,\ 00,35,00,36,00,33,00,30,00,64,00,2d,00,62,00,36,00,62,00,66,00,2d,00,31,00,\ 31,00,64,00,30,00,2d,00,39,00,34,00,66,00,32,00,2d,00,30,00,30,00,61,00,30,\ 00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7d,00
  5. @jaclaz > And the little app by Uwe Sieber: didn't work? I did not try it although it seems interesting. Because it is not "portable" : it requires an installation with new service created, and some setting which is not common (machine-specific)
  6. @jaclaz > I would rather look for problems in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USBSTOR, but of course I may be completely off-track. Thank you for your reply. I looked into this key and did not see anything abnormal, there are entries for vendor id/product id for the USB HDD/keys I plugged in the past. How can I see that there is a problem? Do you know the meaning of MountedDevices entries type 2 (beginning with #)? I did not see any relationship with other entries types. For old entries of type 2 that are not found in type 4, I assume I can safely delete them. By the way, the only workaround I found to change drive letter is to rename the key of type 4 (changing for example \DosDevices\E: into \DosDevices\U: , instead of using the mmc/disk management that would hang.
  7. Hello, I have the following problem: I am running XP SP3. 1) As soon as I plug an USB Hard disk, everything is OK (drive letter assigned, files access etc...). I can start disk management (mmc, dmremote, dmadmin), but I cannot change the drive letter assigned to the USG hard disk. It hangs. I have to unplug by force the USB HDD, then kill the mmc.exe/dimremote.exe to recover). The problem is reproducible at will. 2) As soon as I plug an USB key, , everything is OK (drive letter assigned, files access etc...). But I cannot start disk management, it hangs forever. I have to close the disk management window, and again kill mmc.exe and dmremote.exe. In the registry, under HKLM\System\MountedDevices I have 4 types of entries : 1) Default 2) Entries that look like #{10bd8f26-4567-11de-9d7d-005056c00008} (REG_BINARY) 3) Entries that look like \??\Volume{10bd8f25-4567-11de-9d7d-005056c00008} (REG_BINARY) 4) Entries that look like \DosDevices\C: (REG_BINARY). Questions: Entries type 1) and 4) seem OK for me. For type 4), the binary value is apparently the disk signature of the HDD/USB HDD with the assigned drive letter. 1) What is the meaning of entries type 2) and 3)? 2) Can I safely remove all entries of type 2) and 3) ? Could this fix my original problem? Thank you.
  8. Thank you for your hint. The problem is now fixed. Explanations: I used first a removable USB key with the program. Once it works, I copied all the files to a USB HDD and rerun the program which correctly detects the fixed USB HDD. By pressing GO there are 3 choices. I chose the SYNC option (this is the problem): this option does NOT update the txtetup.sif file, even if I delete it. From your post I use the third option (Cancel button) to delete the two $WIN_NT$.~BT and $WIN_NT$.~LS directories. This time the txtetup.sif is created and has rdummy.sys and now it works. Suggestion: maybe txtsetup.sif should always be updated regardless of the option chosen ? Other question : I use USB HDD key with multiboot capability. The program did patch setupldr.bin to avoid collision with /minint/setupldr.bin (UBCD4Win) and txtsetup.sif at root. I also have ERD commander 2005/2007 setupldr.bin that was patched to resides inside \ERDC and \ERD7 directory respectively. Now it no longer works due to presence of txtsetup.sif at root. I assume I have to patch some specific location of txtsetup.sif to notsetup.sif ? Edit: answer to my own question: yes, one occurrence of txtsetup.sif has to be changed to notsetup.sif to avoid collision.
  9. Thank you, but I did not see concretly how to add the rdummy.sys to make it works. I did check the option to force removable disk but with bad result. Does the program do anything for me? Could you please provide more details, thank you.
  10. Hello, I tried WinSetupFromUSB version 0.2.1 and it works very well. One question : if I use an USB HDD instead of an USB key, the USB HDD is seen as fixed disk, and on XP setup the internal IDE hard disk where XP will be installed to as seen as D:. Does it means that after installation D: is the system drive letter ? How it would happen if I remove the USB HDD and boot from the internal disk? I would like to have C: as system drive for the XP to be installed to the internal disk. Is it possible? Thank you.
  11. This is not correct. Two examples: 1) Linux: USB stack is loaded using first BIOS USB with initrd/kernel (less than 5MB). Then the USB stack uses protected-mode USB 2.0 to exploit the hardware in high USB 2.0 speed. 2) XP/Vista: as with Linux, but without RAM disk in normal booting. This explains also slow boot on some machines with BIOS USB 1.x booting (although with USB2.0-hardware capable). Then afterwards the loaded OS will exploit the USB2.0 through drivers.
  12. @Chozo4 Thank you for all your replies. I used the Maximum-Decim Native USB drivers version 3.3. How can I find the 2.24 drivers version? Hotplug is not a requirement since probably can plug them before booting. What I expect is to be able to boot form USB hard disk, and use it USB 2.0 speed. Thank you in advance.
  13. Hello, Does anybody succeed in booting Win98SE (with Maximum-Decim Native USB 2.0 drivers) from external USB hard disk ? With the original drivers, I can get it boots OK, but only with USB 1.1 speed and without any hot plug/unplug recognition. Once applied the USB 2.0 drivers, Win98SE hang after few disk accesses at logo screen. No problem when I pulled back the hard disk out of its USB enclosure and put it back as internal IDE hard disk.
  14. @spacesurfer Thank you for your tutorial. What I understand: XP (hd0,0), Vista is (hd0,1) and BartPE is (hd0,2). I have a question : Since E: is active, when booted with grub4dos in the menu.lst I did not see the makeactive directive for (hd0,0) partition. So when booting Vista (hd0,0), C: will not be assigned to (hd0,0) but to (hd0,2). Is is correct? And then it would cause problem to Vista. Maybe same problem when booting from XP (hd0,1). Am I missing something?
  15. Acronis has a product called Acronis® Universal Restore : http://www.acronis.com/enterprise/products...al-restore.html