jaclaz

So, all you want to do is a slipstreamed SP2 XP pro install CD? Can you post a link to the guide you used? Also, saying "I used CDIMAGE" says nothing, I mean WHICH command line options you used with it? You can also try using nlite to create a slipstreamed SP2 XP pro install CD: http://www.nliteos.com/ http://www.msfn.org/board/nLite-f89.html jaclaz

As expected: http://europa.eu/rapid/pressReleasesAction...;guiLanguage=en jaclaz

The above makes me wonder... ...you could use SUBST: http://www.computerhope.com/substhlp.htm to map the \Main and the \Sheets to a "plain" drive letter. jaclaz

There are some paths and filenames ENCODED inside SETUPLDR.BIN. Tipically: \I386\ on CD's \minint\ on HD like devices (with the /minint switch \$WIN_NT$.~BT\ for pre-installation files on HD like devices \CMDCONS\ for Recovery Console If your CD searches for anything inside \$WIN_NT$.~BT\ instead of \I386\ some file is missing or the build procedure is wrong. If the file is missing AFTER the pre-install bootfiles have been copied to HD, again something is wrong, probably in txtsetup.sif, but cannot say for sure. HOW did you create the CD, I mean WHICH tutorial/howto/method did you use to create the .iso? WHEN exactly in the booting process does it happen? What EXACT error code does it show (like error 18)? jaclaz

Yep, but if, for any reason, H:\Main and H:\Sheets are "far apart" physically on the drive, the seeking back and forth may be increased. I would test both solutions with the same set of files and see if there is a noticeable difference in speed, the hardware specs appear to be extremely low. jaclaz

Well, then, yes, the: For %%A in (H:\Main\*.*) Do Copy /Y H:\Main\%%A C:\Data1 For %%A in (H:\Main\*.*) Do Copy /Y H:\Sheets\%%A C:\Data2 Should work allright. jaclaz

Well, check if when you do "Save as" in notepad in lower listbox you have by default: ANSI Unicode Big-Endian Unicode UTF-8 The kind of error you report is often reported when one tries by mistake to use a Unicode text as .cmd, it MUST be ANSI. jaclaz

Point is, is there a reason why not using xcopy? http://www.csulb.edu/~murdock/xcopy.html jaclaz

@trefrog I understand you are newish here , and I also understand that what is usually defined as "common sense" is often unexpectedly UNcommon, but come on, the board is to post shortish messages and code snippets, NOT several hundreds of lines of text. Please use the attachment feature, attaching a FILE, whenever you have LOOONG things to post... jaclaz

Maybe, if you paste a few lines of the batch, NOT of the output, near the one containing: it may help. Please do the above TWO times, one using Notepad, and the other one using Wordpad to open the batch file. jaclaz

Well, it's not like the EU commission took Microsoft name out of a hat and forced the Company to do something just because they fancied it. Anti-trust provisions are Laws, and they should be respected. I am fiercely against speed limits on highways, I like the way the Germans manage it, but nonetheless, should I get a ticket for speeding I would pay the fine. I suspect, and mind you this is my personal opinion, that the fact that Microsoft and it's lawyers used every trick of the trade, and even one more to obstacle (lawfully, of course) or delay the investigations did not help much MS position, remember that the original EU decision dated back to 2004! But the decisions are very well documented and supported, maybe the words of Mario Monti: show exactly the main aspect where EU antitrust laws differ from US ones. And we are not talking of code (open or closed) but rather about protocols, to use the words of the Commission the "the interoperability information": jaclaz

@jrf2027 FYI, you can well try grub4dos, that can reside on NTFS partitions as well: http://www.boot-land.net/forums/Grub4dos-f66.html grub4dos has a number of added features, specific to MS based systems, DOS and NT. jaclaz

Yep, it's a voluntary move, of course : http://enarpri.org/Article.php?article_id=317 2007 The decision was confirmed in September 2007: http://europa.eu/rapid/pressReleasesAction...;guiLanguage=en http://europa.eu/rapid/pressReleasesAction...;guiLanguage=en See this also: http://www.itnews.com.au/News/63623,eu-for...atent-dogs.aspx jaclaz

Never had an occasion to try it, but there is an update thingie made by asiekierka : http://www.msfn.org/board/Integrating-NT-4...wto-t99030.html cannot say if there is anything useful for you within it. jaclaz

@fizban @arfett I guess that what mehargags asked for is a way to have the SAME drive lettering WHATEVER system is currently booted. This is VERY recommended, as one time or another, you will just forget in which system you are currently booted and save a file in the wrong drive, possibly overwriting a different version of a file: http://www.msfn.org/board/Problem-drive-letters-t25127.html Surely he can change letters to "other" drives, but changing Boot and System one is tricky. @mehargags See this also: http://www.msfn.org/board/Dirver-letters-W...ion-t53177.html Cannot say whether Vista uses some strange ways, you should also check this site: http://www.multibooters.co.uk/ jaclaz

