submix8c

Huh??? "meaningless unicode"??? Do you have English with MUI installed? Have you "swapped" a Non-English file into an English Install. Sorry, but that makes no sense! You'll have to provide more info than "I blew up. Now I made it "STOP" to see the message." Exactly WHAT do you have installed and WHAT have you fiddled with (swapped or whatever)? BTW - read this through. Claims (in the end) it was a hardware error. https://www.windowsbbs.com/threads/blue-screen-of-death-stop-c000021a.49053/ Hmmm - you applied the patch you indicate here?

Naturally, because they were to busy creating the new monstrosity to care about anything else. Look at all the XP Post-SP3 fixes. Also note the "End Of Support" method, which precludes "bumping" Win7 into another cycle.

Turn off Auto-Restart On Failure and tell us what you see.

Well, that confused me... If Win7, no SP, you'll need SP1. Now comes the Convenience Rollup. No go to Windows Update and see what gets tossed at you Post-Rollup and get those. SOP, right? (Nothing else matters?)

"Doesn't give me an option in my router's properties" doesn't make sense. The Router is an independent piece of hardware/software. I searched for that Wireless model and found this right away. You really shouldn't depend on XP to give the proper Driver. I have a D-Link USB and it will *not* work without the correct driver. Go here, read, download, install, and see if it "fits". http://h30434.www3.hp.com/t5/Notebook-Wireless-and-Networking/Broadcom-4313-drivers-for-Windows-XP/td-p/2942675

