bphlpt

Both those names sound like a variation of MS to me, at least in spirit. Cheers and Regards

From what I've read, the same "broken" update issue applies to all versions of XP including POSReady. Using the r256 version of MUWeb.dll solves it for now, AFAIK. Cheers and Regards

Since you say you have uninstalled the Kodak printer, maybe you have some garbage left over in the registry. I'm still on Win7, so I don't know if this will work, but have you tried a registry cleaner such as CCleaner to see if maybe that would help? Cheers and Regards

Relying on only the existence of any particular folder to determine the bitness of the OS has its limitations due to the possibility of running into some "not very well written" setup package, as you have found, even though it does simplify the code. Switching to "C:\Windows\SysWOW64" doesn't really help either, (even though I used to believe that, too), since there are real chances to find some x32/x64 setup package that want to drop some dll or exe into the SysWOW64 folder, and will create it if necessary, no matter what OS you are running. That is why MS suggests not relying on any file location at all but rather the values of system variables. A reliable result for OS bitness can be obtained by checking PROCESSOR_ARCHITECTURE and PROCESSOR_ARCHITEW6432 without checking folders or files, provided that nobody changed either value in the registry at "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment". SET "ARCH=x64"IF /I "%PROCESSOR_ARCHITECTURE%"=="x86" ( IF NOT DEFINED PROCESSOR_ARCHITEW6432 SET "ARCH=x86")But there have been problems reported even with this method. There are situations in Win7 install where the eventual install will be x64 but the environment variables, and the file system at that point, are in a 32bit state so %PROCESSOR_ARCHITECTURE% will return x86 on AMD64 hardware, (example bug over at DriverPacks.net: http://forum.driverpacks.net/viewtopic.php?pid=48416#p48416), and SysWOW64 might not exist yet, though most of the time just checking for SysWOW64 will work here. There are other situations that even though you have a 64bit processor and a 64bit OS installed you do NOT want to run or install the 64bit version of an app or driver, you want to run or install the 32bit version, but ONLY when you are already running another 32bit process such as a 32bit CMD session or you are running a 32bit app, such as a 32bit browser. That's why you have to have 32bit versions of all the various runtimes even when you install a 64bit OS. Once you are in 32bit mode you cannot then call a 64bit app or runtime, just as you cannot install a 64bit version of Windows on a 32bit processor based machine. In any case, if for whatever reason you need to find out which arch mode you are in, you have to check, that's the only way you will know. You cannot just rely on which processor, OS, or file system is in place. You are ONLY able to tell that you are in one of these situations by ALSO checking whether %PROCESSOR_ARCHITEW6432% has been defined, but that check is ONLY valid if you have already determined that the environment variables or file system indicate a 32bit environment. For that situation, if %PROCESSOR_ARCHITEW6432% has been defined, even though %PROCESSOR_ARCHITECTURE%=x86 or SysWOW64 does NOT exist which both normally indicates a 32bit arch, it is actually a 64bit arch. It is only a 32bit arch if %PROCESSOR_ARCHITEW6432% has NOT been defined. I'm sorry if my attempt at explanation doesn't help clear things up, but it can be very complicated. It is also a more robust test to check for the existence of SysWOW64\cmd.exe and not just SysWOW64, since the chance that someone/some setup pack will try to overwrite the existing "%SystemRoot%\SysWOW64\cmd.exe" is less likely. So a combination method with multiple checks has been developed which checks for the existence of a particular file, not just a folder, along with checking an environment variable: :PROCESSOR:: Detect OS bit-ness on running system. Assumes 32-bit if 64-bit components do not exist.SET "ARCH=x64"IF NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" ( IF NOT DEFINED PROCESSOR_ARCHITEW6432 SET "ARCH=x86")There are several ways that you could use the results of this test to selectively execute code based on the results of the OS bit-ness. SET "ARCH=x64" IF NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" ( IF NOT DEFINED PROCESSOR_ARCHITEW6432 SET "ARCH=x86" )IF "%ARCH%"=="x64" THEN ( (x64 EXE 1) (x64 EXE 2) (x64 EXE 3) ) ELSE ( (x86 EXE 1) (x86 EXE 2) (x86 EXE 3) )Is one way that would work. You could also use GOTO statements which don't use SET statements or you could utilize the value of %ARCH% as part of the path or file name to determine which commands to execute. You could set %ARCH% to x86/x64 or 32/64 or other values depending on your needs. All work perfectly well in batch/command script and are purely programmer's preference. For the common situations such as deciding whether to install a 32bit or 64bit app, checking for the existence of SysWOW64 is usually sufficient. And if you use the built-in automatic methods in Win7 x64, this is often handled for you without you having to do anything special at all. But the check for "arch" or "bit-ness" can be used in other stuations besides just app or driver installs. And if, for whatever reason, you are trying to do things manually, then those automatic things don't always work, especially if you specifically choose to not use them. The final method above is simply an alternative version of what was suggested by Microsoft. It has been proven to work in circumstances in which just testing for SysWOW64 has failed. So even though just checking for SysWOW64 has also always worked for me in the past, if Microsoft and others all agree that the test can be made more reliable and robust with one simple extra check, then to be prepared for any possibility that's what I'm going to do. You can read a more thorough discussion about this subject here. Cheers and Regards

