jaclaz

Of course provided that his reaction time is actually shorter than three seconds.... jaclaz

NO air, nor atmosphere, unfortunately , no sky either, nor horizon only an immense bubble (surrounded by vacuum ) of odorless tasteless gasses. jaclaz

Yes, this may be an issue. You might want to try another approach, slipstreaming the actual AHCI driver to the source (by itself or using the DriversPack) as to remove this possible issue. I am not sure to understand the reference to the SD cards. More loosely, you have a working OS (Windows 7) and a USB stick (or SD card reader?) that can boot to grub4dos, so you have in any case a way of booting. Before making other experiments I would create (on the USB whatever) a Windows 7 boot floppy image, see here: http://www.multibooters.co.uk/floppy.html For a quick howto. And test it from the USB. Something like: map --mem /myfloppy.img (fd0) map --hook root (fd0) chinloader /bootmgr should do nicely. If you need more info on how to make the floppy image (I would personally use IMDISK) , just say so. Once you have this "failsafe" provision, you can try to copy the Windows XP source to the internal hard disk and install it through WinntSetup: jaclaz

Naah , all the balloons behind the green glass door are not inflated, they use a compressor to aggrandize or swell them using a poutpourri (or assortment) of different gasses. jaclaz

Or - maybe better - get the info from the mouth of the wolf, go to the dedicated section of the board: http://www.msfn.org/board/forum/157-install-windows-from-usb/ from which at least two of the mentioned resources were originated. (BOTH using an old version, of this ). Here is the original source (in the now "historical" thread) of usb_prep8.cmd that the linked to sites used: Though of course working, that method/tool is now considered obsolete and we have several, much more "flexible/comprehensive" methods/tools. jaclaz

I have seen everything and the opposite of everything, obviously most of the passive cooled (no fan ones) are slowish/low power. <- please read as "slowish netbooks like" but there are more than a few that have more than decent performance (but usually need a fan or heat pipes or whatever). A good place to have a quick look for models is this one: http://www.logicsupply.eu/mainboards/ (mainly jetway motherboards) besides the historical: http://www.mini-itx.com/ There is also the not-so trivial issue about $'s jaclaz

You mean the HKEY_LOCAL_MACHINE\Enum\PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01 or an actual USB device (under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\USB or where)? That tool is limtied to PCI, by design. Can you see them with USBview (GUI): http://www.ftdichip.com/Support/Utilities.htm jaclaz

Try instead creating (notepad will do) an empty file named "usbdrive.tag" on the root of the USB device first partition. More generally the idea of a check is to check something . If the check fails it is advisable to create the conditions for the check to be successful instead of removing the check alltogether. The real question being of course WHY that file hasn't been created by the WinSetupfromUSB? Still you didn't answer the asked questions (just like checks are there for a reason, questions are asked for a reason): how EXACTLY did you partition/format the device? Or, if you prefer, are you sure that you are booting from a grub4dos MBR (and not from the PBR)? You see, if by any chance you started with a "deviation" from the "standard", it is unlikely that by pure chance your path will cross again the path of the application, the risk being finding a new issue ( to be worked around) at each new step. jaclaz

Actually, it would be easier if you could test the mentioned PCI.EXE and verifies that it can identify correctly your hardware. I mean, we have already a complete list of PCI devices, no need to rebuild it piece by piece by user's contribution, let's see if we can find a way to use the existing lists and tools in such a way to make your procedure easy to replicate to the final users. jaclaz

Oww, comeon, this is unfair to tomasz86 me still thinks he's da man. (as much as I'm still The Finder ) You da man disputes tend to soon become like .... jaclaz

@PROBLEMCHYLD I am not sure to get the last part of your post. The "last four" keys are hardware dependent, every hardware will have it's own Ven and Dev. VEN_1033&DEV_0035&REV_43 is a PCI to USB Host controller by NEC VEN_1033&DEV_00E0&REV_04 is a USB 2.0 Host Controller by NEC VEN_8086&DEV_7112&REV_01 is a PIIX4/4E/4M USB Interface by Intel Corporation http://www.pcidatabase.com/ and: http://web.archive.org/web/20070901052015/http://members.datafast.net.au/~dft0802/downloads.htm (maybe PCI.ZIP can be *somehow* reused in combination with the csv or tab delimited available from tne pcidatabase site) jaclaz

Ah, well, if you say so then I am so. It is however interesting how you are very clever in finding typos in other people's posts but fail to see how - besides the typos - you write in a language that is almost, but not quite, completely unlike English (which is not only about spelling but also about grammar and syntax). An example of a recent sentence that makes no sense in English (besides the senseless CAPITALIZATION): It must be a new kind of selective sight , you might want to apply for the new season of http://en.wikipedia.org/wiki/Stan_Lee's_Superhumans Hmmm , the whole point you are seemingly missing is that I'm already at home here at MSFN . jaclaz P.S.: Forgot: Have a nice day.

