jaclaz

Judging from version history: http://www.peid.info/history.html upgrading 0.94 to the 0.95 version is a "must" jaclaz

Not only "backup", also make sure you can restore. Better be VERY safe than sorry. jaclaz

Back to square #58: http://www.msfn.org/board/problem-installi...74-page-57.html But we have not yet determined, if: the flash device is hosed (and the ONLY way is for you to test it on another computer) OR the 2K Registry is hosed. If #1 using the manufacturer tool may bring it back to pristine state. If #2 using the manufacturer tool is pretty much unuseful/unneeded and risky If BOTH installing the Manufacturer Tool on a "shaky" 2K may do more harm than expected and possibly really "hose" both the device AND OS/Registry. However, all in all you have not much to lose, so I would go on all the way down, AFTER having tried to properly clkean the Registry USB related keys - ALL the steps. Take this thread LOOSELY as a base reference for a typical use of MP Tool: http://www.msfn.org/board/screwed-up-usb-drive-t137990.html though a USBest is talked about there, most manufacturer tools have a similar approach. jaclaz

NO you are not. ANother solution has been given in the thread you referenced. You are looking for a way to perform the Registry shrink solution. I agree that slimming down the Registry is a better and more elegant way, but you cannot slim it down if not up to a certain limit. I would try RegSeeker, but do not expect miracles: http://www.hoverdesk.net/freeware.htm The sizes you report do not seem to me "abnormal". Something you may want to explore would be to reduce the ControlSet002 to the bare minimum, but you are effectively losing (at least partially) an "escape pod" in case of troubles. You sure you have just ControlSet001 and ControlSet002, I had a 2K machines where in time I had as much as 5 ControlSets. Using the nirsoft tool that GrofLuigi suggested, this usually results as a "problematic" area: http://www.pctools.com/guides/registry/detail/1238/ jaclaz

Read the stickies here: http://www.boot-land.net/forums/index.php?showforum=77 particularly this one: http://www.boot-land.net/forums/index.php?showtopic=9201 AND if needed this thread: http://www.boot-land.net/forums/index.php?showtopic=9051 jaclaz

Read flyakite's guide: http://flyakite.msfn.org/ http://flyakite.msfn.org/xpprosp1.htm Editing "setupldr.bin" Alternative: grub4dos or grub4dos+floppy images: http://www.msfn.org/board/please-help-w-du...sp2-t127900.htm Cannot say if everything that applies on 32 bit also works exactly the same on x64. jaclaz

Sure, and as well ANY number of other softwares would do that, point is/was that the numerical data in the usb.if file is Decimal, whilst all the commonly used tools in the "usb field" use Hexadecimal. Maybe useful hint : usbif2csv.cmd|FIND "13FE" Results in: jaclaz

WHICH Linux tool? jaclaz

Maybe the ones I posted a link to? jaclaz

JFYI, and for the record: http://www.boot-land.net/forums/index.php?showtopic=1659 @dencorso NO, the Lexar's don't use Phison chips AFAIK. The BootIt tool appears to be compatible with SMI and Alcor chips, but NOT with USBest or Phison ones: http://www.911cd.net/forums//index.php?showtopic=21850 BUT using the manufacturer tool you can combine allright the two partitions AND make it "Fixed". jaclaz

Just to remain "in-house" : Disk Imaging Software, What else is there? http://www.msfn.org/board/disk-imaging-sof...99.html&hl= jaclaz