LOL They have a database for THAT??? Of course they do. I'm sure it's meant to prevent folks from copying the design of an existing product and marketing it as their own. There are many. many patents on all the different aspects of the various products involved in any industry, and cutthroat competition exists in every business, as does piracy. Money is money after all. Thanks for the laugh, jaclaz. Cheers and Regards

Thanks Noel! It was cloudy here and we couldn't see it directly. Cheers and Regards

The easiest way, and most often used, is to simply abandon the account. That way any posts you made that are part of a thread will remain and not disrupt the flow of the thread, and you can come back at a later time if you decide you want to. Just be sure to disable any notifications that you might have in place, and you should never hear from any of us ever again, unless you choose to initiate contact. The board and staff will not contact you and you won't get any spam as a result of the remains of your account being left here. Cheers and Regards

It worked for me just now. Cheers and Regards

I believe that the AMD Athlon II X3 435 includes instructions for SSE, SSE2, SSE3, and SSE4A. At least according to this. Cheers and Regards

If he gave any hints or screenshots at all he would just be bothered that much more by folks asking for more. When will it be released? Will it do this or that? Can I help test it? etc, etc. This way he can work in peace. It's just better to take the approach of -- If it comes, it comes. In the meantime, use one of the other tools available such as Win Toolkit. Cheers and Regards

I've never used it, but doesn't Rainmeter provide that kind of capability? Have you tried that? EDIT: Never mind. We were talking about different sidebars. Cheers and Regards

Welcome to MSFN! Cheers and Regards

+1 Cheers and Regards

Welcome to MSFN! http://www.msfn.org/board/topic/171886-help-needed-with-rt7lite/?p=1078886 But please do a little bit of searching for already given answers to questions before posting. Cheers and Regards

IIRC, Flasche is running a POSReady 2009 system, but I could be wrong. Cheers and Regards

+1 LOL Cheers and Regards

You mean like jaclaz? Yes bphlpt is an acronym, an endearment my wife and I use so I plan to keep it. It's "G" rated, but no I'm not saying what it is. Likewise, and BP is fine for me. Cheers and Regards

Check the guide for description on how to set DisableGlassOnBattery correctly to retain Glass while on battery. Cheers and Regards

[ OT ] Anyone know what happened to Charlotte? [ /OT ] Cheers and Regards

You're quite welcome. Now if only everyone can learn to spell my name. LOL Cheers and Regards

Welcome! Cheers and Regards

http://www.glass8.eu/ Cheers and Regards

Welcome to MSFN! Cheers and Regards

Welcome back, Larry! Cheers and Regards my friend

But I believe that some versions of DISM can be installed on Vista, and I think even on XP. Cheers and Regards