Seldzar

Ok well Anachronox issue wasn't the Philips card as it does the same with the live but at least there are no odd noises =)

Defrag? =)

I have this card and I'm about to swap it back for my sblive *UNTIL* there are better winxp drivers. My solution for the crackling was to turn off windows sounds so it's silent. Aside from that there are no fixes for it apart from waiting for new drivers or ms to possibly fix it. The crackling is the least of your problems, anachronox in winxp with the acoustic edge is a nightmare, check this out: win2k & Anachronox(which absolutely rocks) eax sound = crashing occasionally, usually between level loads a3d = didn't play long enough with it on as the sounds seemed too loud and out of place no 3d sound = barely crashes and works good When I say crash I refer to Anano.exe generating errors WinXP + Anachronox eax = crash on load or 2 seconds in or 20 minutes in, competely random a3d = didn't bother no 3d sound = didn't seem to change much in terms of randomly crashing. I'll be swapping my sblive back in tonight and i'm sure that will make the game stop crashing in winXP. If not i'll come back here and post otherwise. But aside from that I haven't really had any issues with dvd playback, ripping, mp3, games or divx audio. Here's hoping philips isn't lazy *** with their drivers.

mattdaddyz, Install the via agp driver in compatability mode. Also I use the 12.90 or 12.41 drivers in winxp and don't have any performance issues, it's all good and smooth.

Just the 405c agp driver, don't install the rest.

Speeddisk speeds up the file coping nothing more. If its on your floppy run it at the command prompt then install it. Otherwise find it on a win9x box and copy it to the floppy then run it and install.

Heh no your not. Your using the official Asus drivers otherwise there would be no avimini.dll it would be nv_mini.dll. Asus drivers don't work in WinXP. www.nvidia.com Get the Win2k ref drivers.

It's a bad cd. Reburn the cd. Try at a lower speed or a better brand of blank cdr's I've had this happen a few times and I just reburned it. Try using a different program to burn the image than the one you used. If the image was on a network drive, copy it over and then burn it. Doing any combination of the options above should get you a working disc.

typedef enum, dude, your using a Acoustic edge in winxp? What is your hardware config as me and a buddy have one and in winxp the windows sounds have a popping/distorted sound but only at the start of the sound. For example in winxp the default sounds for right click and browsing to submenus are little clicks but on my Philips it's not even a decernible sound just some noise. On longer sounds such as an icq uhoh the popping/distortion is there just for a quick second at the begining of the sound and then is gone. It sounds kinda like someone touching the end of a live jack (that bzzzt sound you get out of the speakers) I'm just curious if it might be related to my hardware if it's working fine on your box in the windows sounds etc. I'll clarify the mp3 playback and gaming sounds are just fine. And yes the sound quality is awesome, it blows the sblive away.

