OverFlow wrote:

your welcome and have a great day!

UM just in case it may help someone else what were you doing....

I am going to guess You removed all the existing drivers useing nLite...

We add drivers to windows and we don't replace them unless there is an update. most standard IDE drivers dont have upgrades so removing them would make them unavaliable since they are not in the packs.

did i guess correctly?

No. care to try for whats behind door number 2?

Just kidding.

Actually my mistake was in having a mass storage driver pack from another provider and the second pack was causing the bashrat pack to get corrupted. I guess the moral here is... Don't mix driver packs from unknown sources, stick with whats available here.
I erased the other pack, slipstreamed with software from here and everything is oki doki now.
I just have to find updated drivers for the new laptops that are coming out from HP. The funny thing is that I work for HP (certified field engineer), but thats another story.
Anyway, thanks for your advice OverFlow smile

OverFlow wrote:

you shouldnt get driver errors in vmware or virtual machine as they emulate standard hardware

yes you are doing somthing wrong...

Thanks overflow, your response made me take a closer look at what I was doing and the answer was in front of me all along.
I finally integrated the driver packs and I no longer get the acsas.sys error i was getting.
Many thanks smile

I get the "arcsas.sys" not found error after slipstreaming with nLite and the current Mass Storage Driver Pack.
Am I doing something wrong, or is there a list of drivers that I can remove from the driver pack that may be causing this error?
Any help would be greatly appreciated.

*Note: I get the error after creating the .iso and loading it on microsofts Virtual PC

Josefo