jaclaz

Well, no, you mean quotes, not initials, but echo "64 bit system" should output: "64 bit System" whilst: echo 64 bit system should output: 64 bit system The need for quotes is for PATHs containing spaces. jaclaz

Well, most people outside a corporation/business/large network (and not *all* corporations) actually have a WDS, and it would be - I believe - improbable that a network administrator would start in 2017 deploying XP images. I mean, while still a lot of businesses still run XP on some machines, surely they already have suitable images and already know how to re-deploy them, because they were originally deployed when the machine was set up, and as you correctly say modern hardware has a lot of issues with XP drivers, so that deploying an XP image on new hardware makes very little sense.. But you are right the OP never mentioned a thumb drive or a CD/DVD. On the other hand he also never mentioned WDS, and as originally stated by Tripredacus the OP posted a "generic" (too generic) questions and never followed with more details. Personally I doubt that OP ever used WDS, both the "old" or the "new" way, and the (as we both say very complex) guide you posted a link to uses not a WinPE to apply/deploy the .wim or booting to the WDS to deploy the image, it stops to when the image is captured. We both concur on the fact that today it seems a huge waste of time to deploy a XP sysprepped image, whatever means are used for doing that, still the OP question was about deploying (even if he calls it "installing") an already existing (sysprepped) image (through WinPE), while the (complex) guide you posted to is about creating a (sysprepped) image (through a VmWare install) and capturing it (through WinPE and WDS). Simplified, the overall process is in four steps: 1) Install 2) sysprep 3) capture 4) deploy It seemed to me like the OP asked about #4 only, giving the first three as already done. whilst the mentioned guide stops just before #4. jaclaz

... while remaining still useful for people with less experience or knowledge ... jaclaz

There is a mis-communication of some kind going on. As I see it the guide you linked to seems a complex way to create a hardware independent sysprepped image for deployment through WDS. I personally find it easier to sysprep an offline image, but the OP question was about deploying an already made syprepped image from a WinPE (NOT through WDS) And anyway all are not "installing XP", but rather "deploying XP", it is not the same as "installing". jaclaz

Yes and no. Sure it is not at all "always valid" (hence the given link to an ample discussion about this and "better" methods) , however - just for the record - the good MS-guys are attempting to make it "valid" as a side effect (or collateral damage) of pushing the senseless UEFI machines, that require an "alignment" between OS and processor bitwidth, Unfortunately, before or later, they will win. jaclaz

Which Windows 10? 32 bit or 64 bit? And (for *whatever reason*) a 64 bit using the 32 bit cmd.exe? There are several ways to check OS, the one you posted seemns fine, but if it doesn't work, see if any of the alternative work for your particular OS/setup: https://stackoverflow.com/questions/12322308/batch-file-to-check-64bit-or-32bit-os More generally (and as a side, side note), the batch is IMHO a bit "redundant", I would simplify it along the lines of: @echo off md c:\e4u_storm copy ocx\*.dll c:\e4u_storm IF "%PROCESSOR_ARCHITECTURE%"=="x86" ( SET Target_Path=c:\windows\syswow64\ ) ELSE ( SET Target_Path=c:\windows\system32 ) ECHO %PROCESSOR_ARCHITECTURE% %Target_Path%regsvr32 c:\e4u_storm\dbvxft.dll /s %Target_Path%regsvr32 c:\e4u_storm\dm.dll /s %Target_Path%regsvr32 c:\e4u_storm\envxrf.dll /s But more than that "as is" it seems (to me) pointless , I mean, no matter if the system is 32 bit or 64 bit, the regsvr32.exe will be in %PATH%, i.e. no matter if it is in c:\windows\syswow64\ or c:\windows\system32\ (or the OS is on another drive, like D:\ or E:\ ) the OS will find and execute it when invoked by simply "regsvr32" or (better) "regsvr32.exe", it is when - for *whatever reason* you want to execute a particular version of an executable and not the one coming with the OS that you need to invoke it with an explicit path. Maybe what you posted is just the "initial part" of a more complex batch, and then there may be other reasons for selecting the "bitwidth" of the OS. However you want to open a command prompt and type manually "echo 64 bit system". What happens? Try echoing something else, like "echo here". What happens? jaclaz

Maybe in 2008 (i.e. when Cannie started this thread/guide) the situation of the internet was a bit different from today and I would also dare to hint that maybe, just maybe, 9 years ago you were a little less knowledgeable and possibly your comment here would have been a little less condescending than today. jaclaz

Not really. The whole point of that linked guide is about sysprepping the image (and then deploying through WDS), not a "normal" install. JFYI, as hinted in an earlier post, a Windows XP can be sysprepped offline (which would simplify the matter): https://web.archive.org/web/20120222113222/http://www.911cd.net:80/forums/index.php?showforum=43 https://web.archive.org/web/20111124134153/http://www.911cd.net/forums//index.php?showtopic=22064 jaclaz

