Portable Workspace Creator is not new....It was in build 7850....Write "pwcreator" and you will see it but interesting are other new features =)
Its to see all detailed system info. formaly known as EVEREST Ultimate Edition. A company has taken over the product and renamed it to AIDA64 Extreme Edition
I somewhat agree with you, but OEM keys can be taken from any PC bought and are for hundreds to thousands to millions of PCs, retail keys are bought and are just for the user (up to 3 activations i think). So unless this key is a OEM key, then I agree with the MDL staff by not allowing the key to be shown. Now, lets get back on topic and continue to talk about Windows 8
unless this key was made by the company and sent to OEM makers (like HP or DELL) to be installed on PCs to be sold, then it is not OEM. I dont care if it can work on Windows, MAC, linux or any OS and I dont care if it lasts till the year 2000000, unless it is a real OEM, dont post. If you dont want to abide by the rules the owners of this forums say, then leave or dont post anything.
Retail keys can be used for endless times on different machines as long as it is used on one single machine at one time. OEM keys can be used for endless time as long as it is on the same machine (i.e. WGA returns 7 yes's among 10), but I heard many times that if you make a voice activation and tell MS that you changed the MOBO, they usually give you a code, no0 further questions asked. OEM keys for pre-installed OS is something else.
Hey, anyone else notice you can drag things into the address bar, like if i had music and i wanted to move it back into a folder i can do this... i51.tinypic.com/2rm5fm9.png
Just noticed that the new pdf reader contains a non standard full screen print dialog, accessible by ctrl p: (the tablet version of IE uses the traditional print dialog) h**p://cid-7a804666fc63cba9.photos.live.com/play.aspx/pics/PDF/Untitled.png?ref=2
The key listed was not for Windows 8, the key displayed in that picture was a registration key for AIDA64
I think the scooby patches might work without problems, but only if everything is inverted. I don't know anymore why slc.dll needs to be patched, but it began with 1 thing. What was done is: 1 or some files ask genuine status from slc.dll, so slc.dll was cracked to report always genuine. There were new bugs and crashes, the fix: rename the original slc to slx.dll and place it in system32. ALL files that needed slc.dll and are instable now are patched to ask for slx instead of slc. The inverted way, and maybe better is: Leave slc.dll INTACT. Rename the cracked vista or 7984 slc.dll to slx.dll. Patch only that single file that caused the trouble in the first place to ask for the hacked slx.dll With this method only 1 file needs to be patched and 1 additional slx needs to be placed, which is better than patching a lot of files.
It wasn't, in win 7 it doesn't allow you to move/copy items using the address bars segment thing (there's a word for the bar i can't remember)