cluberti

Technically, according to the wording of the EULA, you're supposed to provide all media that came with the OEM computer including any CD/DVDs and documentation. The media you used to install Windows wasn't technically following the EULA either, and a new Windows license should have been purchased when you purchased the machine (the COA isn't the only part of the license - the media is the 2nd half, whether that be a recovery disc, the original XP install disc, or a hard-disk based image to do the recovery from). You can read a bit about that bit here (it discusses refurbished PCs, but the same things hold true for OEM software/hardware transfer at sale): http://oem.microsoft.com/public/oem/refurb...ensingguide.pdf Unless the sale of the machine (to you from the original owner) contained both the COA *and* the restore/recovery medium, it wasn't a legitimate transfer. I would (if you can) at least try to get the OEM to ship you (probably at a small cost) the correct recovery or restore media for that machine before selling it, if you can. Given that this happens regularly enough that we've all seen it, I don't think anyone is going to "mind" if you provide the new owner a burned copy of a non-specific OEM disc, but it's not technically a legitimate install or recovery disc.

Description: VBscript to gather some basic computer information, including locale, install date, current time, etc. Programming Language: VBScript Usage: Use cscript to launch, otherwise you'll get lots of pop-ups from wscript. Output: ------------------------------------------ System Details ------------------------------------------ Computer Name: COMPUTER Operating System Information: ============================= Operating System: Microsoft Windows 7 Ultimate 64-bit Version: 6.1.7600 Ultimate Edition Build Type: Multiprocessor Free Locale: English (United States) Serial Number: XXXXX-XXX-XXXXXXX-XXXXX Current Time Zone: Eastern Standard Time Offset from UTC: -5 hours DST In Effect: False Windows PID Key: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX Office 2010 PID Key: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX Install Date: 7/23/2009 4:24:52 PM Last Boot Time: 12/21/2009 4:25:21 PM Local Date/Time: 12/28/2009 6:54:42 PM System Status: OK Hardware Information: ===================== CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (x64) Physical Memory: 7.92 GB Video Card: Radeon X1550 Series (Microsoft Corporation - WDDM) Adapter DAC: Internal DAC(400MHz) PNP Device ID: PCI\VEN_1002&DEV_7143&SUBSYS_204E17AF&REV_00\4&2FFCA7E0&0&00E1 Video RAM: 256 MB Driver Version: 8.56.1.15 Driver Date: 4/24/2009 Video Card: Radeon X1550 Series Secondary (Microsoft Corporation - WDDM) PNP Device ID: PCI\VEN_1002&DEV_7163&SUBSYS_204F17AF&REV_00\4&2FFCA7E0&0&01E1 Driver Version: 8.56.1.15 Driver Date: 4/24/2009 Video Card: ATI Radeon HD 2600 Pro (Microsoft Corporation WDDM 1.1) Adapter DAC: Internal DAC(400MHz) PNP Device ID: PCI\VEN_1002&DEV_9589&SUBSYS_E410174B&REV_00\4&324FA3B&0&0008 Video RAM: 256 MB Driver Version: 8.56.1.15 Driver Date: 4/24/2009 Sound Card: High Definition Audio Device Manufacturer: Microsoft PNP Device ID: HDAUDIO\FUNC_01&VEN_11D4&DEV_1884&SUBSYS_103C2819&REV_1001\4&2260D901&0&0001 Sound Card: USB Audio Device Manufacturer: (Generic USB Audio) PNP Device ID: USB\VID_045E&PID_070F&MI_00\6&216596F4&0&0000 Sound Card: High Definition Audio Device Manufacturer: Microsoft PNP Device ID: HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1000\5&36D18A18&0&0001 Volume: C: Compressed: False File System: NTFS Volume Size: 465.67 GB Free Space: 368.08 GB Network Adapter: Intel(R) 82566DM-2 Gigabit Network Connection MAC Address: 00:0F:FE:83:0B:63 DHCP Enabled: True IP Address: 192.168.200.100 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.200.1 Lease Obtained: 12/28/2009 4:13:18 PM Lease Exipres: 12/29/2009 4:13:18 PM DHCP Servers: 192.168.200.10 DNS Server: 192.168.200.15,192.168.200.16, WINS Primary Server: 192.168.200.16 WINS Secondary Server: 192.168.200.15 Enable LMHosts Lookup: True System Information: =================== Computer: HP Compaq dc7800 Convertible Minitower Serial Number: 2UA81017DR BIOS Version: 786F1 v01.04 UUID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX osinfo.vbs.txt

Being able to go home, visit for the holidays, enjoy the snow, then come back to warmer weather afterwards. Driving in the snow *is* fun, though .

It's on MSDN if you change your language, I dunno about technet.

GetLocaleInfo is what you should use if this is going to be run on platforms older than and including Vista/Win7, but if the app is Vista and newer only, you can use GetSystemDefaultLocaleName instead.

I think the argument is that there really aren't any differences between the EU's N versions and the Korean "KN" versions in Vista and 7, unless you're specifically looking for IM support on XP. Both versions lack Media Player support, so if you've got an "N" version and the language is Korean, for example, the locale output would be "0412" and the OperatingSystemSKU would return an N version (in almost all scenarios). From that, you can fairly easily assume that this is a Korean N version, given (for example) a SystemSKU of 16 (Business N) and a Locale of Korean (0412). This would be harder with Ultimate versions, however, as (at least on Vista) they always seem to return "Ultimate" for the Caption without N distinction. I haven't tried it on Windows 7 yet, as I'm still downloading the K and KN versions, but I would be interested to see what the Caption value is and if N has been added for Ultimate SKUs or not. GetProductInfo returns all of the possible regular, E, and N SKUs, and again pairing it with a locale check would give you a good idea if it was a KN version (versus just an EU "N" version), but there's not really a difference short of the KN version lacking a pre-installed IM client on XP, and with Vista and Win7 there is no preinstalled IM client in the base OS image anyway.

Given my blazing fast download speeds today < sarcasm / >, it may take awhile. However, so far I've only found reference to determining between non-N and N versions (as MagicAndre was questioning), with no information in any of my testing of GetVersionInfo, IsOS, or even Win32_OperatingSystem that would indicate there's even a check or return for a K or KN version. Given that these versions were released after the XP codebase was put down, I can understand it in XP, but not Vista or Win7. However, it looks like (according to KB 922461) that checking HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures for the value data of 0 in the "Windows Media Player" DWORD is the suggested way of determining a K or KN SKU (it either doesn't exist or is set to 1 on other SKUs). Technically the K and KN versions should only be available in Korea and in Korean-language versions of the OS, but I would admit it would be nicer to have some way of checking, considering they've added checking for N SKUs).

Not entirely sure - I'll build up an N and KN version and see what the differences are in the usual places.

It would probably be better to try the ISO itself in a virtual machine - it might not be the media at all.

I had flown in from Chicago that evening, and I was supposed to leave that Thursday (27th). I remember not being able to fly back until the 29th, and I barely made it onto a plane that day without getting bumped as well. Good times, and one of the reasons why I don't live there anymore .

Reminds me of being in Buffalo in 2001 - 35 inches of snow in a 24 hour period, a little over 80 inches of snow over 3 days right after Christmas that year (approximately 2.1 meters). What a fun mess it was - I don't have any pics of my own, but I'm sure a quick google will find some if you like snow pictures. The AP had this one, for reference (sorry about the crap quality, thank the AP for posting a heavily compressed jpg):

Is it a hologram install DVD, or is the install from a burned ISO or thumb/usb drive? I would think the hardware would be fine, although testing a downloaded source in a VM first is usually a good idea.

Indeed.

The application most known to write THAT value to THAT key is Foxit PDF reader (the full version, of course, for the trial period). Monkey with it at your own risk, but deleting it and reinstalling to verify would be considered valid troubleshooting in my book. However, if you like the software, it's always best to buy it and use it legally, of course.

Why not extract the components and use device manager to manually point the video device at the extracted contents? I never trust the full catalyst installer anyway.

Yes, specifically.

I didn't see anything obvious in either dump (in fact, the browser was completely idle). However, I could tell that approximately 1 hour had passed since the browser last attempted something, and *something* had spawned a worker thread in both the frame and tab processes (but possibly died out). I took the stack base and stack limit for that thread, and found this in the frame process: 0:010> dds 05eb2000 05ec0000 ... 05ebf64c 75720000 kernel32!_imp__DebugBreak <PERF> (kernel32+0x0) ... 05ebf748 77a73af4 ntdll!RtlpAllocateHeap+0xab2 05ebf74c 77a73b23 ntdll!RtlpAllocateHeap+0xe73 ... 05ebf860 77250000 KERNELBASE!_imp__RtlUnicodeStringToAnsiString <PERF> (KERNELBASE+0x0) ... 05ebf8c4 77a6e20c ntdll!RtlpLowFragHeapAllocFromContext+0xaec ... 05ebf99c 77a72b21 ntdll!RtlAllocateHeap+0x21d ... 05ebf9c0 7721140a ws2_32!DllMain+0x1bf ... 05ebf9e0 74f41233 rsaenh!DllMain+0x103 05ebf9e4 7510140a mswsock!DllMain+0x183 ... 05ebfa18 73aa11d0 xmllite!__DllMainCRTStartup+0xe1 05ebfa1c 73aa0000 xmllite!_imp__UnhandledExceptionFilter <PERF> (xmllite+0x0) ... 05ebfa24 73aa1227 xmllite!__DllMainCRTStartup+0x24e ... 05ebfa50 759caf8c msvcrt!_initptd+0x8c 05ebfa54 759ca501 msvcrt!__CRTDLL_INIT+0x102 ... 05ebfa68 73ac7e4c xmllite!_except_handler4 ... 05ebfa74 73aa1227 xmllite!__DllMainCRTStartup+0x24e 05ebfa78 77a797c0 ntdll!zzz_AsmCodeRange_End 05ebfa7c 73aa0000 xmllite!_imp__UnhandledExceptionFilter <PERF> (xmllite+0x0) ...05ebfafc 77a79fbc ntdll!LdrpInitializeThread+0x131 05ebfb00 77a79f6a ntdll!LdrpInitializeThread+0x179 ... 05ebfb10 73aa1142 xmllite!_DllMainCRTStartup 05ebfb14 7efde000 05ebfb18 77b40214 ntdll!PebLdr+0x14 ... I found this in the tab process, confirming an RPC call likely to spawn the xmllite thread in the frame proc: 0:008> dds 03d52000 03d60000 ... 03d5f108 757336c6 kernel32!ConDllInitialize+0xd4 ... 03d5f73c 75733647 kernel32!_BaseDllInitialize+0x92 ... 03d5f750 7573365c kernel32!_BaseDllInitialize+0x2cf ... 03d5f764 75720000 kernel32!_imp__DebugBreak <PERF> (kernel32+0x0) ... 03d5f7e8 761a02e0 user32!gcsAccelCache 03d5f7ec 7613c6bd user32!NtUserInitializeClientPfnArrays+0x15 03d5f7f0 7613c665 user32!ClientThreadSetup+0xf2 03d5f7f4 77a8f818 ntdll!NtDllUserStubs 03d5f7f8 77a8f8d0 ntdll!NtDllUserStubs+0xb8 03d5f7fc 77a8f988 ntdll!NtDllUserStubs+0x170 03d5f800 76120000 user32!_imp__GetTokenInformation <PERF> (user32+0x0) ... 03d5f8bc 77a6e20c ntdll!RtlpLowFragHeapAllocFromContext+0xaec ... 03d5f940 77a73af4 ntdll!RtlpAllocateHeap+0xab2 ... 03d5f994 724a9907 IEShims!IEShimLib::CStringParseCommandLine+0x2f ... 03d5fa44 724bd6cf IEShims!NS_RedirectRegistry::RedirectorRegistry::ThreadAttach+0x31 ... 03d5fa54 77a5f88a ntdll!ZwCallbackReturn+0x12 03d5fa58 7613c5c6 user32!__ClientThreadSetup+0x1e ... 03d5fb30 75bf27ef ole32!RPCSStoOLE32SecurityCallback+0x38 ... 03d5fb48 7606618c rpcrt4!RPC_INTERFACE::DispatchToStubWorker+0x141 ... 03d5fd9c 77a62056 ntdll!ZwWow64GetCurrentProcessorNumberEx+0x12 03d5fda0 77a728e0 ntdll!RtlGetCurrentProcessorNumberEx+0xf ... 03d5fdb0 77a728fe ntdll!TppGetWorkerFactoryHandle+0x10 ... 03d5fdc0 77a61ee6 ntdll!ZwWaitForWorkViaWorkerFactory+0x12 03d5fdc4 77aa21aa ntdll!TppWorkerThread+0x216 ... 03d5fde0 77b40180 ntdll!TppWorkerpList ... 03d5ff70 77a79d45 ntdll!_RtlUserThreadStart+0x1b 03d5ff74 77aa2c91 ntdll!TppWorkerThread ... 03d5ff8c 77aa2c91 ntdll!TppWorkerThread ... 03d60000 ???????? It looks as if xmllite was loaded for something, IE went down into the network (winsock) stack, and there was some exception that caused a debug break. However, since no debugger was attached, you probably have a "hung" process waiting for commands from a non-existant debugger. Also, I noted that the stack base in the tab process was invalid, which could mean something bad happened while the thread was being created, but in any case a static dump of this probably isn't sufficient to show the issue. It'll probably take someone at the console when the problem first occurs to dump it then, if that's even possible. It could be an xmllite issue, but I don't think that's likely. Is it always the same website that's up when the browser hangs?

No. I don't know exactly how safari works, but it's probably similar to Firefox - with IE, Google Chrome, and Firefox, the browser simply calls down into the winsock APIs and gets a socket in return that it can use to send/receive data for whatever it wants to do (it can request more, free up sockets, etc). This is all handled differently within the browsers themselves, but ultimately they go into winsock on Windows. If you wanted to force a browser's sockets to a specific network connection, at the least you'd have to write a winsock app that you could use to intercept all requests for sockets, and you could then force those packets to specific connection object based on the requestor via bind(), but that would take a good amount of time and code, and it would introduce some latency and possible performance issues for all network apps.

disk.sys loads, and then any filter drivers (or disk drivers) that rely on disk.sys load. Sounds like, if this is just a clean install, the driver for your disk subsystem isn't loading properly. That board uses the ICH10R, which works fine out of the box in Win7 (I have many systems using that without issue), so I'm not sure what's happening. Is it the first restart after Windows finishes installing, or is it still installing? Also, is this a 32 or 64bit install?

According to reports (and Google), the Catalyist 8.12 (or 8.1) work the best with the x1300 and Windows 7.

Look at the output of the System Properties window carefully - if it doesn't say "System Type: 64-bit", it's a 32bit (x86) installation of Windows 7.

Wikipedia has a good article about this very subject that I suggest you have a look at. What the poster in the article you linked was describing was a System Virtual Machine, which provides native execution of emulated hardware (meaning the virtual machine in the VM software running Windows 98 only sees very generic hardware, regardless of what's in the parent machine running the system virtual machine software - in this case, Vista running Microsoft Virtual PC).

All this captured was CPU data - there's no memory, process, or any other counters. I've never seen perfwiz do that, ever..... Can you try again? Assuming you follow the instructions to the letter (and perfwiz doesn't screw up), you should get A LOT more data than this.

That is actually exactly why it's happening. Take ownership of everything on the drive and push more appropriate permissions down afterwards, and things should clear up.

Windows 98 is a consumer product (NT was the business product line). Win98 and WinME actually had their support extended from the usual 5 and done to 2004 and 2006, respectively, but after that everything's done. You cannot get Win9x on a Premier support agreement (again, it's not considered business software), which you would have to do to get an Extended Support and Extended Hotfix Support agreement written up for it (and you'd have to pay back to 2004 or 2006 and every subsequent year for both agreements to get it current, that's also required). It's basically made fiscally unfeasible to try and keep those products alive - one, it means Microsoft doesn't have to pay someone (or some group) to keep updating the code for products that most people don't use anymore, and two it means that those who do want to pay for it make sure Microsoft is making some money off of it to offset the costs of building, testing, and maintaining said code (and probably at a small profit too, after a few years past end of support).