jaclaz

@dencorso I guess that these old news: http://arstechnica.com/information-technology/2009/10/microsoft-mulling-128-bit-versions-of-windows-8-windows-9/ are also a no-no? jaclaz

I am clearly missing something, but if I go here: http://download.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/ENUS/x86/MSEInstall.exe through the Wayback Machine: https://web.archive.org/web/*/http://download.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/ENUS/x86/MSEInstall.exe I can download a MSEInstall.exe for x86 from a snapshot taken on March 25, 2014. Files inside it (opened in 7-zip) are dated October, 23 2013. The file downloaded from Filehippo is EXACTLY the same. This should mean that the version for download on MS servers was the same at least up to March 25, 2014. jaclaz

Here (in the dark ) I have SP2 (with a number of "selected" updates and/or mods/tweaks) The reason being that I never found the time and/or a real reason to update to SP3: simple, straight, not tortuous, nor contrived explanation . jaclaz

Excellent (for the supported hardware ) Remember that at the time: there were NO SATA bus/drives, only IDE ("standard") and SCSI (very common, as they were faster, on machines with NT 4.00 installed) and very well supported (possibly also because you spent big bucks on - say - Adaptec cards and fastish 10,000 RPM Seagatye Cheetah drives) See: http://redhill.net.au/d/62.php there was NO USB bus there was NO Wi-Fi there was NO buit-in support in NT for PCMCIA/PCCARDS (but there existed third party tools for it) there was NO AGP bus video cards were simple video cards and 64 Mb or 128 Mb was the total amount of RAM you had in your whole system (as in "not 1/4 of the amount in the cheapest video card you can find ")Now, even today, if you have an issue in any NT based system, it is very likely that it is connected to a driver of one of the 6 above. jaclaz

I see . The easiest is probably using the first method submix8c posted, BUT that set of instructions is assuming that a Linux is used, so you will need to adapt the instructions to your OS environment (i presume XP). If you need help just say so, though most probably you will need to make a few attempts (having a Virtual Machine to test the .iso would be advisable). jaclaz

And you have GOOD reasons for this When (and IF) there will be an official statement by MS, then we will have something (apart from hearsay, speculations, vague anecdotal evidence and the like) to discuss. jaclaz

Windows XP or Windows 98? Your question as is does not make sense (to me). Care to explain a little better what you would like to do? jaclaz

Let us assume that (from the info I managed to EXTRACT from you on the now closed thread) you are using Rufus. You are having a 0x0000007b Stop Error, we know that. You were already told on the other thread what the possible causes can be. Now, provide on your next post AT THE VERY LEAST these info: the EXACT data about the computer you are trying to install the XP to <- (is it a laptop or a desktop, which EXACT make/model, etc.) a detailed enough description of the source that you are using (XP Home/Professional, SP level, if modified in ANY way, like nlited, etc)or in other words, what was already asked to you and that you completely failed to provide, which is needed to try providing some assistance, otherwise I will also close this thread in no time. Or, if you cannot do the above (or do not want or it is too painful) , refrain from posting at all, and try first the other tool that was suggested to you instead of Rufus, WinSetupFromUSb: http://www.msfn.org/board/topic/120444-how-to-install-windows-from-usb-winsetupfromusb-with-gui/ http://www.winsetupfromusb.com/ You are given one (and only one) chance, use it wisely. jaclaz

....it can be used with wait. WAIT... What? An image is worth a thousand words: jaclaz

