For the last few days I have tried, for many times, installing both evaluation and torrent images mentioned by sebus at the first post. All the installations (with keys ending PM4CB) were successful in VM workstation 9. However on every occasion, the first boot logon screen rejected my username/password. Can someone give some tips to resolved this? Is there any way to install Pos 2009 without a password? andgio
Very welcome. I had the same problem when trying to login the first time a well, I tried everything I typed during setup then administrator.
POSReady 2009: OEM does NOT require SLP 1.0 (behaves almost like VL) - most likely each manufacturer had they own key (would be nice to pick one from ie HP POSReady 2009 till VL & retail = I doubt they even exist, as it was only OEM product for making POS units
How serious is this "virus" thing really? I am getting a little concern when I can't RVM Integrator or nlite to recognise the "I386" directory at all
all it was if you read that carefully is, the system MS made the eval with, had malware originally on the system. However all that are left are traces in reg. The above was an Advisory to advise of potential problems if someone were to act on the reg entries by adding "the ACLs on the directory "%windir%\temp" in systems installed from this image/CD allow unprivileged users to create a subdirectory "sso" in "%windir%\temp" and then the "ssoexec.dll", allowing them to have their code run under every (other) user account used to log on afterwards, resulting in a privilege escalation". Personally I would repair that info if this were to be used as a production setup. However I think I would go to PosReady 7 before using this.
hi EFA11, can you please describe how you might "repair that info"? I may be using this a lot after XP support ends. thanks
remove the registry entries Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\SSOExec] "Asynchronous"=dword:00000001 "Impersonate"=dword:00000001 "Logoff"="SSOReset" "Unlock"="SSOExec" "Lock"="SSOReset" "DLLName"="%windir%\\temp\\sso\\ssoexec.dll"
Yes, it is. The iso inside the iso is same hash as original MS one And the key is interesting (none that I seen before!) Will need to check it to see if it is also Retail Sadly there is no other sure way to know. chkpid shows Code: "Key","Grade","PID","Flags" "*****-*****-*****-*****-XPKYG","{;Embedded-SP3-3FF1006B;}","(XXXXX-620-0656981-06175)","[;]" which is a good sign, as *-620-* is also given using the only know retail key (trials have 623 or 622) sebus edit Tested this key & it is definitely OEM (fully working)
