submix8c

To tie it together - http://www.msfn.org/board/topic/171482-get-windows-xp-x86-to-recognize-more-than-4gb-with-pae/#entry1094603 I assume that you *only* applied the patch, or did you add certain parameters in BOOT.INI? You never specifically said over there.

I assume you've read this Topic (Stickie List)? http://www.msfn.org/board/topic/95815-important-stickified-pinned-959898-seme-topics/ For the RAM, in particular this? http://www.msfn.org/board/topic/118097-day-to-day-running-win-9xme-with-more-than-1-gib-ram/ Above is pointed to in Post #4 of this (found in first link above). http://www.msfn.org/board/topic/129983-how-to-install-windows-98-in-modern-motherboards-using-more-than-1-gb/ HTH Addendum - I don't know what may be included in your particular Unofficial SP. I will assume it's an older version of the original project in your language.

Capacitors have a "small thin space" between them and the MoBo board. If there's any particulate under them, that could couse a "short". And I agree that you should check from within Windows, if possible, to be sure.

Source of your troubles? http://www.poweriso.com/tutorials/how-to-make-winxp-bootable-usb-drive.htm You've used BartPE ISO. All well and good, but you *may* be doing something wrong.

What are you getting at anyway? Why would you need to know the Volume Label? Here's what you need to know for your PC - http://dellwindowsreinstallationguide.com/download-microsoft-windows-and-office/download-microsoft-windows/download-windows-8-1-retail-and-oem-iso/ Enterprise is *strictly* (AFAIK) for Businesses and require a KMS/MAK Server to "activate". Professional is comes as OEM and Retail. Retail you just enter the Supplied Key (no SLP) - OEM requires the Key to be in the BIOS (SLP). Whether you can enter the BIOS Key using an MSDN or Retail, I have no clue. In either case, it still will (AFAIK) "phone home" to ensure you're Genuine. HTH edit - Google "windows 8.1" editionsand see what's going on with the differences between all of them.

I'm supposing you've already read the instructions for the USP? http://www.htasoft.com/u98sesp/ And also followed the link to the *complete* instructions? You *seem* to be following them. If you have any problems, I would suggest that you request moving this topic to here - http://www.msfn.org/board/forum/91-windows-9x-member-projects/ ... or else it won't get noticed. And I guess you're aware that this Sticky Topic is *one* of them that you refer to (besides KernelEx) - http://www.msfn.org/board/topic/61749-98-se-sp-332/ The Members Projects is the place for what you're talking about doing. If that's the route you've chosen, by all means go for it. Just be aware of all the Stickies under the 9x Forum regarding RAM, etc. I say that because you haven't even said what your Machine Specs are, just that you did a Fresh Install. HTH

Can you provide the EULAID's (e.g. "EULAID:WinBlue_R8_1_etcetc")? Only thing I can find is it should begin with "IR1_" something-something...

Are you using the UPnP facility? Google this UPnP mp4Further, seems that UPnP (of which I do *not* have installed) is for streaming a variety of files between a variety of devices (e.g. XBox). You might want to check on that. It *really* sounds like you have one of those PC's set up as the "server". HTH Addendum - be aware that I'm not absolutely sure this is related, since (as I said) I don't fiddle with UPnP whatsoever.

Maybe http://howto.wired.com/wiki/Stream_Your_Music_Online

Realtek seems to have a problem, according to this (don't know what MoBo, but...) - http://www.cybernetman.com/kb/index.cfm/fuseaction/home.viewArticles/articleId/109 http://www.boredsysadmin.com/2008/03/windows-xp-sp3-and-microsoft-hd-audio.html http://timwheatley.org/www/2008/03/02/realtek-hd-audio-fix-for-windows-xp-sp3-kb835221 http://en.kioskea.net/forum/affich-7670-no-sound-after-installing-windows-xp-professi This one talks about a Conexant driver - https://social.technet.microsoft.com/Forums/windows/en-US/9a2633eb-50ba-4585-b2ce-6859f0e21079/uaa-hd-audio-windows-xp-sp3?forum=itproxpsp http://www.davesdrivers.com/forum/showthread.php?tid=2008 I assume you have SP3 installed. Seems to be a "bug" or something. I haven't actually tested any of this so... HTH and good luck.

FWIW, my (older PC) BIOS (running pre-Win7) lists SATA-0 as Disk0 and PATA-0 as Disk1 (the OS/Boot drive). IOW, once a SATA is connected, the DISKn "shifts", whether I like it or not.

BTW, There's both an x86 *and* an x64 version of Server2003R2. Rule of thumb - you can't go x86<->x64 (for *any* OS) becuase it has to be the same "bitness" to "switch" between "normal" to R2. IOW, x64 will have to installed be from "scratch". JFYI. (BWC probably already knew that, as well as you...)

Check the Security Level Settings in the Intranet/Internet Zones in the IE Options. I had a heck of a time "turning off" those stupid blockages. See each line item within it and look up what it "does". I'd list mine for you but ATM I'm drinking Neros (cheap beer). Pulled an all-nighter figuring out how to allow "download" of a DAT file from my website. (needs MIME setting for the given file in the IIS Web Setup). Sorry I can't help anymore (other than my Settings). There *has* to be an answer...

I believe Ponch may be right about the SP3 Pre-Integrated bit. @Vinifera, that *may* work (manual integration), based on Ponch' response.

@glnz - A] Yes B] Nope, sorry - see this http://www.msfn.org/board/topic/173422-xp-mode-use-nlite-to-install-only-post-sp3-updates/?view=findpost&p=1093743 C] No, it will not I started to "experiment" with "reassembling MS XP-Mode Install" from XP-Mode pre-install-files, but it's (well... read the post). I guess that will just be a "project". You *could* use an OEM/Retail XP Pro, get the MS "internal" Key and insert the OEMBIOS files, but there's still the matter of certain VM-oriented files. I believe I have figured them out, but no time to test the theory. I just got an old PC reassembled and still have to hook up my Win7 PC again. Theoretically, you could use -X- files and a script, but it *may* cause a "gltch" in that Optional Components (Add/Remove MS Components) won't be installed and -X- files include (I believe) some fixes for them. Stick with "Plan A" (WSUS) for the time. I'll revisit this after further testing (whatever...).