If you are having a 0x0000007b it is likely that there will be no difference whatsoever between CD or USB (stick or disk). The issue is more probably in the source files. Since Rufus is only one among the several methods, it is also possible (but I doubt that) that *somehow* the same source files may work with another method/tool (like the mentioned WinSetupfromUSB). IF the 0x0000007b is due to a SATA driver missing, you can change all the hard disks you want, but the SATA interface (for which a driver is missing) will remain the same (and continue to proiduce a 0x0000007b). On the other hand - and it depends on the hardware, for which you did not provide NO data whatsoever - it is possible that the BIOS allows to set the storage subsystem as "IDE compatibility mode" (or similar), i.e. emulating a plain IDE/ATAPI interface for which the drivers are surely included in the (unmodified) XP source. Whilst I am sorry for your suffering over these three days, I really cannot see what is so difficult (or painful) in posting some actual data, which is needed in order to hopefully try and help you. I mean, I can install XP in - last time I counted them - 7 or 8 different ways, ALL succesfully, it's you that are having a problem, it is your problem (that I am trying to help you with, BTW for free). Next time, read this: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html attentively BEFORE asking for help and comply with it, I am getting tired of the "I'm ill, doctor. Help!" approach. When (and if) you are ready, start a new thread, I am closing this one as it leads nowhere. jaclaz

I would call it "poor" or "short" Typing this on my IBM "M" keyboard, clickity, clickity, click. And yes I have no fancy "windows" key . JFYI: http://www.msfn.org/board/topic/155361-good-mechanical-pc-keyboard-amigaatari-xl-feeling/ jaclaz

No. That is theory, practice is different. In the US (like everywhere else BTW) it greatly depends on the actual name of the three letter agency and n how much they want to know from you. Look up what an extraordinary rendition is: http://en.wikipedia.org/wiki/Extraordinary_rendition If "they" are after you, "they" will get you (and get whatever information you may have from you, one way or the other). Usual comment: ...but, but .... that is illegal ! Sure it is, and you can sue them (afterwards) IF you manage to get back jaclaz

My personal advice is to NEVER use/trust, for ANY reason CS (Cable Select) as it is in theory a good thing but has been in practice implemented poorly on a large number of motherboards (and possibly hard disks), of course there are usually no issues if it is the only device on the cable. If the disk is marked ATA33 you can use a 40 wire cable, if it is 66, 100 or 133 you MUST use an 80 wire cable, and remember that this latter is "colour coded". See here: http://www.msfn.org/board/topic/160758-windows-98-on-floppy-disks/?p=1023838#entry1023838 AND links in it. jaclaz

Good (not that a BSOD is "good", but the 0x0000007b one is very common and it is usually easy to solve ). The 0x0000007b mean "Inaccessible boot device" and it is normally caused by the install source missing the appropriate (nowadays SATA) Mass Storage device driver. Another reason why you should post some details on the hardware . You can either slipstream the appropriate driver in the source or use a "F6 floppy" for it. Post details on the hardware and we will be able to provide you with further support. BTW, this would be FAQ #3: http://www.msfn.org/board/topic/116766-faqs/ jaclaz

Good to know that I contributed (a little) to another happy bunny : http://www.msfn.org/board/topic/128727-cant-access-repair-my-pc-option-via-f8-startup/?p=828512 The different name of the license in lsview it's "queer" however, maybe it doesn't like the "dots" (but then why would it miss the "2"?) I guess it is one of those (unfortunately happening too often with complex network/domain settings ) issues that should be categorized as "voodoo" and solved by magic (or luck) more than anything else. jaclaz

Sure , though I see noone ever doubting it jaclaz

Well, the idea is that you: choose one (and one only) among the programs if it works, good if it does not, report EXACT errors, COMPLETE description of what happens, etc., etc. it is possible - mind you - that the error comes from your (modified/nlited extremely/non-original/whatever) source, or from an actual issue of the actual hardwareFrom your posts I cannot even understand if what is not working is Rufus or WinntsetupfromUSB Try describing what EXACTLY you did and what EXACTLY you get (and please also some data bout the actual hardware you are using). Sometimes even only writing down the steps performed is enough to understand which one causes the issue. The 0X000000C8 BSOD is "not common", and usually is connected to *some* driver, what else can you read on the Blue Screen? jaclaz

And possibly it can even be a hardlink/graft-point. Added: If both are uncompressed, as JFX suggested, not if compressed, as Atari800XL "alternate solution" posted on RyanVM. http://www.ryanvm.net/forum/viewtopic.php?t=6438&start=2920 jaclaz

