jaclaz

A very educated guess jaclaz

That's probably pretty much "normal". That file has duplicate [system32.Files] entries, second one empty. I seem to remember that entries need to be deduplicated first. jaclaz

There is NOTHING that needs to be added. Modern drives like the 7200.11 store some info on a chip (often called ROM, though it is actually either a Flash or EEPROM). These data are specific to the disk that is attached to the PCB. Through special tools (OUT of reach for the hobbyist) it is possible to read these data from the "old" PCB and write them on the new PCB. An alternative is to physically de-solder the chip from the old PCB and re-solder it on the new one. This also is OUT of reach for common hobbyist, as it needs some experience/abilities that are not "common". Some people who sell replacement PCB's will do either of the above for you. BUT this WILL NOT help for a LBA0 or BSY issue. DO NOT EVEN THINK of swapping a PCB unless the PCB is "fried" and you don't do one of the above explained procedure. Guess WHY this additional sticky was made? jaclaz

Well no, there is software, only most probably you won' t like it's price tag: http://www.seagateunlock.com/ http://www.hddunlock.com/drives/seagate/ http://www.hdd-tools.com/products/rrs/ You can try also with SEDIV, see here: http://forum.hddguru.com/seagate-non-standard-ata-master-password-t12920.html http://forums.seagate.com/t5/Barracuda-XT-Barracuda-Barracuda/SEAGATE-BARRACUDA-7200-12-ST31000528AS-1TB-MASTER-PASSWORD/m-p/60234#M20842 but cannot say if that drive is supported in any of the above mentioned tools. jaclaz

Not even "slightly-more-advanced-user" friendly (if I can be .consodered in this category) What is written there is just "RTFM"! What may be useful could be this list of commands: http://files.hddguru.com/download/Datasheets/Seagate/Seagate%20Diagnostic%20RS-232%20Port/ And the actual manual (I presume this one is the one for your disk, but as always check and double check): http://www.seagate.com/staticfiles/support/disc/manuals/ce/Pipeline%2520HD%2520Series/100529372g.pdf I have NO idea if what you wish to do is possible at all and/or if the aboive given files contain enough data to perform it. Would not using hdparm work on that disk? Today's thread with some references: jaclaz

Good, now you have to find out which kind of password (if any) is set (of course should you be able to retrieve this kind of info from the "old" raid machine it could be easier). WHICH OS are you running/have available? I presume that using "normal" hdparm under Linux woud be "more direct", but you can try using the NT port: What happens when you follow the instructions here? https://ata.wiki.kernel.org/articles/a/t/a/ATA_Secure_Erase_936d.html Review this thread if you are using a Windows NT: http://reboot.pro/13601/ jaclaz

Good. Now had you followed the given "generic advice", you would have found that you are not the first one to attempt something like that, there is at least a previous attempt: unfortunately daddo1980 never came back to report if it worked.... A small Quote for you (still related to "generic" advice): http://en.wikipedia.org/wiki/AK-47 http://en.wikipedia.org/wiki/AK-47#Design_concept jaclaz

If I may you have TWO separate questions/problems: boot from the PCMCIA (or CardBus)? access contents of the card from "pure" MS-DOS The second (only) may be solved through DOS drivers. Finding dos drivers that work on your particular hardware may be dufficult, but it could be doable. You may find of interest: http://www.quatech.com/support/pdf/pcmcia_for_dos.pdf http://www.rocketsoftware.com/products/systemsoft http://www.tssc.de/index.htm# http://www.cer.com/pages/products/prod_faq_answ.php?faq_id=24 http://www.mail-archive.com/arachne@arachne.cz/msg20538.html http://wayback.archive.org/web/19980715000000*/http://www.datorintensiven.se/dinew/drivers/iqnote/cardwiz.zip http://www.oldjake.co.uk/progs/cardwiz.zip http://support.lenovo.com/en_US/downloads/detail.page?&LegacyDocID=DSHY-3NPU8M It greatly dpends on your hardware, chipset used, etc. ec, and some tweaking may be required anyway, since your hardware loks like "not so easy" one: http://pcmcia-cs.sourceforge.net/cgi-bin/HyperNews/get/pcmcia/toshiba.html?inline=-1 jaclaz

Good, now go and wash your mouth fingers with soap! jaclaz

Sure : http://www.plop.at/ http://forum.plop.at/ jaclaz

What does it mean? Why the Lord of WinXP is so negative? Not at all "negative", a simple, plain, statement. Would you prefer that I lie and EITHER: tell you (falsely) that I know a perfect solution for that issue but I am not going to tell you exactly how to do it OR tell you (falsely) that I know a perfect solution for that issue then send you on some wild goose chase jaclaz

For the record, that command WILL NOT update the MBR code, it will update the bootsector or PBR one, you need to have the Windows 7 version of bootsect.exe and add the switch /mbr to it to modify the MBR code. The original article: http://technet.microsoft.com/en-US/library/49ded4da-b66f-4b42-9563-04c218a1a6ac.aspx leads to confusion. The Windows 7 version has the added /mbr switch: http://technet.microsoft.com/en-us/library/dd744577(v=ws.10).aspx jaclaz