Thank you, Ponch for the further link. Please be aware that Post#6 "semi" corrected my earlier post that you quoted. I now *completely" stand corrected. It *may* be that WSUS automatically does that regardless of the User being an Admin or not by default. Otherwise, why in the heck would it do that (noting that Restricted Users *may* not have the Update ability)? There are exactly *two* references in that link that simply don't explain *why*. Kind of "odd" that it may be necessary. I must be missing something. Google "WSUSUpdateAdmin"It seems that it involves the Reboot (for some reason) and that *could* cause a problem if pysically interrupted. Edit - I also noticed that even though WSUS is downloading via the Official WSUS files, they *may* be incorrect as far as Superceded because I've compared their XP SP3 to UDC and found *many* to be unnecessary (including IE7). Indeed, if you install *all* Components in Add/Remove and use an Install Script along with the -X- UDC files you need reboot only *once*. Them go back and uninstall the "extra" if you really didn't need them. Take a look at the List compared to -X- List/ChangeLog. IOW, WSUS Offline isn't that smart - same as/because MS does the same thing if you go to Windows Updates (download/install/rinse/reboot/repeat). Try it and find out as this subject has been broached before. Here's the explanation of why -X- doesn't download redundant/superceded Updates - http://www.msfn.org/board/topic/155381-which-post-sp3-updates-will-not-integrate-in-the-nlite/#entry999188 Bear in mind that I have "ignored" the Generated CAB files and used the Originals with the Home-Brew Script. The -only- ones (AFAICR) that required reboot was IE8 Fixes (after IE8 install) and MediaPlayer11 Fixes (after it was installed) because of the replacements in the Registry/FileSystem required for what is *really* an "Upgrade". See this for a Functional Sample Script - http://www.msfn.org/board/topic/152020-batch-script-for-windows-software-updates-installation/ Note that it'll *still* install Fixes that you may include for Add/Remove Components that you haven't Optionally installed. Not knocking WSUS Offline, just saying it has some "holes" in the process that can't be circumvented since MS is the one that screwed up.

Try using the NAS Machine Name. I also have an entry for mine using "http". Here's my Full Intranet settings (as shown in IE). hcp://systemhttp://localhosthttps://localhosthttp://martin-entltd.no-ip.orghttp://<computername>I've replaced my Machine Name. Just (try to) use the NAS Computer Name. I also have "Reqiure Server Verification" turned off (unchecked). HTH Yep, that appears to be the problem! See this - http://forums.dlink.com/index.php?topic=13033.0 Edit - give it a go. If it works, get/create the REG entries, and reinstall without IE, if it suits you.

Or Vista. It "breaks" the acceptance of the Product Key. http://www.msfn.org/board/topic/158294-nlite-officialunofficial-faq/ Basically, anything NT system newer than XP SP3. Generally speaking - Win2K, XP, 2K3 only. Haven't attempted on NT4 but *may* work. nLite requires ".NET Framework 2.0 SP1" x86/x64 (depending on OS). AFAICR, you need to slip an x64 on an x64 OS. Info on OS that supports ".Net Framework" - https://msdn.microsoft.com/en-us/library/ms973853.aspx It *appears* thae v2.0 will install on NT4, so *maybe* the SP1 will install. HTH Edit - Nope on NT (any NT). dotNET v1.1 will install on NT4, but not v2.x. https://msdn.microsoft.com/en-us/library/ms229070.aspx ...like this - http://www.petri.com/installing-net-framework-1-1-on-windows-nt-4-0-server.htm

