D
Delrin
I posted about this problem some time ago, but I'm going to try again since
I have a "bit" more info on it. Maybe someone else has come across a
solution by now
I have Vista Ultimate 64 installed and working well, with the exception of
ReadyBoost. I have two devices that I know work with ReadyBoost since they
both work fine in my other computer running the Business edition, 32 bit.
The problem on this computer is that shortly after I select "Use this device
to speed...." it will create the ReadyBoost file on the pen drive, then,
somewhere between 20 seconds and a few minutes later, it will simply get rid
of the file. I can be looking at the contents of the pen drive at the time,
it just goes away. I've checked in event viewer, and the last related entry
is that of creating the cache file successfully, nothing about it having
vanished.
The system with Vista Ultimate is running off of an Asus A8N-SLI Premium
motherboard using the NV4 chipset, and the USB ports I've tried these
devices on are either directly connected to the motherboard, or off of a
motherboard header, no additional USB controller cards involved (which might
be my next attempt).
To make things more interesting, I recently tried putting in an older HD,
and installing the 32 bit version of Ultimate to test ReadyBoost...same
problem. I installed the 32 bit Business version to test that, same
problem.
The devices are a Sandisk 2 gig high speed CF card (internal reader
connected to mobo header), and a Sandisk Cruzer pen drive, 2 gig. Both
devices work fine on my other (older) computer, niether work on this one
I've run the NV4 platform driver from NVidia, version 15.00 to see if that
made a difference, but it did not. I guess I wasn't too surprised there, I
don't believe it has much / anything to do with USB support for the
motherboard, but I'm reaching. I found a hotfix for Vista 64 that mentioned
something about USB compatibility, can't recall the KB number of it off
hand, but tried that as well, no help.
Has anyone else had this problem? And, if so, maybe there is something in
common with the hardware we're using? I'm just trying to find an answer
Thanks for any input!
-=D=-
I have a "bit" more info on it. Maybe someone else has come across a
solution by now
I have Vista Ultimate 64 installed and working well, with the exception of
ReadyBoost. I have two devices that I know work with ReadyBoost since they
both work fine in my other computer running the Business edition, 32 bit.
The problem on this computer is that shortly after I select "Use this device
to speed...." it will create the ReadyBoost file on the pen drive, then,
somewhere between 20 seconds and a few minutes later, it will simply get rid
of the file. I can be looking at the contents of the pen drive at the time,
it just goes away. I've checked in event viewer, and the last related entry
is that of creating the cache file successfully, nothing about it having
vanished.
The system with Vista Ultimate is running off of an Asus A8N-SLI Premium
motherboard using the NV4 chipset, and the USB ports I've tried these
devices on are either directly connected to the motherboard, or off of a
motherboard header, no additional USB controller cards involved (which might
be my next attempt).
To make things more interesting, I recently tried putting in an older HD,
and installing the 32 bit version of Ultimate to test ReadyBoost...same
problem. I installed the 32 bit Business version to test that, same
problem.
The devices are a Sandisk 2 gig high speed CF card (internal reader
connected to mobo header), and a Sandisk Cruzer pen drive, 2 gig. Both
devices work fine on my other (older) computer, niether work on this one
I've run the NV4 platform driver from NVidia, version 15.00 to see if that
made a difference, but it did not. I guess I wasn't too surprised there, I
don't believe it has much / anything to do with USB support for the
motherboard, but I'm reaching. I found a hotfix for Vista 64 that mentioned
something about USB compatibility, can't recall the KB number of it off
hand, but tried that as well, no help.
Has anyone else had this problem? And, if so, maybe there is something in
common with the hardware we're using? I'm just trying to find an answer
Thanks for any input!
-=D=-