Look, it's like comparing Orange and Apples, it can be done allright: http://improbable.com/airchives/paperair/volume1/v1i3/air-1-3-apples.html but not necessarily using the one will be an answer to a problem that can be solved by the other. A Porsche 911 is much faster than a Toyota Hilux truck, but if the issue at hand is "how do I bring my apples (or oranges for that matter) to the fruit market to sell them?" the latter is a more suitable answer to the question. As well, remember that "native" VHD booting is available only with some of "high end" Windows 7 licenses. jaclaz

That should mean that you have some setting in your OS that prevents writing (to be 100% sure you can test those devices on another PC). There are two main reasons for this, one is the use of this key in Registry: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StorageDevicePolicies] “WriteProtect”=dword:00000001 there are tens or maybe hundreds of "USB protect" softwares that use the above, if this is the case, you can use info here: http://www.howtogeek.com/howto/windows-vista/registry-hack-to-disable-writing-to-usb-drives/ to disable the key. The other one is this particular software that implements a READ ONLY filter driver in the system: http://www.softpedia.com/progViewOpinions/USB-Write-Protect-163146,.html http://www.nareshmdr.com.np/index.php?pg=mysoft_info&soft=usbwp (though there may be others that use the same approach) Of course only you can say if you ever run the above mentioned - or some similar - software. jaclaz

Maybe, just maybe, if a Manufacturer tool says that one of their disk drives is "password protected and can not be tested" maybe it is because ACTUALLY the device is "password protected". Remove the password from the disk. This may be possible or not depending whether you know the password and WHICH type of password has been set. The mentioned SecureErase/HDDerase may be able to deal with it, as well as hdparm: https://ata.wiki.kernel.org/articles/a/t/a/ATA_Secure_Erase_936d.html Read this, also: http://www.rockbox.org/lock.html jaclaz

Though I can see an interesting use of USB drives, as the PC's I have do not have a port/connector to which I can connect a VHD. jaclaz

Here, right after you . And this thread is about installing TO an USB stick, not really a surprise that your mileage may vary. I have NO idea WHat is happening/WHY it is happening, so all I can do is provide some "generic" advice. You should check the available methods and become VERY familiar with them before attempting to introduce variations/complications, expecially if mainly UNneeded (in the sense of NOT really-really needed): http://www.msfn.org/board/forum/157-install-windows-from-usb/ A much easier approach would be, if you really-really *need* to have the source in second partition to (temporarily) switch partitions and make it first one: http://www.911cd.net/forums//index.php?showtopic=24392&start=0 On the other hand why some of the known methods to install XP from USB do use, in case of "Fixed device" (i.e. USB hard disk) a "reversed dummydisk.sys" to make it become "removable"? jaclaz

Yep , I would also add the adjective UNSTABLE to the "explosive" substantive. jaclaz

OT , but not much search for "revolutionary" on this page : http://www.microsoft.com/download/en/details.aspx?id=19004 Abd - still OT but not that much - a comparison related to design evolution: http://reboot.pro/16395/ jaclaz

Actually much more than enough. The ONLY needed thing is usually to 00 out the first sector of the device, if - for any reason - "normal" Disk Management cannot deal with it. More commonly the only actual thing that may be needed is to 00 out last two bytes of first sector, removing the "Magic Bytes" 55AA, and thus getting, as soon as you open Disk Management, the prompt to "initialize" the disk: http://reboot.pro/12253/ jaclaz

.... and NT based systems have a HAL (hardware abstraction Layer), thus *anything* the BIOS says is ignored by the OS that re-interrogates everything through device drivers as soon as the real mode part of booting switches to protected mode ...... I would personally take BIOS out of the list of 2K related questions. A BIOS will either work (or completely fail to) with 4 Kb disk drives, no matter the OS that will be later loaded..... jaclaz

Do you mean that you: tested Atto AND tested it AND it works on WIn9x downloaded it BUT NOT tested it under Win9x downoaded it AND tested it AND it does NOT work n Win9x Same as above for "USB Flash Drive Tester". If you prefer, I am sure that people wouuld appreciate the results of the tests as opposed to a list of what you have downloaded, no matter if listed for WIN9x or not . jaclaz

Atto could be "old enough" to run under 9x (but cannot say): http://reboot.pro/9874/ jaclaz

jaclaz

That's exactly the behaviour I described earlier (which I tested on XP). Gunsmokingman introduced a "variation" on the theme adding a number to the name of the item that may have confused you (or I confused you by NOT adding the number to the name and echoing instead the number ) Yes, the point - as I see it - is that creating a .ini stile file, i.e. with lines of the type: item=value through ECHO should be a "common enough" kind of task, and it is strange that noone around here had noticed this strange behaviour, Yep, same here, and IMHO it is the "fun" part of it! jaclaz