jaclaz

3.5" are easily found: http://www.lindy-usa.com/31-2-floppy-disk-...aner/40411.html point is that the example above costs 12 bucks whilst a new floppy drive can be found for as low as 10 US$ P&H included: http://shop.ebay.com/i.html?_nkw=1.44MB%20....m14&_pgn=2 I guess this item was mislabeled/mispriced : http://www.superwarehouse.com/Teac_1.44_MB...FC929/p/1533255 @multibooter JFYI, this is outrageous : http://www.mitsubishielectric.com.au/895.htm#4. http://www.superwarehouse.com/LS-120_SUPER...T/41066/p/59773 Image found here: http://demo7.ibiz10.com/ibiz10Demo7/images...cts/149073w.jpg A semi-random idea, investing in the past: http://cgi.ebay.com/LOT-of-540-3-5-1-44MB-...id=p3286.c0.m14 jaclaz

Not so sure about intelligence, I guess memory/experience has more to do with it. Before anything I would try running the two utilities Chipgenius and USB Device viewer on the "working" XP. Find relevants links to them in this thread: http://www.msfn.org/board/screwed-up-usb-d...;hl=usbstor.sys Once you have found which is the Controller inside the cable/adapter it should be easy to find Manufacturer and it's driver for 2K (IF existing). Also, unrelated, but you never know, this may be nonetheles of help : http://www.msfn.org/board/generic-98-usb-d...rks-t99220.html NOT a solution, maybe a hint towards a possible exploration path, you will need to read "between the lines". jaclaz

Has something been changed again? Direct link to post don't work anymore properly. The result is that instead of pointing to the actual post they point to the page (nothing/10/20/30/40/50/...etc) where the post is. Example: the link to the previous post by ilko_t given in the copy and paste popup is this one: hxxp://www.msfn.org/board/index.php?s=&showtopic=137119&view=findpost&p=878576 which once "resolved" by the board becomes: hxxp://www.msfn.org/board/broken-links-forum-issue-t137119-pid-878576.html but the result is that the first post on the page is shown, not the pointed to one. Even the "other" old syntax: hxxp://www.msfn.org/board/index.php?act=findpost&pid=878576 resolves to: hxxp://www.msfn.org/board/broken-links-forum-issue-t137119-pid-878576.html with the same result Using "post offset within thread" it should be (with the"new" "page" definition): hxxp://www.msfn.org/board/broken-links-forum-issue-t137119-page-9.html or, with the good ol' "&st=" one: hxxp://www.msfn.org/board/index.php?s=&showtopic=137119&st=9 which BTW is now resolved as: hxxp://www.msfn.org/board/broken-links-forum-issue-t137119-page-9.html&s= jaclaz

A potential physical damage (the arm) will NOT create a connection problem via hyperterminal to the PCB. Heck, within limits, you can connect to it even after having completely removed the PCB. This said, it is unlikely that the problem has developed WHILE transferring data (meaning THE firmware problem discussed in the present thread). The actual cause of the problem, is when a sort of internal "event log" inside the drive reaches a given # of entry 320 or multiples. Thus it is very likely that it happens at boot (or connection of hard disk) time. @fasthands A "normal" USB to SERIAL might not be the appropriate interface. Read about TTL levels here: http://www.msfn.org/board/solution-seagate...-page-1730.html In any case perform a loopback test to check that the adapter is actually working: http://www.msfn.org/board/solution-seagate...-page-1661.html jaclaz

ALL of them, including the MP tool? That is AFAIK, last possible chance, as it's "special drivers" are capable of accessing the device at a "lower level" then "standard" USBstor ones. True, but not specifically in this case, unless some of the good Linux guys has written a specific driver/app (possible, but I don't know any of them) No, "normal" programs cannot work. They need a "target" to partition, if the device is not seen by windows as \\.\PhysicalDriven or under linux as /sd<something>, there is NO way they can work. You need a lower level kind of app, something that provides it's own USB drivers or somehow accesses the port directly. I am out of ideas, right now. You are in a situation very near to the "fakesize" problem on cheap sticks, try browsing here: http://fixfakeflash.wordpress.com/ they also put in nice words what I am trying to tell you: jaclaz

Thanks for the update/info . I will try studying a bit the given info, but I guess it will take me some time.... WARNING: @all Generic problem already found elsewhere: Google translates REMOVES "double minus signs": -- REPLACING them with "single minus sign [space]; "single minus" are left UNTOUCHED. Be very aware that the grub4dos menu.lst example "filtered" by Google WON'T work with copy and paste, example, this: NEEDS to be written in menu.lst as follows: # Whole file to find OEM_SCSI.IMG find --set-root / oem_scsi.img # Find and map (fd1) map --mem / oem_scsi.img (fd1) # Directly to the virtual one blank (fd0) map --mem (md) 0x8000 +1440 (fd0) map --hook jaclaz

