tjtenor4

Hey, I've been running Windows Vista Beta 1 for a couple of weeks now, and I just can't seem to get AIM working on it. It installs OK, and then it starts up once. But once I restart the computer, it doesn't load. The process loads, but takes up 0 CPU time in task manager. I don't think I'm the only one with this problem, there have been mentions of it on other forums, but no one seems to have found a workaround. Any ideas? other than wait for the retail release, of course :-Þ

I'm using Symantec Corporate 10 on Vista Beta 1, it works fine

So no one has any comment on this one?

Hey all, I'm pretty new here, but I've been spending quite some time working on an unattended install CD. Your instructions here are great. I've made successful slipstreamed SP2 & updates cds with no problem. The issues I'm having relate to installing the drivers for my Intel SATA RAID ICH5R controller. Now, I have successfully used the "raskren" method described in detail by raskren and bashrat. It works fine. However, no insult intended to anyone here, but I view this method as kind of "cheating," since you're hacking the txtsetup.sif file. So I started working on trainee's "method 2". I have had absolutely zero success with this method. I know you all like to see the code from my txtsetup.oem and winnt.sif files, but I have used so many variations I don't think it's worth it, 'cause I'd list one and you'd suggest something, and it would be something I've already tried but didn't post... you get the point. Just so you know, the error I'm getting consistently is txtsetup.oem causing error (18) in oemdisk.c at line 1747. This file is a background file created during the unprotected ("real") textmode portion of Windows setup. My question is, has anyone successfully used "method 2" to install an Intel RAID driver from CD w/no F6 disk? ALSO, I would like to point to some interesting links to which I do not believe anyone has referred yet: Microsoft's commentary on MassStorageDrivers from CD Same problem, seemingly solved This person had my exact same problem, but his solution did not work for me. Perhaps because he was doing a network install (which MS says is OK)? Anyway, any commentary would be appreciated. Thanks everyone.