jaclaz

Maybe you could make a step back and simply use the good ol' way: http://www.911cd.net/forums//index.php?showtopic=16713 just use FAT16 instead of FAT32 for NT 4.00. jaclaz

You add a migrate.inf to the source. Search for posts by me or cdob here or on 911CD with keyword "migrate.inf". Please note that the "usual" migrate.inf is for assigning a letter to a partition, you will need to adapt the idea for the CD-ROM-like device (that is a "Removable" device, and thus it is identified in a different way). jaclaz

NO. jaclaz

Opera works correctly, 100% with CODEBOX, BUT with the CODE, TABs are converted in multiple (4) spaces. This latter behaviour is a known thing, and it is always a good idea when using TABs, to specify where they are. I haven't a Firefox installed now, so I cannot say. jaclaz

The ones you have not working (and clicking) are malfunctioning drives where the mechanical part failed. (more common) The one at hand may be one of the rare cases where the electronic part failed. (less common) Though "transplants" in some cases are possible, I don't think it is worth the hassle, unless yu have to recover data on the drive. jaclaz

There are separate apps: http://www.msfn.org/board/index.php?showforum=157 that already do that. jaclaz

There may be motherboards that use passwords, as some laptops do, usually using a so-called "security chip", but a drive can be "locked" ONLY by the in-drive password feature, in which case the BIOS should prompt for password when booting, but this is NOT always true. Some details about the two (three including "standard" BIOS password protection) different protections is here: http://www.pwcrack.com/bios.shtml A locked drive will usually prompt for something like the ones reported here: http://www.hdd.profesjonalnie.pl/hpr.php As said, a HDD utility like mhdd will tell you whether a drive is locked or not: http://www.real-world-systems.com/docs/MHDD_en_manual.html peeps, don't do this at home if you are not absolutely positive about having thoroughfully read and understood the ATA/ATAPI standards and manual/faq's of mhdd. Think twice and thrice before issuing a command with pseudo-low-level utilities! jaclaz

Check this; http://www.pctools.com/guides/registry/detail/788/ jaclaz

It's not easy to give you an exact or proper answer, there could be a number of services running in the background that still locked that partition, you do not specify whether you unmounted the drive before re-partitioning over it ..... ....however re-booting after having made changes to the MBR and partition tables is a good idea anyways, guess why the good ol' fdisk REQUIRED that? http://www.blackviper.com/Articles/OS/fdis.../image1_24.html jaclaz

@johnc FYI: http://www.msfn.org/board/index.php?showtopic=66101 jaclaz

Let's start from the beginning, OK? Any ATA drive has some built-in features. Among them there is the "Locking" feature. A drive is either "locked" or is it not. A "not recognized" drive is not a symptom of it being "locked". http://www.rockbox.org/lock.html http://www.hddunlock.com/ If the drive is NOT recognized: 1) inspect ATTENTIVELY pins and connections, it happens remarkably often that a soldering has "cracked" 2) try accessing it with diagnostics software: http://hddguru.com/ jaclaz

Really? Strangely enough it wasn't mentioned before, if not by cdob and by Kingskawn that acknowledged it being a solution to his OP problem. jaclaz

new version ddlistw on the same link: http://www.boot-land.net/forums/index.php?showtopic=8219 jaclaz

Good, so now you are at Step 0. Well, YOU did it, I just hinted you the directions to take, even small things can help in preventing wall injuries . jaclaz

Did the idea of sharing your found result so that another user searching for this same topic will find it here cross your mind? jaclaz

Undoubtedly. The real question is: would anyone with these abilities be willing to do that? Current things (NOT prone to become "native" anything): http://www.it.fht-esslingen.de/~zimmerma/s...are/ltools.html http://www.it.fht-esslingen.de/~zimmerma/s...ols/ltools.html http://www.chrysocome.net/explore2fs http://www.chrysocome.net/virtualvolumes This: http://win2fs.sourceforge.net/index.shtml claims that "somewhere" he has a 9x/Me version - EXPERIMENTAL - not fully working: http://win2fs.sourceforge.net/faq.shtml#SD1 maybe he needs just some support/motivation to go on or you could try to convince the Author of this: http://ext2fsd.sourceforge.net/projects/projects.htm to port the thingie to Win9x/Me The old project: http://ashedel.chat.ru/ext2fsnt/ was the one that was sold to Paragon Another oldish project (read only): http://www.yipton.net/content.html#FSDEXT2 and it's "evolution" (abandoned as well) courtesy of the Wayback Machine: http://web.archive.org/web/20020404073442/...de/fsdext2.html The "bases" are all available. jaclaz