dibloff, take a deep breath. There are 94 pages of this thread basically full of this info: NO software tool, by Seagate or any other, is capable of reviving a bricked drive the only known solution is to connect the drive to a TTL level serial and correct the issue through command lines in hyperterminal or a similar app You (and everyone else coming here for the first time) should take some time to read, or at least skim through the existing pages, you would have probably found these: http://www.msfn.org/board/solution-seagate...-page-1854.html (up to post #1857) and thereby given links that would have already answered ALL your questions. jaclaz

First thing let me reassure you: your English, whilst maybe not being "from Oxford", is good enough, and very easy to understand, at least for another not native English speaking guy. If you need any help in refining the English sentences of your future thread on bootland, or you need anything to start it, just PM me and I'll try my best in order to help you. Thanks for the link, I will look at the 0PE and see what I can understand of it. jaclaz

OK , I thought that by "software arrangement" you meant that some software was actually installed on the drive (which made me think at an U3 stick, or however to a CD+HD device, since the UT165 has this feature): Since I don't think that both ChipGenius and USBdeview "invent" by thenmselves the data they show, I presume that some functionalities of the stick are still present, and that the stick is actually a UT165 device with VID 046D and PID C016. It is possible that the utilities have "embedded" anothe PID or VID, and thus cannot recognize your stick. Also are you running Vista? There may be problems in running this kind of utilities under Vista, for this particular scope a XP is more advisable. Usually manufacturer tools have a "side app" capable of changing the VID and PID to any number you choose. (including the ones that may make the device be recognized by the above mentioned "simpler" programs. Without going into too much details "simpler" utilities use the "simple" "standard" USB drivers, whilst Manufacturer Tools normally use a "special" driver to communicate with the device. Also, from the USBdeview screenshot you posted, I see that you have several "other" USB devices connected, it is possible that the above programs get confused by them. I could tell you, but I'd have to kill you afterwards. Yes and yes, though the first yes means that I am familiar with the concept of Flash sticks and Manufacturer Tolos, but not necessarily with this specific make (USBest) and model (UT165). Look at the left of any of your posts, take note of the number of posts you made and how long have you been a member here. Look at the left of any of my posts and take note of the same data. Compare them. Check the "title" I have on another board: http://www.boot-land.net/forums/index.php?...c=8710&st=4 Draw your conclusions on the reasons why I can find something you cannot.... jaclaz

I may add that a User Name like: or may trick the oneliner, whilst it does not trick the original one by Yzöwl jaclaz

We are then back to the only available solution AFAIK, which is minlogon. Why don''t you simply try it, and see if it is actually what you need/want? If it is, the thing that you are looking for is easily described: if it is not, you have also an easy negative description: jaclaz

Well, with all due respect to Novicorp WinToFlash, and just for the record, there are also other ways: http://www.msfn.org/board/install-xp-usb-f157.html http://www.msfn.org/board/install-usb-wins...ui-t120444.html and another plainer but still experimental way: http://www.boot-land.net/forums/index.php?...=5041&st=26 jaclaz

MS-DOS 5.0 wasn't that bad. (possibly because 4.0 actually was that bad) jaclaz

You mean the thread where Aegis says to check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion ? From batch/command line one can use WMIC allright, some examples: WMIC OS list /Format:list WMIC OS list BRIEF /Format:list WMIC OS get /Format:list WMIC OS get name, version /Format:list jaclaz

Nicely put here: http://ss64.com/nt/ver.html Though I guess that is "good enough" for "normal" use. I guess the "proper" way is to check the %OS% varaible, than check contents of this Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion ProductName CurrentBuildNumber CurrentVersion Should contain all the needed data (that can be compared with the VER results) jaclaz

Just wanted to make sure. Which .bat file? There is a .zip file to be downloaded: http://students.cs.byu.edu/~codyb/beeblebroxntsetup.zip that you unzip somewhere and then run SETUP.EXE to install the soft. It is important because there are different methods to (hopefully) fix different failures. Let's put it this way: in your home a side wall at the second floor level has a hairline crack: are you gonna put some plaster on it or demolish the house and rebuild it from its foundations in order to fix it? What do you mean by software arrangement? Is/was it a U3 kind of drive? U3 drives have two "partitions" (actually two devices with different LUNs), one which is a CD-ROM drive and one which is a "normal" disk. Check this: http://www.msfn.org/board/install-xp-boota...38.html&hl= The "standard" utility instructions should be these: http://209.85.135.132/translate_c?hl=en&am...4nRuQR2bjhkEhcQ though maybe this other is easier: http://209.85.135.132/translate_c?hl=en&am...Vl9FKaB1tvwUEDQ If the thingy is/was an U3, you might need this other one: http://209.85.135.132/translate_c?hl=en&am...ozKMdWNhKzr58hA I would first thing try this one: http://209.85.135.132/translate_c?hl=en&am...p22iKQPu3C12IYw and before anything else, try only reading the info of the device with this: http://209.85.135.132/translate_c?hl=en&am...GvrpsW_HBgC4gUg You must understand that any of the above (exception made for the very last tool that is an "information only" one) are DANGEROUS, as they can potentially put the device in an actually unrecoverable state (with same utility, the "actual" "Manufacturer Tool should always be able to start again from scratch). BEFORE using any of them, take your time reading the (scarce) info available, try googling to see if you can find anything about the settings that your particular make/model USB stick had been set to. In any case read the manual for the MP tool: http://209.85.135.132/translate_c?hl=en&am...8XFgqchNZRyxMow You must be sure of what you are doing, when you actually run the utility. jaclaz