This might help: wmic DISKDRIVE GET SerialNumberjaclaz

Well, besides being "old news", if I were the FBI and I was actually capable of breaking the truecrypt encryption, I would never admit it. JFYI, some recent possible "enhancements": http://reboot.pro/topic/19690-truecrypt-patched-for-supporting-arbitrary-offsets/ and, if you change the three letter agency name, remember the XKCD's approach to the problem : http://xkcd.com/538/ jaclaz

@Evilgoku There are several different ways to install XP from a USB (stick or hard disk). None of them AFAIK require (or suggest) the use of UltraISO. Why don' t you do like everyone else and just use either among WinsetupFromUSB: http://www.msfn.org/board/topic/120444-how-to-install-windows-from-usb-winsetupfromusb-with-gui/ http://www.winsetupfromusb.com/ or Akeo's Rufus: http://reboot.pro/topic/17902-rufus-v130-has-been-released/ http://rufus.akeo.ie/?locale=en_US or any of the other methods/tools posted here: http://www.msfn.org/board/forum/157-install-windows-from-usb/ as "sticky"? I mean, sometimes re-inventing the wheel or hot water is a nice thing , but the reinvented wheel needs to be rounder and the reinvented hot water hotter.... . jaclaz

Nice . Though I *need* to say something about this: JFYI: http://www.robvanderwoude.com/prompt.php jaclaz

There are a whole bunch of "DOS replacements", some are listed here: http://reboot.pro/forum/13-freedos-and-dos/ one of the "most promising" is (IMHO) nx-dos: http://reboot.pro/topic/4755-nx-dos/ which is still in active development: http://sourceforge.net/projects/nxdos/ http://digitalatoll.com:8080/tawhakisoft/nxdos.html The DR-DOS/NOvell/Caldera/OPENDOS/Devicelogics saga is IMHO way too complex to understand the exact licensing terms http://en.wikipedia.org/wiki/DR-DOS though it has it's followers : http://www.drdos.net/ http://drdosprojects.de/ But nothing "win9x-like" AFAICR/AFAIK. Some GUI alternatives (for Dos) were talked/discussed/hinted about in these seemingly unrelated threads: http://www.911cd.net/forums//index.php?showtopic=16754 http://reboot.pro/topic/623-minibox-rides-again/ and of course MCshell: http://reboot.pro/topic/752-mcshell-a-shell-look-a-like-to-mac-and-win31/ What I personally liked the most was the NewDeal/Breadbox Ensemble: http://en.wikipedia.org/wiki/NewDeal#NDO OT , but not that much , what you should really-really have on your 9x/Me setups, however, would IMHO be the Win9x CMD.EXE: http://reboot.pro/topic/2392-nice-find-cmdexe-for-win9x/ jaclaz

@Rosen88 Let me understand this. You followed TO THE LETTER the set of instructions that ace2 kindly posted here: http://www.msfn.org/board/topic/170850-aero-glass-for-win81-121/page-37#entry1073548 http://www.msfn.org/board/topic/163570-aero-glass-for-win81-rtm-rc3/page-16#entry1058721 which worked for several users, including kupapiachu,raiden89, dhjohns: http://www.msfn.org/board/topic/170850-aero-glass-for-win81-121/?p=1073684 (same exact info, updated), Soukyuu: http://www.msfn.org/board/topic/170850-aero-glass-for-win81-121/?p=1074635 sberdes, and most probably a large number of other peeps that didn't post here, and it fails for you? WHAT is (EXACTLY) the error you get? jaclaz

You see, the point is not bigmuscle telling lies (according to you), the main point is all the other users posting how it works flawlessly for them. Of course it is possible that, bigmuscle AND all the users that reported success are liars , but statistically it is more probable that a PBCAK exists in the cases of the people for which it does not work (and that additionally have your same negative, unrespectful and impolite attitude). jaclaz