drybij, M-Audio driver has a problem of some kind with something [sounds really profoundly put eh? :)] I know from experience. The solution is: after installing the software, go to device manager, right click on M-Audio device [which should have a yellow exclamation mark on it] and do a "update driver">next>ok...>finish. It worked in case of one of my clients with Firewire Solo. I`m not sure what seems to be the problem with M-Audio driver that the install doesn`t work as it should. Anyway, when it works - it works nicely. Maybe the new XPLite build will take care of that? I don`t have anything M-Audio at hand to try, mostly just RME stuff and they don`t have any problems with anything [ad :)]. Cheers!
Dux, I've been using your install for over 5 months now and it flies! I imaged that after installing my essential programs and recently restored that image (to delete PACE), there was quite a speedup again even though I kept it well de-fragged and cleaned (CCleaner and defraggler). So I updated Reaper etc (just pasted the 2 Reaper folders back in) and made a new current image...it's mad that you can restore your machine back to such a fast clean state in a few minutes. Anyhoot, a question...I use the Fireface 800, it runs fine but I was wondering if we need the famous 'Firewire fix' with your build or not? It sounded like that was just relating to 800 speed not 400, which is what I use only....or perhaps I understood that wrong. If it is required, perhaps you could pop that into your new build? Save some work for the IT challenged... :D
--------------------- Level One BMW Master Tech - Chicago Illinois. (actual dealer not shown for my own protection.)
Sorry if it's OT, but do you guys know a free/shareware app I can use to make an image of my Dux drive, or should I buy something? It's great BTW Dux, boots in 7 seconds, thanks for your help
You know I actualy have been having a pretty big problem with my Dux xp install. I open reaper and every once in a while it just closes on random. Its really annoying. Any idea what it could be? Like it doesnt matter what vst's sometimes I'm just editing a basic wav with nothing open and it will all of a sudden close down with no warning just poof and then its gone! What have I done wrong?
Hey Obi, what are your PC`s specs? e.g. what CPU, VGA, motherboard, RAM? I`ve rarely seen Reaper go poof, EnergyXT more likely and it is usually more down to VST/VSTi`s you use than the program you use, but drivers can also be the issue, so many factors actually... Cheers!
Well, fellas - I made a little progress getting the FastTrack Pro ASIO drivers installed. I went back to a slightly older version of the drivers, it's a WDM driver package actually. This package installs the WDM and ASIO drivers all in one shot, there is no install phase after detection of the hardware. So I have ASIO drivers, just not from the version of the installer I'm used to using. If I then try to install the newer drivers over the older drivers, the older drivers are removed and I'm back to where I started. It still appears to me that for some reason, the detect-and-install part of the process is crippled on this stripped-down XP. When I plug in the hardware, it's detected, but the driver install isn't started. Anyway, thanks for everyone's help. This version on XP still rocks!
Obi, You find the Event Viewer in the Control Panel. Open Administrative Tools, there you have the Event Viewer. Look under Application for error marks, double click to get info.
Just chiming in to say how thankful I am for your expertise DUX. I like clean installs, minimalism, and I use old computers, so your XP install receives great reverence around here. I still remember reading through that 17 page thread this summer... wow. Best, Jake