The closest thing commercially-available that works much like Superfetch/Readyboost I have found is called eBoostr. I have the full version on my FTP. Worth a shot, if it doesn't work, its a simple click and uninstall. The only thing is you need to add eBoostrCP.exe as an exception in your AV or it will be picked up as a threat (false positive).

1. Download it here ftp://sealy1986.dyndns.org/Software/eboostr.rar

2. Extract the RAR

3. Go to the extracted contents and inside the folder, extract "eBoostr.v.4.0.0.554.x64.V4-TB.rar" (64-bit version for R2)

4. Launch eBoostr application (3,529KB size)

5. Launch Task Manager. Click on Processes tab and kill the eboostrCP.exe process.

6. Copy the eBoostrCP.exe and EBstrSvc.exe and paste it in C:\Program Files\Eboostr

7. Reboot and then eboostr service will be enabled and you can simply plug in your USB flash drive and use it as a caching device. If you have antivirus I recommend you simply install the program first, so you can add C:\Program Files\Eboostr folder as an exception.



The only thing that I did to get it to work was:

1. Install Superfetch service from R2 Conv GUI
2. Launch Superfetch.reg
3. Launch Readyboost.reg

Next I simply inserted my USB stick and when I went to Properties the Readyboost tab appeared. I have attached the Superfetch and Readyboost reg files in this post below.



The following guide below will give you a better understanding of how Superfetch works.

All of the Superfetch data is located at C:\Windows\Prefetch

The following experiment below will help you better understand how Superfetch works at a basic level.

1. Navigate to C:\Windows\Prefetch; assuming C: is your OS drive letter.

2. Delete everything in this folder EXCEPT Readyboot folder and Layout.ini

3. Leave this window open. Now let's launch an application. Go ahead and launch Calculator.

What do you see populated in C:\Windows\Prefetch?

4. Now close Calculator.

What do you see populated in C:\Windows\Prefetch now?

Notice how the contents of applications are not populated in the prefetch folder until after you have closed them. This is because Windows is learning what applications you commonly use and smartly "pre loading" them into memory. The only difference between the older Prefetching method in XP and the more advanced "Superfetch" technology in Vista/7 is that is has the ability to monitor a user's browsing behavior (aka the applications you most frequently use) so these applications are already preloaded into memory and ready to go.

When an application is launched Superfetch only keeps a working tally for no more than 10 seconds. This design flaw can troublesome on resource-lacking computers such as your netbook with only 1 GB of RAM. Already considering that your netbook's HDD is probably slow enough to load the programs it is understandable that your machine will probably never seen a noticeable tangible gain from Superfetch at all! Atleast on the applications that need it.



I use the PC Boot Timer utility to keep a consistent tally of your boot times. It doesn't keep a history of your previous boot times, but rather is only used for a single boot test. Just simply use Notepad or an actual pen+paper to keep a tally of your boot times.

PC Boot Timer here: http://download.cnet.com/PC-Boot-Timer/ ... 45234.html

WHOA!!!!!!!!!!!!!!!!! Interesting discovery.

I wanted to experiment with your problem on my laptop so I copied all my important stuff over and reformatted and put on R2. My laptop is just a simple dual core with 3GB of RAM, integrated graphics, 5400RPM HDD. Granted I have a T7250 and not a shitty Atom processor (LMAO sorry). But its nothing really special.

Here's the step by step instructions on what I did.

1. Installed Operating System

2. Installed .NET Framework 3.5, Desktop Experience, Windows Server Backup, Wireless LAN features. Rebooted.

3. Installed graphics driver. Rebooted.

4. Installed Superfetch service from R2 Conv GUI. Rebooted.

I rebooted a couple times and my average boot time was roughly 1 min 5. I noticed that loading Internet Explorer is a bit slower than when you do the same thing on a fresh install of Windows 7.

5. Next I opened command prompt and started the disk defrag service: sc start defragsvc

6. Next I changed directory to the Prefetch folder and created the Layout.ini file template.

cd \Windows\Prefetch
echo [OptimalLayoutFile] > Layout.ini

7. Next I built the layout.ini prefetch by issuing the following command: rundll32.exe advapi32.dll,ProcessIdleTasks

I waited for a few minutes for the list to populate.

Next I rebooted. Boot time went down a few seconds to 55 seconds.

I rebooted again and it goes down to 29 seconds (7-esque)!! Apparently Superfetch makes a huge difference in the performance of your boot time. Readyboost I would imagine would be more suitable at performance supplement for application prefetching. Keep in mind that these technologies are just a supplement to performance not a replacement. Your obvious best solution to performance problems is a hardware upgrade (more RAM, faster HDD or SSD,etc)

Not bad though.

I ran the boot optimization process and here's my result. Pretty freaking awesome if you ask me. I think I found my new love and her name is Server 2008 R2 baby.

Hi Enigma,

It's what I thought.

Whatever version you install, RtsUStor.sys (driver) is not loaded with Windows Kernel.



I tried both packs and the result is the same.

Please test it again on your release with this :



I think you may know where the issue is.

This happens sometimes on x64 platforms with 3G USB sticks too.

Regards,

Neige

Sorry for taking so long to get back with a prompt response, but i've had some really pressing issues that just couldnt be put off any longer and they took awhile to resolve. In the meantime, my dad bought me a new laptop as a late birthday gift, so I now only use the netbook when my other PC runs low on battery, which doesnt take very long. I am, however, upgrading the ram to 2 gigs, just placed my order online and it should arrive any day now.

Neige: Thanks for the tool you linked, it's definitely a keeper. i did use it on the netbook but it still showed the driver as being not loaded. So I gave up in frustration and reinstalled Windows, along with all the drivers. I then reinstalled AVG after that and the SD cards still loaded properly. I do think i found the reason why, although I'm not 100% sure on this, but I think that they failed to recognize because i wasnt safely ejecting them after use. when i used the safe eject feature, Windows read my cards each and every time without exception. when they werent properly ejected, any card i put in after that did nothing. as for the driver suddenly not being loaded by the kernel, i'm not sure why that would have been the case.

As for the 64 bit thing, I dont think thats an issue, my previous x64 installs on other machines have never had problems recognizing sd cards and usb drives, except in cases where the device itself was faulty.