Sure , we didn't think for a minute that they came with your hair drier or with your microwave oven. If I may re-word Tripredacus question: Where did BOTH the DVD's AND the laptop came from? Possible answers: they were made by elves and came from the magic forest they were made by noone, they just appeared out of nowhere when I used my magic wand they were made by and came from HP they were made by and came from Lenovo they were made by and came from Sony they were made by and came from (name any other laptop manufacturer, and while you are at it, tell us also the model and which OS came with it) jaclaz

Hmmm. What if you try clicking on each of the 1 to 9 values? (selecting them one by one) However, let's try another way. Please try again with Beeblebrox: http://students.cs.byu.edu/~codyb/ same thing with the drop down box "Physical Disk 0" jaclaz

Since you read and write both Chinese and English, you appear not to consider how difficult can be for a "westerner" to access the wuyou Forum. Through Google translate it is often impossible to navigate Chinese sites, if they use .gif or .jpeg with ideograms which of course the translator cannot see "properly" and translate, and the language is so different that it is very difficult to understand the translated text anyway. Any chance you can post a few direct links to the relevant pages? Or create on boot-land an English Topic for those? jaclaz

I am still failing to understand the question. (and the entire last post) If you need to run a command with "extraordinary" powers, you can try this: http://www.grubletrang.com/Software.aspx?app=PowerPrompt it may (or may not) work for what you want/need to do. jaclaz

I guess you are making things more complex than they are. You have a .iso, right? With a \I386 directory, right? Follow the standard instructions: http://support.microsoft.com/kb/883390/en-us You shouldn't need to copy NTDETECT.COM and SETUPLDR.BIN to ROOT, since you will be using grub4dos as a loader, but since it won't do any harm, do it as well, only don't rename SETUPLDR.BIN to NTLDR. Then try both: jaclaz

If ChipGenius detects it it means that the drive is working (or at least is working enough to be detected). (good news ) It's an USBEST UT165. I am not yet convinced of the HDhacker report. With hdhacker you should check if the dropbox near "Physical Drive (MBR)", which opens by default on your foirst hard disk (physical drive 0), when clicked over shows an added entry after the USB is connected. (if you have only one harddisk, you should have just 0 when no USB is attached and 0 and 1 when it is, and so on) Please check again. Now, if the usb stick remains "missing", there are two possible causes of the problem: something in the Registry has gone beserk something in the stick has gone beserk (or both) Since you tested on several machines and with different OS, I think that the Registry corruption is unlikely, but since it is much safer than the alternative, do check with this: http://www.nirsoft.net/utils/usb_devices_view.html and try cleaning the Registry with this: http://www.nirsoft.net/utils/clean_after_me.html We'll talk later of the alternative (using the Manufacturer's Tool to reset the stick, in the meantime start reading here: http://fixfakeflash.wordpress.com/2008/12/...ucceed/#more-32 and follow the instructions to find and get an appropriate tool, BUT: DO NOT use any tool until we are certain there is no other way! jaclaz

No, rest assured, it should be perfectly recoverable, point is whether it will be easy or difficult. First thing you should find out whether it is seen as \\.\Physicaldrive Easiest way would be to download this HDhacker: http://dimio.altervista.org/eng/index.html Run it WITHOUT the USB stick inserted and take note of which PhysicalDrive it can see. Then insert the USB stick and re-run HDhacker, see if you have an additional PhysicalDrive listed. Then try running ChipGenius: http://www.boot-land.net/forums/index.php?showtopic=4661 http://www.mydigit.cn/chipgenius.htm And see what data it can find. Post results of both. jaclaz P.S.: Be warned that it is also possible that the stick simply "died" of it's own, PEtoUSB (or any other software utility) cannot by itself render a device useless/unrecoverable (while it may make it not detectable by Windows), only a wrong firmware setting may

Ok, since noone AFAICR mentioned it: http://www.fdos.org/ripcord/rawrite/ Have you tested FDimage? jaclaz

Comeon, you don't expect it to be so easy, don't you? Read this: http://www.boot-land.net/forums/?showtopic=4857&st=9 AND links within it. Next time, try searching a bit, you may find very similar questions ALREADY asked and hopefully answered to : http://www.msfn.org/board/install-xp-usb-h...ve-t122170.html jaclaz