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

[sarcasm] You need: This (1 or 2x): http://www.tigerdirect.com/applications/Se...77&CatId=77 OR this (1 or 2 x): http://www.tigerdirect.com/applications/Se...27&CatId=75 a 10" stick for the Power ON/OFF button a BIG screen (or a very, very good eyesight ) a room measuring at least 15" in the direction of your chair-screen [/sarcasm] WHAT is the question? jaclaz

The original idea was that we knowing the STOP ERROR number might help. If you now know it - thanks to the disbled automatic reboot - but don't actually post it, we are at the same point of the other day.... jaclaz

Could you expand on the actual amount (I mean a number) that represents the "few" hours it took you from knowing nothing about unattended and an original XP CD to having your "fully unattended install for OS and apps" CD working? jaclaz

And of course ALL those into the Registry. Wouldn't this be a question like "how to run windows 9.x from RAMDISK?" If yes, there are already answers to that question : http://www.geocities.com/politalk/rmdrv/index.html http://www.911cd.net/forums//index.php?showtopic=12326 http://www.winimize.com/ http://www.boot-land.net/forums/index.php?showforum=53 jaclaz

From what I can see on the manufacturer site, the card creates an USB like simulation, just like a usb to parallel cable. You might want to try using this workaround through the use of the MS loopback adapter: http://geekswithblogs.net/dtotzke/articles/26204.aspx http://support.microsoft.com/kb/839013/en-us Your mileage may vary. jaclaz

I wonder how an app designed for SATA/eSATA will help on a USB device. Apart being not actually connected to the OP question, thanks for the link. @extremepilot No matter whether the USB stick/HD/whatever is set to "Optimize for quick removal" or not, always use the "Safely disconnect" feature, either from the tray icon or from a program/script: http://portableapps.com/node/1083 Better be safe than sorry. The programs from Uwe Sieber cdob already pointed to are very useful. jaclaz

Why don't you simply read the given link? A USB 2.0 bus (fastest currently available) is by FAR slower than ANY other bus available today. The speed of the device -any device connected through a bus - even the fastest one ever built will be slowed down by the maximum speed the bus is capable of. To recap: 480 mb/s USB 2.0 1330 mb/s ATA 1500 mb/s SATA 3000 mb/s SATA II So, you are moving something that whirls away at a theoretical speed of 3000 mb/s to something that tops at 480. However, these are just the theoretical speeds of the bus, a typical flash has fast access time and slow transfer time, unlike a hard disk that usually has a slow access time and a fast transfer one. The idea has been used in the new Vista Ready-boost: http://en.wikipedia.org/wiki/ReadyBoost jaclaz

This motherboard? : http://www.asus.com/products.aspx?modelmen...l3=397&l4=0 Interfaces: Hard disk interfaces: (from http://www.hitachigst.com/portal/site/en/p...trastar/15K300/ ) You will need a SCSI Ultra 320 or SAS adapter card, that's not going to be cheap (example prices): http://www.pc-pitstop.com/scsi_controllers/ http://www.pc-pitstop.com/sas_controllers/ Could you expand on the reasons why you want/need to install that drive and not a "normal" SATA one? Hitachi examples: http://www.hitachigst.com/portal/site/en/p...rastar/A7K1000/ http://www.hitachigst.com/portal/site/en/p...skstar/E7K1000/ jaclaz

I prefer attenuated ones: http://www.thefreedictionary.com/attenuated they are usually less noisy. jaclaz

Read this: http://www.msfn.org/board/index.php?showtopic=127747&hl= and links therein. Every OEM appears to be using a different method to create recovery disks, if you are lucky one of the methods linked to may apply, otherwise you'll need to search for "specific" lenovo procedure (if it has been discovered/published/posted soemwhere on the net). jaclaz

Yep, that's the point of the lines in txtsetup.sif. If you compress luna.the to luna.th_ when expanded it will become again luna.the and the line in txtsetup.sif will rename it to luna.theme, without anyone supplying any name. jaclaz

Like many other people on the board, you appear to forget affection. After having a printer for so many years, a special relationship develops between user and machine, you learn to love each single rattling sound, you keep the paper crumpled by the worn out sheet feeder, you get used to your fingerprints evidenced by toner spilled out..... jaclaz

More links here: http://www.everythingusb.com/windows_nt.html Best bet for USB Mass Storage should be Woodhead's set of drivers: http://www.geocities.com/mypublic99/index.html jaclaz

Sorry, I cannot understand you , you cannot understand me , so it's all a waste of time. You may want to either: ask for help on a Forum in your native language ask for help from a friend that can read and write plain English, in order to translate to you the info given or translate to us what you are actually trying to do Have a Merry Christmas.... jaclaz

Good advice, so that info is spread in another post, info like fdv's one is probably not read by the member who started a new thread, etc...... Would this be related to Rule #9? http://www.msfn.org/board/index.php?showtopic=18408 For the record: vhrc99 started a new thread here: http://www.msfn.org/board/index.php?showtopic=127744&hl= jaclaz

It is possible that the particular CD drive needs a different driver. However, no problem , you can use a different approach. Get this app: VFD: http://chitchat.at.infoseek.co.jp/vmware/vfd.html and install it (read instructions) Start it creating a Virtual Floppy A:. Download the "Driver Free Disk For BIOS Flashing" from bootdisk.com Double click on the downloaded file and expand the disk on A: Copy to A: the BIOS flashing files from MSI. Save the image. Use the image with your prefered CD burning tool as Floppy emulation image and make a bootable CD. This way all files are within the floppy emulation image and no drivers are needed to access them (everything will be on A: when the CD is booted). jaclaz