xstatik
Members-
Content count
8 -
Joined
-
Last visited
Never
Community Reputation
0 NeutralAbout xstatik
-
Rank
stranger
-
Hi there, I'm having a major problem getting the Window Update site to work properly. Now when I visit the site and click the "Scan for Updates" link IE generates a yellow error symbol in the lower left hand corner. Double click on that error symbol and I get the following explanation: Line: 279 Char: 11 Error: Expected ';' Code: 0 I've reset all settings back to default under IE the control panel and still no go. The scan fails to start and I can't access any of the latest updates. In none of the site options work because of this damn Javascript error. I'm not running any ad blocking software or sitting behind a firewall. Is any one experiencing a simliar problem accessing the Windows Update site or is my copy of IE 6 screwed? Regards, xstatik
-
Thanks for helping me out with my question, greatly appreciate it. Regards, xstatik
-
Hi there, I've noticed that Windows XP install QoS as part of the default network configuration. Can I remove this? Does it affect the performance of my Internet applications? Regards, xstatik
-
Thank you so much for that! Regards, xstatik
-
Hi there, Is there a version of RegClean for Windows XP? Could any one recommend any other tools that will clean up and optmize the Windows XP registry? Regards, Carl
-
Hi there, I should have known better after read the large amounts of complaints that SB Live owners have on using Creative Labs driver updates. I decided to download the latest XP drivers for my SB PCI128 sound card and use them instead of what XP Pro installs natively. Bad idea.. choppy sound and poor audio plugin performance in applications like Fruity Loops 3.4 and Acid Pro 3.0. I now want to return to the native XP drivers to see if they are any better. Unfortunately the rollback option under the Hardware Devices control panel doesn't appear to be working properly. It just rolls back to the CL drivers! How I can manually install the native XP drivers? Can I download them from Micrsoft? (I tried looking at their Coporate Windows update site but it only supports Windows 2000/NT4) Can I install them manuall from the XP Pro CDROM? Any help on this would be greatly appreciated. Regards, Carl Osterly
-
Hi there, I've just downloaded the newly released Windows 2000 Liveware drivers from: http://www.soundblaster.com/liveware/w2k/ After downloading all 5 files and then executing setup.exe my machine completely locked up. After that, I rebooted my machine, a dialog box saying a service PfMonNT.sys failed to start. My SB Live card is still functioning with the basic drivers that have been supplied in Windows 2000. I have not previously installed any leaked or beta drivers on this machine. How can I get rid of the error message? How many others of you out there have managed to install and use these drivers properly? Any help or advice would be greatly appreciated. Regards, Carl Osterly
-
Hi there, I've been following some of the posts related to complete machine lockups when installing SB Live cards under NT4 (without Dual CPU's installed). One guy I've spoken to from this board discovered that one of his SCSI hard drive drivers was buggy and by turning off some settings he was then able to avoid any future lockups. I'm getting really desperate, as I've tried just about every suggestion provided on this board along with Creative Labs tech support people. After inspecting my SCSI control panel applet, I must have one of the weirdest setups. All my IDE devices are considered under the control of my Iomega IDE SCSI adaptor driver. I just want to know is this all normal, should all my IDE devices appear here in the SCSI applet, or should only the CDROM or none at all? Take a look at: http://home.primus.com.au/liquidweb/scsi/devices.gif http://home.primus.com.au/liquidweb/scsi/scsi1.gif http://home.primus.com.au/liquidweb/scsi/scsi2.gif Can any one shed some light on this, even if it means nothing to my current SB Live problems at least it will clear up some issues as far as NT handles SCSI devices. Any comments or suggestions would be greatly appreciated. Regards, Carl Osterly