Assembly (D)OBOL and Fortran are the basis of - 1- Speed (ASM) 2- Ease of Code Construction (Human Speech friendly( 3- Scientifically Accurate 2 and 3 "translate" to 1 above. AFMC used mainly COBOL-II, with Assembly for tight calculation (besides direct Memory access for in-RAM tables) and (some) I/O subroutines and FORTRAN-IV for intricate calculations (easier to program than Assembly). So... makes sense and *will* run on the old hardware that's much like the Eveready Bunny. IOW, no surprises here.

@tomasz86 - "Progressive!" why else?

(since "edit" isn't working...) DOH! THIS is the topic... (sorry ) However, I do hope the Drivers link will help. It seems that this Topic is for 5.1 and you require 4.1. Hopefully, someone familiar with the values can help. I'm unable to assist since I don't use Windows 10 (and this is in "Unattended Windows 2000/XP/2003). I will assume that the same Registry setting would be used in any Windows version (I could be wrong).

What page? We have a page (topic) to set the Registry to allow for it? Can you provide a link to it so we know where you got the "registry setting"? Also, please don't USE ALL CAPS IN YOUR POSTS. It makes it sound like you're YELLING. All I can found is this (drivers that supposedly work) - http://windowspro.eu/installing-old-sound-card-on-latest-windows-versions/ HTH (that's short for Hope This Helps)

I don't suppose the OP has looked at this? Or this?

+1. And also curious as dencorso.

Two mistakes right there. It's the sugar that coagulates into the fudge. The chocolate is for the flavor. White chocolate is different than brown chocolate and requires a different amount in the mixture (or more/less sugar). Now, STIR, STIR, STIR!!! Let sit until cool enough to refrigerate (or eat right away). Additionally, find a recipe that involves the ingredients you wish to use, otherwise you're experimenting and may/may not get the result you wish. Lastly, listen to Mom. Moms are *always* right.

Code is (generally) inserted at the end of an existing module and "somewhere" in it a "call" is made to the new code. The new code will save registers (among other things), calculate a Base Address, execute the code, restore registers (etc), then "return" the the immediate next instruction after the "call". Many smart programmers leave "NOP" somewhere in the Data areas for just that, i.e. (as example) at the point where "new" code must be executed, the "old" code is "patched" to "save" the original code in Data, "call" the "inserted new" code (which returns), and the "old code" is then "restored" and normal execution continues. The above is an EXTREMELY loose example, of which many method are used. Bear in mind that (e.g.) C++ is HLL (High Level Language) that is run through an "interpreter" to translate into Machine Language (Assembly translates directly to it) Object Modules which in turn are Linked into Executables. "Fix base" is not as simple as "using a tool". Executables are made of Objects, of which each recalculate it's own Base Address (depending on the design of the Executable). Without a correct Base Address (*and* Data Address) you' "blow up" or (maybe even) completely corrupt the OS (see "Test Bed"). Find these and study them to get an understanding Of Addressibility, Entry, Exit, etc. IntelCodeTable.pdf IntelPIIvolume1-Basic Architecture.pdf IntelPIIvolume2-Instruction Set Manual.pdf IntelPIIvolume3-System Programming.pdf Programming in "real" languages (not "scripts" like Java or REXX, for example) is not for the faint of heart. Nor is "patching" preexisting modules. You might also want to learn a little C-language to understand the relationship to Assembly. Oh, and Code Signing (that MS uses for, e.g., SFC). @jaclaz - "Code Cave" - I guess I must be *really* old to have not used/heard that term for my (extremely) "loose" (and somewhat inaccurate) example. Excellent article, BTW. I highly recommend Dibya study it as well (i.e. "Endorsed").

@Dibya - o_O You do realize Assembly code is... Assembly code and must be assembled either into a full Assembly Code module or patch the Original (hex) to "call" a separate module? You *must* have full code to "insert" code or else Hex-Patch. There is no other way. Side note - Been there, done that, told Computer Associates where their code was wrong on a Mainframe Database module. Supplied both the Hex Patch and the Patched Full Code. No other way, Bro. I had a REALLY neat Disassembler that I LITERALLY improved the code that saved the loss of Source for a VERY important CICS sub-module (after using it on the Load Module), so, no, ain't gonna happen that way. Sorry.

FYI - This link lead to Forum Index for me. Looks like some "fixes" to the Board are goobering (?) (Side note - No Edits!) http://www.msfn.org/board/index.php?act=findpost&pid=1119989

What's that? This isn't XP, ya know. Forget the Convenience Pack and integrate all current Post-SP1 Fixes/Patches. That "pack" is still in review here on MSFN (AFAICT) and elsewhere. http://forums.overclockers.com.au/showthread.php?p=17170435 These links may or may not help (wonko=jaclaz, BTW). http://reboot.pro/topic/21121-convenience-rollup-update-for-windows-7-sp1/ Beyond that... What "alternatives" are you in search of? There's RT7Lite, NTLite, and the MS way (using their tools). Not really sure I understand...

I no longer support my children, but I haven't abandoned them. They're still OEM trademarked. :w00t:

The Autorun file entry is for detecting x86/x64 and has nothing to do with Symantec/Norton.

Hi, Bottle! Glad to see you! Addendum - it appears that XP added integrated in SP2 (or was it SP3?). Google this: "wpa2 support" "windows xp" As you can see, even XP didn't have "native support" until then without an added Driver/Client. Getting WPA2 in anything less is, well, "problematic" at best.

Has this been posted yet? https://ftp.mozilla.org/pub/firefox/releases/ I have yet to test v38, v43, and v46 (the ones I chose for tests for Video Enable). It seems that v38 is when the Video madness began. Ignore using Downloader (like I do by disabling AutoUpdate) and go for direct. Or am I somehow missing the boat (again)?

???? "This article describes a convenience rollup for Windows 7 Service Pack 1 (SP1)-based and Windows Server 2008 R2 SP1-based computers. This rollup package includes almost all the updates that were released after the release of SP1 for Windows 7 and Windows Server 2008 R2, through April 2016. This convenience rollup is intended to make it easy to integrate fixes that were released after SP1 for Windows 7 and Windows Server 2008 R2. We recommend that you include this rollup package in the image creation process to make it easier to quickly set up a computer." So, is this some kind of "rollup" like ye olde Win2K/XP-MCE but *may* include stuff you don't want? It kind of imples if you install this at a clean install/integrate you'll be up-to-date? (but with slipped-in telemetry and GWX, the dirty barstoods) Also "To get the package for this update, go to the Microsoft Update Catalog website" and "Prerequisites"... Hrrmmm... Your post in here says A-OK (mostly)... http://www.msfn.org/board/topic/175618-convenience-rollup-update-for-win-7-sp1/

MSVCP71.DLL is part of VS2003 (Visual Studio 7.1) and/or dotNet Framework v1.1. That version of dotNet would install on 98/ME (and up) but not 95 and lower (obviously). FWIW, I probably have the "redistributable" (tucked somewhere) but can I redistribute without software? http://stackoverflow.com/questions/1596167/where-to-download-microsoft-visual-c-2003-redistributable Hrm... Yes, I *may* have it but the file you would want "VS7.1sp1-KB9322981102-X86-Enu.exe" is not available anymore (AFAICT) even on Web Archive. And I would be mighty careful about discussing K*g*n*r*a*t*s if I were you. Edit: See this also. https://blogs.msdn.microsoft.com/asklar/2011/07/14/how-to-install-the-visual-c-7-1-runtime-on-windows-7/

It's the driver that inherently interfaces with the hardware, not the client. Without a functioning nVidia Driver the nView client is useless (as an example) and does absolutely nothing.

Washington DC-esque comment right there (the general populace is inherently "Oh, OK, whatevs. It's for my own good, so..."). I can't wait for Win-X to start installing while a diplomatic negotiation agreement is being worked out and the details are on the PC in question.