Ok these are the results of fighting with the shares this morning and talking with shrink to clarify the main issue. ***warning this is not really secure*** Part 1. Win2k box connecting to shares on a WinXP box **this has not been tried with any other account other than the admin account on my win2k box** First ensure the admin password on your win2k box is the same admin password on your winxp box(right click my computer and select manage, under users change the password for admin) Next, on your WinXP box go to start/administrative tools/local security settings and change Network access:Sharing and security model for local accounts to classic mode. Lastly enable a share on your winxp box and leave standard anyone permissions(setting up sharing will now look just like win2k)Now try and connect to the share via win2k, intead of being prompted for a user/pass or getting a failed connection you should log right in and see the shares. This was done on my win2k box admin account (to)-> my seldzar account on my winxp box. Changing the share to classic mode seems to keep the shares after a reboot(even with the reset crack) part 2. Winxp box connecting to a winxp box share This one is a lot more complicated, it seemed no matter what I did I always got a failure even connecting to the box so here's the way around it. (this involves quite a bit mucking around, be warned) First, on each WinXP box go to start/administrative tools/local security settings and change Network access:Sharing and security model for local accounts to classic mode. Enable a share on each box.(if you followed through part 1 there is already a share on the second machine) Here's the tricky part, log in on WinXP box1 as a different user or in win2k if you dual boot Or log on in safe mode under the administrator account. Ensure you show all hidden files(folder optins) and copy all the contents of your current regular user folder(mine was documents and settings\seldzar)into the documents and settings\administrator folder.(This will transport most of your settings, icons, cookies etc over to the admin account) Right click my computer and select manage and browse to the user section. Delete the user account you normally use so that the administrator account comes up on boot(if you have any other users, ensure none of them are aministrator users or else administrator might not comeup, hell it might not come up anyway being that I haven't tested that far) Ok once the regular user account is deleted reboot and winxp should come up with administrator as your log in option. Once logged in and if all was done properly it should look almost exactly as your user account was with a few tweaks you may have done that need resetting. You need to do this to both winxp boxes if they are to access each others shares. You also need to ensure both administrator accounts have the same password. So in the end of this part you have: 2 winxp boxes. 2 administrator log in accounts set up as your normal accounts. 2 administrator passwords on each winxp box that are the exact same. 2 shares, one on each box. You should now be able to go back and forth to the shares on each winxp box from within winxp. If this doesn't work for you then I really don't know what to say other than it's working for me right now and you may have done somethign wrong or I didn't explain something properly(or even missed something) Post your results here if your brave enough to mess with your accounts in these unscrupulous ways. Edit: Spelling fix

Ok back one more time, redoing the dvd rip in win2k jsut to see if the audio is ripped properly. I installed the latest version of virtual Dub on my other winxp box (2495) and it had all the correct codec's lsited so no worries there. Chances are my previous issue with not seeing all the correct codecs was that the app was installed in win2k and I just ran the exe without installing it in winxp. I will double check withmy 2499 build later if this is the case.

Ok lets see, the compression to divx looked like crap(could have beent he 3.11 alpha codec I was using instead of the 3.20 which is what I got in now. The 1gb wave file with the audio had nothing in it, blank, no sound. In Winxp The max limit of mp3 encoding was 56k in virtual dub, in win2k it's up to 320k so this is that annoying winxp mp3 limitation. Anyone know of a way to enable the full range of mp3 encoding? basically though I got through ripping and encoding a movie, whether it looked like sheit and had no audio is not the point, it did all the necessary steps to complete the encoding. Still waiting to find out what problems you have.

Well aside from certain divx encodings not playing where exactly is your problem? I figured I'd give it a shot last night as a first attenpt. I used CladDVD 2.0 and followed the instuctions from their website I ripped all VOB files to my hard drive, removing macrovision. I then used DVD2AVI and converted the VOB's to a divX file. Once that was done I had the avi and the wav audio. I am now about to mess with virtual Dub to get the audio and video together, first attempt didn't seem to be doing anything. I had selected Divx Audio as it seemed to be the only place that had 128kb 48000 16kb/s option for audio. The mpeg layer 3 option didn't have that at all, highest was like 56kb. Could this be MS and winxp? I'll check that later in win2k to see if it changes anything. This is in winxp 2499.

OLEerror, now that is a good arguement for not providing the source and one I can agree with but still you have to admit, ms could have still provided the bare 2d functionality in the drivers, simply disable anything else and give a compatability warning. But oh well the win2k drivers work fine for 2d and thats all I need for my v3.

Where do you get this nvidia supporting crap from? This is how easy it is: Ms "hey, nvidia,can you pass us the source code for the v3/4/5 series so we can fix a few minor issues with our winxp whql drivers?" Nvidia "Sure here ya go(passes over source code)" MS "Thanks! Millions of customers will be happy now." Nvidia "Anythign else you need from us?" Ms "No the source code was all we needed, thanks again." Wow that was a whole lot of support on nvidia's side. The entire point is it would not have cost anything for nvidia to pass the code over to MS so that millions of potential nvidia customers would be happy and not harbor angst toward them for not being the great company it could be.

First off it was clearly stated by someone from MS that nvidia will not give them the source for the 3dfx drivers. That means directly or in directly they are the initiating cause. second, Nvidia has never supported nor have they ever had to support anything 3dfx, this was clearly stated in the agreement when nvidia bought 3dfx's IP. Basically MS coudln't fix a few bugs in the drivers that, in their opinion were severe enough to remove, and nvidia didn't provide the source so they could repair and get the drivers working to their standards so they removed them. So yes it is Nvidia's fault for being dirty bastards who like to screw millions of customers cause they don't like people owning a 3dfx card and want them to upgrade to an nvidia card. Having no drivers in winxp is the first step, whos to say it wasn't nvidia's urging that messed up glide and ogl? <-- that is most likely the bugs that ms wanted to fix.

cancel the detection and just delete the device from device manager that has the "?".

They have improved and are improving the upgrade path they just removed legacy junk and streamlined the codebase more. How much code do you think it takes to keep win95 and nt4 in the upgrade path? Probably a sh1tload more than without it. Also being that they want it to work well and be fast and smooth so cleanup the code and get rid of the 6 year old crap. Just face it, win95/nt4 is ancient in terms of code and support. I'm suprised someone isn't crying about how they can't upgrade from win3.1, geeez. Also on the point of nt4(even 95), most corporations running NT4 on their desktops are in now way gonna "upgrade" all the workstations so that they have possibly hundreds of flaky machines. They will do what well managed IT departments do, create a baseline image and reimage the pc's 1 at a time until they are all upgraded and freshly installed. Of course they will do extensive testing beforehand to ensure all their software works with it. The same would be true for any win95 os's in a corporation. So as you can see it would be a large waste of code , time and effort to make those available in the upgrade when it's completely pointless and the amount of people who will actually upgrade from those platforms is VERY small vs the amount who will do clean installs. This is just an excuse for more people to b|tch and cry and not pay for the full os. So you look at it this way, keep the upgrade for the very small amount of people who will upgrade their win95 os and then whine cause it's flaky. Or remove all that extra code, streamline the setup and upgrade, save lots of devel time and money, and make it better for everyone else? This also avoids ms being flooded with support calls for the brilliant people who upgraded win95 to winxp and it's puking on them which in turn costs more money. You tell me which one you would pick if you were the project manager?

**oops messed up my edit**

Ever thought that it might just not be possible due to changes to the os or limitations of win95? Or better yet that the best possible upgrade scenerio leaves the user with a incredibly flaky and unstable setup? Win95 is 6 years old, that is an eternity. Win98 is only half that and presents a much more refined codebase for them to upgrade from. I'm sure there's an official reason posted somewhere.

I've experienced some of those issues as well. We shall have to see what a new build brings.

Anyone got 2495? I tell ya it's not much use to me since you now have to activate before you can even log on. You can still get into the os via safemode with command prompt but replacing winlogon from 2481 isn't the solution. I've tried the typical unregister regwizc.dll and licdll.dll but I'm not in any mood to mess further, i'll let someone else do the dirty work anyone got a way in? or a bypass or *gasp* a crack?

No worries, it's all good. first install wasn't with the winlogon.ex_ and setupreg.hiv replaced second install was overtop without a format and gave the same problem with the files mentioned above. After that I formatted the partition and started again with the winlogon and setupreg files and all was good this time round, wierd. I like it thou, really fast now

Well be sure to let me know if you can get into the os as I ran the crack for 2495 from the web site i posted above and so far nothing but I'll keep playing with it. Let us know if you get in and how about you went and did it.

hmm ok thanks but I didn't want to have to rebuild the cd with those. I'll give it a shot. Update: http://xxl.at/winxp much easier crack =)