It is possible (but cannot really say ) that Vista and (maybe also) Vista64 still relies on the migrate.inf file. It's a loooong shot, though. Do check this seemingly unrelated post: http://www.msfn.org/board/Installation-end...ve-t112923.html and links therein However, since you are going to reinstall VISTA anyway, I would try using a PE of some kind or even good ol' DOS and change the entries in the partition tables, in the MBR and in the EPBR to make the partitions "hidden" (simply changing first hex number of partition type from "0" to "1"): http://www.win.tue.nl/~aeb/partitions/partition_types-1.html Another possibility is that rather than in the order the partition is phisycally on the hard drive, Vista setup looks at the order in which partitions are listed in the MBR and EPBR, in this case exchanging the orfer of the entries may get the desiref result. jaclaz

Reinstalling properly would be easier. It is possible to change a Boot or System Volume letter, but really, really tricky and really NOT advised. However: http://www.goodells.net/multiboot/index.htm http://www.goodells.net/multiboot/partsigs.htm Read also these: http://www.911cd.net/forums//index.php?sho...c=19663&hl= http://www.msfn.org/board/Change-Boot-Driv...ion-t90495.html And be very careful, even a minor error could (and probably will ) lead to an unbootable system.

Well, no. Electronics components have a working temperature range, usually comprised between -30° C and +65° C, for "normal" grade components, usually -40° C and + 85° C for "industrial grade components" with some components that allow for a -65° C to +125° C : http://www.extremetemperatureelectronics.com/tutorial1.html WITHIN the given temperature range, there is an "ideal" working temperature, that almost invariably is around the middle of the allowed range, more or less amounting to a temperature at which the users of them (humans) live and operate them, i.e. +0 °C to 40 ° ,but WITHIN designed range, components behave anyway WITHIN specs. The "freezing" as well as the "tapping" method to revive a dead hard drive, can, in VERY RARE occasions allow for a TEMPORARY revival because they may resolve a mechanical problem, including defects in the soldering or connection of a component. Remember also that every year hard disk technology changes dramatically, and what may have worked in a particular occasion, on a particular type of failure, on a particular drive model/capacity most definitely won't work with next generation of drives. You can also try shouting very hard at it, using a magic wand and some spells on it, you can freeze it: http://geeksaresexy.blogspot.com/2006/01/f...cover-data.html as well as "boiling" it: http://www.mandible.net/2007/11/24/how-i-r...ble-boiling-it/ But ALL of them should be a LAST, LAST resort, only after you have decided that your data was not precious enough for you to attempt a recovery by a professional, and you have nothing to lose anyway. If it's an electronic problem a more "rational" approach like this: http://www.deadharddrive.com/ may work, but not on recent drives where the board is "coupled" to the innards. I would suggest everyone to check the above links and this one: http://www.hardwaresecrets.com/article/245 then judge themselves what would be more wise to do. jaclaz

Hmmm, besides the fact that is very difficult to read what you write (why using Arial Black? ), I guess that you failed to actually read the License of nlite, that last time I checked was this one: (bolding is mine) jaclaz

NO, but in most cases a relative can guess it, no need for "social engineering", the knowledge of habits, passions, hates, birthday dates, names of dear ones, etc., etc. should be common between the members of a same family. You joking, right? The point is NEVER, NEVER, and I mean NEVER allow access to a PC you want to keep private, if you do, do it only under your direct and attentive surveillance, otherwise it may well happen that, in the short turn of five minutes: ALL YOUR PASSWORDS ARE BELONG TO US! jaclaz

Well, it is possible to use the internal hard disk as hdb, though there is a RISK in making the "working", possibly "system", drive accessible from the VM, it would be better to use as hdb an image of the drive, rather obviously all drivers instealled within the VM may or may not be compatible with real hardware... Qemu "internally" should see hda as \\.\PhysicalDrive0 and hdb as \\.\PhysicalDrive1 LOTS of testing is needed before "advertising" this possible way, allowing direct access to system drives is VERY like playing with explosives.... jaclaz

Mind you, completely and utterly UNTESTED but read FAQs here: http://fabrice.bellard.free.fr/qemu/user-doc.html http://kidsquid.com/cgi-bin/moin.cgi/Frequ...yAskedQuestions http://calamari.reverse-dns.net:980/cgi-bi...bb75619b572be-2 jaclaz

I doubt you will find one here. Or are you looking for a suggestion? What about: arachnospellingbuster It may fit.... jaclaz

Well, NO, the detail would be a list of all single settings you used with nlite, all apps you added, all choices you made with WPI and Unattended CD Creator, with those FULL details, someone may be able to understand where the problem lies, though checking such a mass of info would take, of anyone would take the challenge, a lot of work. You must "reduce" the possibilities: Do steps 1. and 2. only, burn the CD and test it. If it works, do later steps 3. 4. 5. , burn the CD and test it. If it works, do later steps 6. 7., burn the CD and test it. This way you will know at least which app creates the problem. At this point check what could be related to keyboard and try removing/adding it or try making just a small number of things and test the result, by the way you could use a Virtual Machine instead of burning test CD's. jaclaz

@all It seems like the other day was "wish" day on boot-land and Nuno Brito has started working on this app, there is already a fully working (but still missing some asked for features) release here, ninf 1.1, enjoy: http://www.boot-land.net/forums/index.php?...ic=3960&hl= @damian666 It seems like there is not anymore need for your work, but thank you very much for your offer to do it , I am sure I can find some other interesting project for you , should you still be willing to write something for the community , again, thanks for your kind offer. jaclaz