JFYI : http://support.microsoft.com/kb/100394/en-us http://support.microsoft.com/kb/101875/en-us http://www.nthelp.com/40/ansiNT.htm http://www.windowsnetworking.com/kbase/windowstips/windows2000/usertips/miscellaneous/commandinterpreteransisupport.html EDIT: And OT , but not much: http://support.microsoft.com/kb/102901/en-us So a new question arises: do the above mentioned MS keyb's apply to later than DOS 5.0 versions (and on later NT based OS's)? EDIT2: Added a couple of links and an almost completely OT one: http://reboot.pro/10122/ EDIT3: This wasn't an "easy" one, but Hey, I'm still The Finder : http://web.archive.org/web/20071222191504/http://home.tiscali.dk/8x305617/provide/ansi.html jaclaz

Sure , but "popular" is not necessarily a synonym of "good" or "better" , it simply means "popular", as well "obscure" or "rarely talked about" is not a synonym of "bad" or "worse", if you prefer I was surprised at your (and submix8's) surprise at seeing this approach work allright..... (as documented - in few places - at least since 2K times ) jaclaz

Ah, well, if you say so. Let's say that the probabilities of myself surviving here are anyway bigger then the ones about you having much further support here for your "Home Edition"-> "something else" change. jaclaz

With all due respect to everyone involved , I wouldn't call this exactly "news" http://www.windowsitpro.com/article/tips/jsi-tip-2520-how-can-i-customize-registry-settings-prior-to-installing-windows-2000- Or am I missing something? jaclaz

Yes and no. CMD.EXE is the DEFAULT command interpreter in NT and later but (at least up to XP/2003, cannot say about Vista and later) there is ALSO COMMAND.COM in the OS. Using under NT COMMAND.COM instead of CMD.EXE is possible (though mostly senseless). Questions are: is the COMMAND.COM in the various NT affected by this "bug"? does the patch work also on these "later" COMMAND.COM's? does it make *any* sense, even if it works, to patch something that *noone* ever uses? OR, we could do a poll: jaclaz

MVP= Microsoft Valued Professional MVP<>Microsoft Vandalism Provider You will probably find out - in due time - how the knowledge a MVP has is - generally speaking - about "canonical" ways to manage the MS OS (i.e. along the lines of what MS suggests, publishes and advices). An MVP is the LEAST likely person to know how to hack a MS OS and even if he/she knows how, the LEAST likely person to tell you (or everyone else). BTW, and JFYI, the contract all signed doesn't have a provision obliging them to help any illiterate, bad mannered, impudent kid around with making senseless modification to his/her OS as you seem to assume. Help is given on a voluntary basis and - usually - to people that ask nicely about senseful matters and takes the time to explain in detail the issues, the goals, the procedures attempted (and failed) etc., etc. jaclaz

Define "reasonable". I guess you would need a KVM switch to make some sense in it's use, but it would be more logical IMHO to actually have the machines interconnected (say through ethernet) and have the "main" one access the other through some kind of VNC or similar. I mean the KVM switch is only a "money" issue, whilst I don't think there is any "consumer grade" floppy or IDE "switcher". If you go through the "one Motherboard only ON at a given time" I guess that the only way out is "convert" mass storage devices to USB and add an internal USB hub. jaclaz

The program was "localized" in 2002 seemingly: http://news.swzone.it/traduzioni/40_RegCompact.html Just for the record, Marco D'amato is most probably the same Marco D'Amato Author of Wincontig: http://wincontig.mdtzone.it/en/ and a very nice guy , if needed I can contact him and ask him if he remembers anything abotu the thingy and it's versions. A .exe RAR self-extracting English version is here (the actual regcompact.exe and ReadMe.txt being dated 18/11/2000): http://www.ndfr.net/telechargements/regcompact-1-0-13.html jaclaz

I may add that my "dinosaur's era" windows 2K and XP installs are as outdated as your newish Windows 7/Server 2008 R2 ones..... jaclaz

This does sound a bit selfish jaclaz

No. IMHO there is some confusion in this topic. There are TWO command interpreters. COMMAND.COM CMD.EXE CMD.EXE has a slightly different syntax, but AFAIK it worls allright and needs NO patches (at least the "original" one in NT/2K/XP). In any case this patch is for COMMAND.COM and NOT for *any* CMD:EXE (if you prefer if *any* CMD.EXE is suffering from this or a similar issue this patch won't do anything about it, as it targets COMMAND.COM and NOT CMD.EXE - the "COMMAND.COM" is hardcoded in the DOS-FIX.EXE) jaclaz

Hmmm. It is very possible since there is a provision to intentionally fail every 10,000 downloads (and successful uses), you may have been simply unlucky. Maybe it is the Windows 7 x64 bits the actual malware (or at least the reason why there is no direct access to the disk MBR and/or the first few hidden sectors) How exactly? (Which tool, with which exact settings, etc.?) You may want to start from scratch (clean the stick) and use RMPREPUSB (and add through it the grub4dos to the MBR). jaclaz

I would say that - surprisingly - there is unanimous or at least 3/3 consensus on this part jaclaz