"xpmuser" is the Default User account (google that). Since it uses RDP, I'm guessing that WSUS Offline needed to create a "special" account in order to run itself. I can't seem to find anything that specifically states which User Group that account initially goes under, but I'm betting that it's a Standard (restricted) User, set up in the Windows 7 Host to allow for RDP/XP-Mode and is *not* an "Administrator" (could be wrong). As I said, I don't have my Win7 box plugged in/running ATM so I can't check my theory. All indications are that it has something to do with User Priviledges (just a guess). You could check on that by going into "User Accounts" and see what Group it's under. Fair warning, I wouldn't mess with it (from what I've found) because it might "break" the RDP interface between Win7 and XP. Also, as I said, see if you can "add" a New User Account (only an Administrator *usually* has this ability). Sorry, but I don't have time to "play" with mine so I can't give anything other than "what I know, what I can find, and what I can *assume*"

Not really sure if it's the same file, but it can also be found in IE401 (SPx) or IE5 (and above up to but not including IE6) inside "SETUP95.CAB".

I shudder to think what the End User would say if something "breaks" and the OEM gets blamed. Otherwise, the Company you work for will be responsible and (as a reminder) sh*t rolls downhill. Trip is correct (as per "rights"), and so is jaclaz (as per the "problem"). I guess it's all on you...

(heh...) Maybe the OP isn't using the 64-bit WinRar/7-Zip and/or doesn't understand that the package needs to target a specific X86/64 independently (no mix/match, choose one). Isn't that why all vendors (including MS) give two different packages? I won't swear to this, but I believe that the Winrar Key (if using Winrar) will work on either x86 -or- x64 version. Best bet is to use 7-Zip (free) and choose which Target they're going after. +1 Yzöwl

For "HTTP", yes. For FTP use "FTP". BTW, there's a difference between "Internet" and "Intranet". The "Dword value" is a pointer to a Zone. See this - http://support.microsoft.com/kb/182569 You have a lot of reading to do about Security Settings in the Registry, my friend. You could have kept IE and just not used it. The only time you have a "security hole" is if you actually use it to access a Website. Otherwise, you could have used it *just* to set those Security Settings. But, you insisted on removal via the FDV Fileset. There's paranoia (red pill) and extreme paranoia (blue pill). You chose the blue pill. Just take a look in the Registry at those places I indicated. BTW/FYI, SpyBot inserts a whole pile of "Restricted Sites" in there and also puts them into the "HOSTS" file. HTH, and good luck!

FYI - your terminology is incorrect. WSUS Offline doesn't "creat an account". It downloads all Fixes directly from MS and creates an Install, which you must have run accordingly. It *may* have deleted the Install Set - I can't offhand remember how it "works". In addition, it *may* have overlayed some XP-Mode files/fixes. See this post (to further tie things together) - http://www.msfn.org/board/topic/171171-introducing-unofficial-windows-xp-sp4/#entry1093808 Some "related" info (you probably have a CPU that supports Hyper-V/ "HT" on an Intel and on an AMD it's called "VT") - http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/01/14/virtual-machine-connection-key-combinations-with-hyper-v.aspx Please note that the terminology gets real confusing. MS says this - (see this and the download links) -https://technet.microsoft.com/en-us/library/ee681616%28v=ws.10%29.aspx In addition, the "standard" XP-Mode works like this during/after installation (scroll down) - https://forums.lenovo.com/t5/Windows-7-Discussion/Setup-and-Security-of-XP-Mode-in-Windows-7-SP1/td-p/1443313 Baiscally, it uses RDP to interact with the Host OS. I don't have my Win7 PC hooked up (with XP-Mode installed) ATM, but I'd say off-hand that the "Auto-Logon" is enabled in the XP and you have no Password assigned? If you go directly to the Dsktop, it means that you have that enabled (somehow). Probably the initial Installation (before Updates) caused CTRL-ALT-DEL (which you could have disabled?) to be the defualt but the Updates changed something (a registry key?) to allow for "Auto-Logon". Guaranteed if you add another User-ID in the XP-Mode VM that you'll have a "Welcome" Screen where you "pick" a User-ID. Further info directly from MS - http://windows.microsoft.com/en-us/windows7/products/features/windows-xp-mode (leads to...) http://windows.microsoft.com/en-us/windows7/install-and-use-windows-xp-mode-in-windows-7 Everything you might want to know about Windows Virtual PC (not to be confused with Virtual PC 2004/2007) - https://technet.microsoft.com/en-us/library/ee681737%28v=ws.10%29.aspx The theory behind XP-Mode is that you can literally run XP-only programs directly from Windows7 (actually "executes" on XP)) while XP-Mode is running. The intent was to make a stop-gap for those that had to use XP Programs that wouldn't run on Windows7. Just for fun, install a Third Part program on XP and see if you can run it from the Windows7. I see you posted the exact same thing in your first post here - http://www.sevenforums.com/virtualization/360065-how-disable-ctrl-alt-del-log-xp-mode-but-weird.html HTH and have fun learning. P.S. - It's possible to extract the original VHD from the package if you want to start from scratch. That's how I discovered the "stunts" MS pulled (re - Integrated stuff).

Not so sure you can do that. My investigation reveals MS integrated some HotFixes, not to mention a couple of VM-oriented files. I wouldn't use the Unofficial SP4 except against a clean SP3-only Install. Sorry... (and a big FYI...) Addendum - I could be wrong - maybe the SP4 "checks" for any pre-existing HotFixes? I haven't used/tried it yet.