Just to keep things as together as possible, here: http://www.boot-land.net/forums/index.php?showtopic=8219 is a small batch to take advantage of the features of the dd --list mentioned before. Example output: C:\VSS>ddlist Drives by drive letter: c: 0,1 Fixed HarddiskVolume1 {b0b284c3-8a33-11dd-8781-806d6172696f} d: 1,1 Fixed HarddiskVolume2 {b0b284c4-8a33-11dd-8781-806d6172696f} e: 3,1 Fixed HarddiskVolume3 {98f06d4c-9506-11dd-8147-001fc6bb76ce} f: 8,1 Fixed HarddiskVolume11 {0cb309be-d343-11dd-ab05-001fc6bb76ce} g: 3,2 Fixed HarddiskVolume4 {98f06d4d-9506-11dd-8147-001fc6bb76ce} h: 3,3 Fixed HarddiskVolume5 {98f06d4e-9506-11dd-8147-001fc6bb76ce} i: x,x CD-ROM CdRom0 {80cf88c2-8a34-11dd-813c-806d6172696f} j: 2,1 Removable Harddisk2\DP(1)0-0+5 {5d3e8800-9c1f-11dd-8148-001fc6bb76ce} k: 4,1 Removable Harddisk4\DP(1)0-0+f {80cf88c3-8a34-11dd-813c-806d6172696f} l: 5,1 Removable Harddisk5\DP(1)0-0+10 {80cf88c4-8a34-11dd-813c-806d6172696f} m: 6,1 Removable Harddisk6\DP(1)0-0+11 {80cf88c5-8a34-11dd-813c-806d6172696f} n: 7,1 Removable Harddisk7\DP(1)0-0+12 {80cf88c6-8a34-11dd-813c-806d6172696f} o: 3,4 Fixed HarddiskVolume6 {98f06d4f-9506-11dd-8147-001fc6bb76ce} Premere un tasto per continuare . . . Drives by connection: c: 0,1 Fixed HarddiskVolume1 {b0b284c3-8a33-11dd-8781-806d6172696f} d: 1,1 Fixed HarddiskVolume2 {b0b284c4-8a33-11dd-8781-806d6172696f} j: 2,1 Removable Harddisk2\DP(1)0-0+5 {5d3e8800-9c1f-11dd-8148-001fc6bb76ce} e: 3,1 Fixed HarddiskVolume3 {98f06d4c-9506-11dd-8147-001fc6bb76ce} g: 3,2 Fixed HarddiskVolume4 {98f06d4d-9506-11dd-8147-001fc6bb76ce} h: 3,3 Fixed HarddiskVolume5 {98f06d4e-9506-11dd-8147-001fc6bb76ce} o: 3,4 Fixed HarddiskVolume6 {98f06d4f-9506-11dd-8147-001fc6bb76ce} k: 4,1 Removable Harddisk4\DP(1)0-0+f {80cf88c3-8a34-11dd-813c-806d6172696f} l: 5,1 Removable Harddisk5\DP(1)0-0+10 {80cf88c4-8a34-11dd-813c-806d6172696f} m: 6,1 Removable Harddisk6\DP(1)0-0+11 {80cf88c5-8a34-11dd-813c-806d6172696f} n: 7,1 Removable Harddisk7\DP(1)0-0+12 {80cf88c6-8a34-11dd-813c-806d6172696f} f: 8,1 Fixed HarddiskVolume11 {0cb309be-d343-11dd-ab05-001fc6bb76ce} i: x,x CD-ROM CdRom0 {80cf88c2-8a34-11dd-813c-806d6172696f} Premere un tasto per continuare . . . jaclaz