You have a "botched" Registry (or stick, but since it works under 9x, this cannot be, and the only way to make sure is to try the stick on another machine which you don't have). Windows 2000 sees the stick as if it were a card reader (No Media). I would bet on the Registry cleaning procedure that I outlined in the other threads. Remove the stick. Before going through ALL the steps listed, try running the nirsoft app: http://www.nirsoft.net/utils/usb_devices_view.html clean ALL USB entries related to Mass Storage devices,. Check again with the other utility: http://www.nirsoft.net/utils/clean_after_me.html Try re-inserting the stick. You may well have also a "botched" USBSTOR.INF or USBSTOR.PNF or whatever. jaclaz

WHICH problem are we talking about right now? The USB stick or the original one? If the USB stick, it looks from the screenshot as it only mounted letter J: (which is "normal" under 2K), can we have a screenshot of it seen in Disk Management? ChipGenius does not identify it "properly" (though it does say it seems like Phison based). 13FE means defintely Phison 1D21 is not one of the known PID's, seemingly. Post a photo of your actual stick, and the brand/model and whatever number or alphanumeric string may appear on it. It is probable that either: USB 2K REL90 (UP10&UP11&UP12) or Phison MPTool MP2232 v1.11.0 (PS223X, AE2263, UP10-UP14) http://www.flashboot.ru/index.php?name=Fil...op=cat&id=6 is the appropriate tool. but DO NOT try using it for the moment. jaclaz

Yep , the idea was to get the Winbuilder .script and see what Registry changes it makes. Winbuilder is after all a batch processor and the Syntax is very similar to "normal" batch. Here is (at first sight ) the relevant part: If,Not,EXISTDIR,%WindowsDir%\System32\Dism,DirMake,%WindowsDir%\System32\Dism If,Not,EXISTDIR,%WindowsDir%\System32\Dism\%WimLanguage%,DirMake,%WindowsDir%\System32\Dism\%WimLanguage% FileCopy,%SourceDir%\sources\Dism.exe,%WindowsDir%\System32 FileCopy,%SourceDir%\sources\wdscore.dll,%WindowsDir%\System32 ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\wimgapi.dll#$q" ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\wimserv.exe#$q" ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32\Drivers#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\drivers\wimmount.sys#$q" ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32\Dism#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\Dism\*.*#$q" ShellExecute,Hide,%Tools%\7z,"e -y #$q-o%WindowsDir%\System32\Dism\%WimLanguage%#$q -r #$q%SourceDir%\sources\boot.wim#$q #$q%WimIndexBoot%\Windows\System32\Dism\%WimLanguage%\*.*#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\CbsProvider.dll#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\CompatProvider.dll#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\DismCore.dll#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\DismCorePS.dll#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\DismProv.dll#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\IntlProvider.dll#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\MsiProvider.dll#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\SmiProvider.dll#$q" ShellExecute,Hide,regsvr32,"/s #$q%WindowsDir%\System32\Dism\UnattendProvider.dll#$q" RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT,NextInstance,1 RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,Service,wimmount RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,Legacy,1 RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,ConfigFlags,0 RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,Class,LegacyDriver RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,ClassGUID,{8ECC055D-047F-11D1-A537-0000F8753ED1} RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000,DeviceDesc,wimmount RegWrite,HKLM,0x4,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000\Control,*NewlyCreated*,0 RegWrite,HKLM,0x1,System\CurrentControlSet\Enum\Root\LEGACY_WIMMOUNT\0000\Control,ActiveService,wimmount RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,Type,2 RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,Start,3 RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,ErrorControl,1 RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,Tag,5 RegWrite,HKLM,0x2,System\CurrentControlSet\Services\wimmount,ImagePath,system32\DRIVERS\wimmount.sys RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount,DisplayName,wimmount RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount,Group,FSFilter#$sActivity#$sMonitor RegWrite,HKLM,0x7,System\CurrentControlSet\Services\wimmount,DependOnService,FltMgr, RegWrite,HKLM,0x7,System\CurrentControlSet\Services\wimmount,DependOnGroup, RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount,Description,Wim#$sMounting#$sDriver RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount,DebugFlags,0 RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount\Instances,DefaultInstance,Wimmount#$sInstance RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount\Instances\Wimmount Instance,Altitude,180700 RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount\Instances\Wimmount Instance,Flags,0 RegWrite,HKLM,0x3,System\CurrentControlSet\Services\wimmount\Security,Security,01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,00,1c,00,01,00 ,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,00,00,02,00,60,00,04,00,00,00,00,00,14,0 0,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20, 00,00,00,20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,00,18,00,fd,01,02 ,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,00,00,0 0,00,00,05,12,00,00,00 RegWrite,HKLM,0x1,System\CurrentControlSet\Services\wimmount\Enum,0,Root\LEGACY_WIMMOUNT\0000 RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount\Enum,Count,1 RegWrite,HKLM,0x4,System\CurrentControlSet\Services\wimmount\Enum,NextInstance,1 Set,%DismProg%,%WindowsDir%\System32\Dism.exe,PERMANENT jaclaz

See here: http://www.boot-land.net/forums/index.php?showtopic=9113 I guess that some Registry keys need to be added. jaclaz

Last time I checked WINRAR was COMMERCIAL. 7-zip, on the other hand is Open Source (donations accepted): http://www.7-zip.org/ jaclaz

Why are people making it more difficult than it really is? You have a circuit (the RS-232 to TTL converter or the USB to TTL converter). This circuit needs to be powered in order to work. You need to supply the appropriate needed power (Voltage) the circuit requires. This can be depending on the actual circuit you are using, 3,3 V (3 V will do) or 5 V. The hard disk NEEDS 5 V and from a reliable source (read PC Power supply or similar - like those Power supplyes that come with external USB boxes) It DOES not matter WHERE FROM the proper voltage for the circuit comes, it can be from a PC power supply, from a battery, from a second AC/DC adapter, whatever, as long as it is appropriate. THEN we are talking of exchange (relatively) high speed signals between different devices that are NOT physically GROUNDED together and are powered in DC, through an unshielded and ungrounded cable. This means that DEPENDING on the actual circuit board (it's internal impedance and insulation) and on a number of other factors, like the length of the cables used, their type, the actual power source and what not, there may be interferences in the data exchange. If this happens on your particular setup you need to properly GROUND everything together. If this doesn't happen there is no need to ground them (though it's always a good idea grounding together all the pieces). If one is not capable of using a soldering gun, he can peel off a short bit of insulation from the GROUND wire and use a hook: http://www.testleads.net/Catalog/OldakerCatalog.htm or a clip: http://www.testleads.net/Catalog/OldakerCatalog.htm or use "Quick Splice Adaptor": http://www.wiringproducts.com/contents/en-us/d266.html @Twittwilly What should Carterincanada say more than this? : http://www.mapleleafmountain.com/seagatebrick.html jaclaz

Did you use a card between the contacts and PCB? Check this: http://www.msfn.org/board/solution-seagate...-page-2021.html jaclaz

The problem with the "hard Disk Low Level Format Tool" is possibly twofold: the device is NOT a Hard Disk the tool is NOT a "Low Level" Don't want to confuse you , but try simple things before tryng "complex" ones: (baby steps before jumping) jaclaz

In the version of the tale I remember, the "MSFN user" told a completely different story. In that version, he was a poor student that accidentally deleted an otherwise perfectly working Disk/partition using Partition Magic: http://www.msfn.org/board/hp-notebook-reco...nd-t131620.html and he managed to "solve" the problem by finding a copy of the original bootsector from another machine: http://www.msfn.org/board/hp-notebook-reco...20-page-87.html which of course is not a solution, it is a workaround. Same workaround (copying from an "original", "untouched", "identical" hard disk) should work as well for the whole disk/partition (as opposed to the bootsector or MBR only). Why doesn't the "MSFN user" image the drive of one of the affected PCs "as is", tries whatever experiment he is wishing to carry on, and if it/they do not work, re-images the drive back in the previous state? (nothing to lose) jaclaz

You may want to use both a bootmanager capable of chainloading SETUPLDR.BIN in a subdirectory (without using the PRO1.DAT bootsector) and hexedit the path in SETUPLDR.BIN, but you are limited to 4 characters (the length of I386 in SETUPLDR.BIN) see here: http://flyakite.msfn.org/xpprosp1.htm Editing "setupldr.bin" I.e. maybe something like \b\00, \b\01, \b\02 may work replacing \i386 See this (for \i386, \minint and $WIN_NT$.~LS on HD like media - NOT CD/DVD): http://www.911cd.net/forums//index.php?showtopic=17504 http://www.911cd.net/forums//index.php?showtopic=20123 http://www.911cd.net/forums//index.php?showtopic=23200 http://www.msfn.org/board/win-nt-bt-can-om...03.html&hl= jaclaz

Well, as well , out of several suggested steps, you did just one.... And of course, and out of the blue, FIFTH step of THIRD suggested set. First: Second: Third: http://www.msfn.org/board/usb-device-not-r...-7.html&hl= Roughly it is a mechanism that allows to "override" some behaviour or "add features" to certain devices/drivers. http://en.wikipedia.org/wiki/Filter_driver Examples: http://www.911cd.net/forums//index.php?showtopic=18379 http://pcsupport.about.com/od/driverssuppo...owerfilters.htm http://www.boot-land.net/forums/index.php?showtopic=9105 Probably completely unrelated but I remember a similar behaviour to what you report in good ol' DOS with SUBST drives. jaclaz

There may be something "sticky" in the Win2K Registry. See here: http://www.msfn.org/board/usb-device-not-r...63.html&hl= Check also (Upper and Lower) Filter Drivers in your 2K (like virtual drives, some Acronis, and various software may install) Instead of a full low-level format, 00'ing out the first few sectors makes sure the drive can be re-partitioned/formatted clean, but I doubt this is the case: http://www.msfn.org/board/usb-booting-issu...63-page-13.html jaclaz

Also, peruse this: http://www.msfn.org/board/debricking-seaga...es-t133387.html http://www.mapleleafmountain.com/seagatebrick.html jaclaz

Not really. JFYI: http://www.boot-land.net/forums/index.php?showtopic=9113 jaclaz