Forum Replies Created
EDIT: Since I will start making an installer soon, please anyone mention if you’ve had any bugs or problems with ReadyBoost after installing via this guide! (It will also support 64-bit)
Yeah this is the only thread as far as I know, I remember working on this ages ago.
Yes, the installer. I had started one, but I found it difficult to program because of those manual steps and stuff. But I remember I made this a while ago, it’s amazing what you can learn in just a few months 😉
I use Windows 7 right now i don’t have much interest in Server > Workstation conversion anymore I because I think 2008 R2 is crap… and I have lots of serious projects I’m working on. But hey I will make an installer for it soon unless someone beats me to it. It will be something to put on my soon-to-come blog =)
this part of the instructions is a little bit confusing:
“Navigate to the…
…key and edit the Multi-String entry “LocalSystemNetworkRestricted” – add “EMDMgmt” to the end of it, on a new line.”
“add EMDMgmt” ?
add as what, a string without value ?
You need to edit the existing entry LocalSystemNetworkRestricted which is not a string entry but a multistring. When you open it it will look like a textbox which can take multiple lines like Notepad. All the existing entries are other serives so don’t make a mistake and delete some of the texrt! Scroll to the end of the value and type EMDMgmt and OK it. Here’s a screenshot –
Note that I did that grab on Windows 7 so the existing services are probably different to 2K8, but hopefully you can see what I mean by the example of adding the service.
This thread is over a year old 🙄
I have SuperFetch sort-of working but would like to cross-check everything with the other guys before I release for testing.
AsciiWolf and GnatGoSplat – could you guys release your work so far (4shared link is dead) so I can make sure all our work is inclusive 🙂
Its such a great feature in windows 7 (and vista), too bad its not easier implemented in server 2008.
Yeah, I managed to get ReadyBoost in 2K8 but that had SuperFetch as an addon module, so it wasn’t as hard. There’s all drivers and junk in Win7/R2 😯
Are there any news on this topic?
Did anyone manage to test and see if superfetch could be added back to 2008 r2, and if it did work?
This topic have been quite silent for a long time.
I am two thirds through comparing all the differences between a Win7 and R2 installation (registry and file differences) and already found some Superfetch/Readyboot information that is missing from previous installers in the thread though I’m unsure if they’re needed yet.
So yeah I guess there is news 😉 I’m still working on getting my ReadyBoost for R2 (you need SuperFetch for ReadyBoost) and will have it all in one package when I nail it.
(1) Hyper-V is a Type-1 Hypervisor whereas VMWare is a Type-2 virtualization suite.
System virtual machines (sometimes called hardware virtual machines) allow the sharing of the underlying physical machine resources between different virtual machines, each running its own operating system. The software layer providing the virtualization is called a virtual machine monitor or hypervisor. A hypervisor can run on bare hardware (Type 1 or native VM) or on top of an operating system (Type 2 or hosted VM).
(2) Hyper-V has it’s drawbacks. As does VMWare.
(3) VMWare is the only consideration for gaming. That and DOSBox for retr0 fans like me 😆
(4) My personal opinion is that Hyper-V is best suited for corporate sandboxing; virtualizing from a mega server for hundreds of clients to work on. It’s very low level, but as far as non-Microsoft and older software goes it is probably less compatible. VMWare however is a ‘hosted’ virtualizer that is further seperate from the core OS compared to Hyper-V, but is very mature and has great support for Intel instruction sets.
With that said, it would make sense that Hyper-V is better performing than VMWare, but everyone agrees VMWare is better for standard consumer-level applications (games, Photoshop, etc). Not to mention the latest VMWare beta (OSX only for now) can run Crysis @ ~10fps average [Shader Model 2.0 and lower is supported] and will apparently have 100% Direct3D9 < SM2.0 on Windows very soon. The way I see it, Hyper-V is good for doing it by the books. To do Microsoft and Technology Collage/class stuff, it’d be helpful there. Maybe also geek factor, it’s pretty hardcore. But let VMWare do everything else 😉 Player is freeware (registerware actually, signup = instant download) and it can create machines now so it can’t hurt to try 🙂
Have you installed the drivers? The Framework might not be enough. Check the Product Page for the laptop (google the model number) and check the Drivers/Downloads section – probably under ‘Support’. Try looking for Vista drivers for Biometric Reader.
Howdy mage7 and welcome. Isn’t DreamSpark great 😀
ZOMG I missed the trolling in Open Topic! You all smell like pine trees!
*Throws cheese at Indrek*
*Kicks a buffalo with “J.F. was ‘ere” painted on it*
*Hisses at R.C.*
Dunno how this all started but the three of you are just as stubborn/proud as the other. And we’re all as equally geeky here, there’s no need to argue about who has the biggest spacebar or flattest mousemat – look at the fudging forum we’re on!
ON TOPIC, yeah… Windows 8….. a.k.a Not-windows-at-all-just-made-to-look-that-way-to-publicize-better Midori Experiment…. 😉
Some people say that 1 means boot optimization only, other people say it means apps optimization only. And there are even people that say that it doesn’t make any difference at all to change it from 3 to 1.:(
That’s only for Vista. That key has no effect on Windows 7, it is ignored and provided for backwards compatibility. 7 will always cache both boot+user binaries as it sees fit. There’s a big MSDN blog article about Windows 7’s Superfetch they mention it there.
Unfortunately, Microsoft has only documented the “EnablePrefetcher” parameter, and only for Windows XP.
The EnablePrefetcher key is only in XP because in Vista the Prefetch Driver was replaced with the Superfetch service. Again, only there for backwards compatibility. But from memory, Vista will actually change this reg value depending on Superfetch service state – so that older pre-Vista software can still test if ‘Prefetching’ is enabled or disabled – when it’s actually checking Superfetch status.
P.S. That first one is a BitAND – 1 is probably “cache boot”, 2 would be “cache user apps” so 2+1 = 3 = do both. 0 is do none.
IMO, all the other stuff that doesn’t work in Server 08 R2 is because of missing depedencies.
Like the DVD Maker, I can’t get it to work (MP2 encoder is missing)
Install Windows Media Encoder for XP (I think) which has all the audio/video encoders that are stripped out of Server installations. Not sure of the name, just do a search for “Windows Media” on download.microsoft.com and download anything that might be a codec 😉
You might need to experiment with XP codecs, because Vista/7 ones don’t exist (they are included with Windows Media Player 8+ Redist. installers as far as I know). I’m not at home right now, if you can’t figure it out let me know and ill take a look on my home storage drive.
EDIT: Oh if you mean the MPEG-2 video encoder, yes that will require hacks I think because only Workstation OS’s have the licencing for DVD Video Authoring capabilities whereas the specific MPEG-2 encoder Windows DVD Maker uses is was only included in certain editions of Windows for legal reasons. Maybe. Dunno.
A little program called InstallRite, while outrageously outdated, still works flawlessly under 2008 R2. In fact I’m using it right now to try and make a portable version of VMWare Player 3.
Basically you can use it to take a ‘snapshot’ of the entire registry (or specific hives), and also optionally snapshot complete harddisks or specific paths – then you do whatever, install anything… change anything… reboot… heck even System Restore… then load the program and do an ‘Analyse’ and it’ll list all the changes made since the last Snapshot.
Well System Restore might bugger it lol… but it stores it’s own database in it’s own file within the program folder, it’s completely independant of the registry as far as I know (it works without installing but you need to manually specify it’s database path if theres no reg details for the program).
99.9% of Windows system settings are in the registry, the rest are stored as files under C:ProgramData. If you run InstallRite as administrator, it catches everything you could ever need.
The only concern I have is that Hotfix installers tend to rely on runtime .manifest generation, because it fingerprints the install based on the current computers PID/SID or something like that. In which case, that’d be the real obstacle to overcome.
I have no idea how to make it trusted. It should be possible to make developer test certs and make them trusted with tools from the Windows 7 SDK, but it’s a 4GB download which will take me awhile to get.
Test Mode booting would then be required for x64 machines, or the ReadyDriver Plus BCD trick for unsigned driver booting. The only other way is to become a Premium MSDN member (as a developer partner) which costs a lot of money.
I’m pretty convinced you’d have better luck making a custom installer that extracts the required files from the original source MSU, and then adds registry entries/drivers manually – rather than trying to hack the security on Windows Hotfix catalogs 😯
No, Windows 7 does not even have an ecache.sys file nor emdmgmt.dll. That gives me more reason to suspect maybe ReadyBoost and SuperFetch are integrated together.
This was something I already knew. The new Prefetch/Cache systems in Windows 7 are closer to the HAL (in fact, it’s right in-between the HAL and low level device drivers such as Storage I/O), and unlike Vista – ReadyBoost actually does provide performance enhancements even in systems with high-volume and high-speed RAM… ReadyBoost apparently also makes branch prediction for secondary calculations (e.g., non-FPU; i.e., GPGPU/DirectCompute) much better by giving the CPU even more possible code prediction results more instantaneously – this is something that traditional RAM in x86 architecture cannot do at all and is usually left up to L2/L3 cache entirely (due to it’s legacy roots). It also explains why Windows 7 is faster than Vista on older hardware – have you tried using a 4GB ReadyBoost drive on a Pentium 4 Win7 machine with only 512MB of RAM? WOW @ Loading Time improvements!
The fact that they are between the HAL and system drivers also might explain why you got BSOD’d a few times – it never happened to me at all when messing with ReadyBoost and Superfetch in 2008 R1 because it was a very optional component (as far as the windows core goes). Either that, or you/we’ve missed the ReadyBoot driver – neither ReadyBoost and Superfetch will not work at all without ReadyBoot, and if ReadyBoot is present without SuperFetch then it will not work either (both scenarios would most definately cause a catastrophic halt in the CPU aka BSOD in Windows terms).
ANYWHO…. SuperFetch+ReadyBoot alone should still work without any ReadyBoost references in the registry; insepcting Windows 7 and forcefully removing the ReadyBoost driver didn’t disrupt SuperFetch at all for me. But thanks for the info and data, I’ll continue to research on my hive comparisons of Windows 6.1 Workstation Vs Server. Cheers!