Well, we are not in an online computer assistance hotline following a script, and you are not a common user that hasn't ever seen an electrical appliance before, so the canonical questions: 1) Do you have electricity? 2) is the power cable (or power adapter) actualy plugged into mains? 3) Have you tried flipping the on/off switch on the device? 4) Does any light blink or any sound (or movement) come from the device when it is powered up? Were given as already asked for and replied positively. The next questions remain: 5) Is it connected to the "right" USB port? 6) Do you have any other (USB) printer (with "manufacturer" drivers) to test that the USB printing support in the install is working? As that would exclude a malfunctioning USB port/bus on either the computer or the printer and some possible issues with the chosen printer port in software. AFAICR (it is ages I don't install a USB printer on a 9x machine) there were issues with selecting the port as even with the "wrong" driver (but with the "right" port) *something* happened (lights blinking, carriage moving, garbage characters printed, etc.) As a matter of fact while - generally speaking - for years (not anymore I believe) all HP printers were good, sturdy, work mules, the real issues with them has traditionally been the accompanying software (and drivers) and in many cases to actually install (having th eactual original, valid, driver) was a nightmare, one example among the many (please note how these are actual "official" HP support pages ) : https://support.hp.com/ee-en/document/c00523824 https://support.hp.com/gb-en/document/buu01858 The "nearest" model I could find a driver for is the D2360, but as often happens unfortunately with driversguide files, there is no guarantee whatever that the file actually contains what is in the download page description and of course no guarantee whatever that a D23xx may work for D42xx. http://www.driverguide.com/driver/detail.php?driverid=794993&si=b6b7e34bceca9b15578c4e979e0c419d However, at a quick check (Universal Extractor can be used to expand into a sub-directory), it does contain 9x drivers. jaclaz

Good , everything is back to normal improbability level .... jaclaz

Do you mean a message *like* "A DVD/CD drive device driver is missing. If you have a driver CD/Floppy please insert it now..." or "A required CD/DVD drive device driver is missing ..." I seem to remember that you need to have the USB device set as "non-removable, *like*: http://www.msfn.org/board/topic/148700-install-windows-7-from-any-usb-ntfs-partition-grub2/ Or is it some other error? (post the EXACT error you get). jaclaz

Sure, this is normal, imagine that the printer is doing someting similar to a computer boot. Unfortunately there is no way to answer , you will need to check several things: Is the printer listed? (besides in "Printers" also in "Device Manager") Is it connected to the "right" USB port? Do you have any other (USB) printer (with "manufacturer" drivers) to test that the USB printing support in the install is working? jaclaz

As long as it is not past the comfort zone of the plastic part at hand, that is fine jaclaz

Removing the screen is NOT needed for the CD swap. Anyway the hinges (and screws) are inside plastic caps, see this photo, the right side has the cap off. Use this page (spares for this model) to have a visual reference to the parts: https://store.emprgroup.co.nz/HPc-46816-6-compaq-presario-notebook-pc-1065-us-282730-005.aspx jaclaz

Tu quoque ... jaclaz Seriously, as long as an "old" version working with XP remains available that would be just fine , after all it is not like new, strange ways were added (for XP) in the last several releases,

The message is repeated two times because it is related to two files: bootstx.dll bootstx.dll.mui Most probably (for whatever reasons and whatever those files are) they are compiled for an earlier version of the OS. This would make sense for LiveXP (as most programs are now compiled for MajorVersion 6 and Minor version 6.1 or 6.2 and anyway XP doesn't uses .mui files) but that shouldn't apply to a 7 based PE. , unless somehow a later (10) version is in use? jaclaz

Wait a minute. When (exactly) are you having the 0x0000007b Stop Error? Describe what you can do BEFORE the BSOD. What I suspect is that you are having an issue in installing the XP from the USB bus. Try using WinntSetupfromUSB on a stick (as opposed to your USB CD/DVD drive) as source: http://www.msfn.org/board/forum/157-install-windows-from-usb/ (or one of the other available methods available in that sub-forum) jaclaz

Hmmm. You must have a sorta of obsession with that particolar make/model jaclaz

Sure, via CUPS, but that would be a "Print Server": https://pimylifeup.com/raspberry-pi-print-server/ Not entirely unlike what you do with a TCP/IP or LPR port on Windows NT series OS's or with a hardware print server. jaclaz

... must be either a part time complicated job or a partially complicated job , I would exclude English grammar teaching, however . jaclaz

It seems like your case has nothing to do with the specific failure(s) discussed in this thread, You are seemingly the unlucky owner of one of the worst hard disks of all times : https://en.wikipedia.org/wiki/ST3000DM001 reportedly those drives simply fail, after some time, in the highest percentages ever recorded. These failures can - in some cases only - be repaired by professionals, no DIY available, jaclaz

I.e. much more than what you manually measured? Or do you have 3/4th of a whole minute in reaction time? jaclaz

My guess is that it is a "lost cause". If possible at all, I would suggest however that instead of the stupid empty blue screen there could be the possibility to have a message like: And the word for today is: http://www.dictionary.com/browse/consistency in the meanings #2 and #3, jaclaz

Sure, you are right: 5) Do you have a console? Go for a gaming console OS jaclaz

Oww, come on , they were so much different that a few hex edits changed the one into the other, you talk like you never knew that NTtune, NTSwitch or TweakNT existed. Don't worry, all links to the tools are invalid now: http://smallvoid.com/article/winnt-upgrade-server.html And differences from XP Home and XP Professional? (I mean the missing security tab/SCM which could be enabled by using a NT 4.x freely downloadable from ftp://ftp.microsoft.com/bussys/winnt/winnt-public/ ) Now from XP to Server 2003 they actually made some differences, but then how much different is XP64 from Server 2003 64 bit? And don't forget all the stupid memory accessible artificially limited in Vista and later .... jaclaz