Rest assured, you don't. The AutoRunAlwaysDisable is a "standard" XP key. Evidently the "Brother RemovableDisk", whatever it is, didn't work properly in tests with the Autorun Feature, and the good MS guys added a key to prevent Autorun to EVER run from a "Brother RemovableDisk". By browsing the Registry you will see a number of these hardware specific "exception" keys, they are all more or less ways to fix incompatibilities between Xp and "strange" hardware. jaclaz

Well, the image you create is NOT a .ISO image. It is a floppy image (a common extension used for these images is .IMA). So you DO NOT "burn" the image. You create a NEW disk using the whatever.IMA as El-Torito Floppy Emulation image. In Imgburn you choose Create Image file from files folders, some tutorial is here: http://forum.imgburn.com/index.php?showtopic=1779 Build mode: http://forum.imgburn.com/index.php?showtopic=6392&st=5 (please note that the example in the last link is about a No-Emulation boot image, NOT for a Floppy Emulation one, which is the one you need to build) You want to make a bootable disk, using the floppy image as Floppy emulation. If you check the checkbox "Make Image Bootable", then choose "Emulation type"-> Floppy 1.44 Mb Floppy Image and supply the path to the .IMA image leaving the defaults as they are you should be all set. jaclaz

Are you using the "XP install from USB"? http://www.msfn.org/board/index.php?showforum=157 No it's not only for XP. There has been a similar report: http://www.msfn.org/board/index.php?showtopic=120631 but the OP "abandoned" the game. I guess that wimb and ilko_t may help you on this. jaclaz

Well, NO. Sure enough some of them do, of course you need an initial loading into RAM, this can happen from CD-ROM also. For the record, system.dat and user.dat ARE the Regisrtry: http://www.computerhope.com/registry.htm @charly A sligthly different, but equally interesting method is this German bootloader : http://www.msfn.org/board/index.php?showtopic=23622 http://lab1.de/Central/Software/System-Tools/WWBMU/ jaclaz

See if reading "between the lines" of this helps: http://www.siginetsoftware.com/forum/showthread.php?t=8 http://www.ryanvm.net/forum/viewtopic.php?p=24275 jaclaz

This already tells us something more (not much ), it is definitely something related to one of the devices that use the disk.sys driver, i.e.: any of the HD's (or the controller, or the cable) any of the USB disk-like devices (USB sticks, card readers, etc.) If you check with Regedit the key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk You will see that disk.sys is the "SCSI miniport" driver that is used to acces the devices that you can see in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk\Enum OR, as it seems probable by now, something somehow interferring with the "normal" behaviour of the driver, like the CD/DVD-ROM, which share the same cable/controller but however use another driver: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdrom HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdrom\Enum OR, an actual RAM problem, that the tips from Infiniti25 should have fixed: http://forums.techarena.in/tips-tweaks/945479.htm What was the problem with the full memory dump? You may want to re-check here: http://www.msfn.org/board/Creating-memory-dumps-t90244.html what you want to do is (apart having downloaded and installed the debugging tools) to follow just the part titled jaclaz

The link given by Infiniti25 should be what you need: Which more or less means, translated into plain English: "Do the right thing!" you need to experiment with the actual device and resolution you are using. I may add that aparts from sheer size there may be font readability issues, it seems like on screens Sans-Serif Fonts and namely Verdana it's easier to recognize/read: http://www.msfn.org/board/index.php?showtopic=99265&st=4 Be also aware that for documents the "standard" black characters on white background are much less readable than (for example) black on medium gray or dark blue on light grey, as the white provides a lot of "light/contrast" that tend to blur characters. Some examples: http://www.sapdesignguild.org/resources/di...xtcolor_bk.html jaclaz

Well, there is no such thing as "Stop 50". A BSOD error looks like this: It is composed of the main error code (0x00000050) plus a number of added parameters of subcodes: in the example. plus, in some cases, additional info: in the example. Though this might seem "Chinese" to you (and to me ) the fact that in their contorted minds the MS programmers wrote a routine to actually display those apparently senseless numbers, should mean that someone can actually understand something more than just "error 50". I was merely trying to help you in getting helped hopefully one or two steps beyond the "I'm ill doctor, help" stage: http://homepages.tesco.net/J.deBoynePollar...ard-litany.html jaclaz