tylau

I actually does not own a SCSI DVD, but from the sound emission you mentioned, it seems the DVD drive is spinning up from a spin-down state. I have read though some uitlity program that can let you disable the spin down of DVD/CDROM drive, but I can remember where it is and if it is specifically for the Pioneer you have.

Creative has just post something for W2K http://www.sblive.com/liveware/w2kfaq.html

PCI devices are confifured default by IRQ steering, unless ythe device is an ISA bus deivce than you can set IRQ manually. I f it happens that you need to take control of some PCI device manually, try this, disable IRQ steering in the "computer" tab under device manager. Many mobos has the last PCI slot sharing the same IRQ with onboard USB controller, so in order to avoid such conflict, also try moving the conflicting card away from the last PCI slot. [This message has been edited by tylau (edited 15 February 2000).]

hahahehahahehe...spooky folder iconic mania I mean how to turn off the email reply, I just got over 10 auto reply emails from this server. [This message has been edited by tylau (edited 15 February 2000).]

I am wondering what services I can disable or alter in order to speed up when I need to play games, (i can always log on as some type of "inhumane fragger", cool?!) BTW, I have only redirect my Telnet port to an unknown state and manually disabled this service, is there any way to turn it back-on remotely?! [This message has been edited by tylau (edited 15 February 2000).]

Their ONCE FOR ALL AND LATEST NT driver does not make it to W2K, and I would be among the first to complint if they does not get one for W2K soon.

In my experience with vide cards, most companies would make their fullest support for their main stream product first, ie, the V3-2000/3000 and when they have the effort spare they would move onto the V3500-TV. If you pay a visit to 3dfx website then you would notice that the existing driver supports even for W9X and NT are all having V3-2k/3k one version newer than those for V3500 counterpart. It is really hard to blame on 3dfx since for a video display card having TV tuning and caturing supprt is worthing double the effort to support than a plain 2D/3D only product. I have once had one of those integrated TV/capture display card and when I was entering the W95 swtiching from W31, I also have such kind of horror for not having anything besided the plain vanilla driver solely for the core display chipset instead for the auxiliay supports. After all, you would see any TV tuner/capture card on the market right now having W2K full release driver, arent you?

Hi Seldzar, to be fair I dont think it is the sole repsonsiblity of MS in these hardware driver related instability, many beta drivers and legacy drivers I have try on is actually making those crashed and blue screens. But since MS decided to up the performance in OS speed and allowing the lowest levels of access by VXD, that would concetenate these stabilities. MS is the laying down some unsafe pratice for the followers (hardware vendors). I would say once the hardware issues (device drivers) are sorted out, the OS seems not inferior in terms of stability to NT counterparts.

For Voodoo3, if the apps can utilize the alpha blending of the V3 driver, then I would say the output quality in many occasions is more or less similar to 24bpp, that would take close crutiny or expertise in differrentiating it from true 32bpp. And hardly noticeable in the midst of gameplay. I dont think 30fps is good enough for any realistic gameplay, and it seems for 3dfx is right on their part to prefer fps over bbp, since nobody care to play Q3A at 30fps leaving low down on the score rather than not switching to 640x480x16bpp and crank up you scroe as well as excitement.

Well guys, what I think of is just keep some patience and a little respect,since W2K is just around the turn, and I dont think creative can afford not having good support for one of its key product line in such a major updrade exercise. cheers.

Just dont give up yet! You could just try running with the safe mode and see if the problem still exist, if it doesnt then there are problems with all your hardware drivers, may be because of beta releases. Should the problem still persists, your mobo may be the source of the problem.

I have my good old Syquest EZ135 removable cartridge drive sitting there wondering how to connect itslef to W2K. Since it is still among the best, interms of drive performance for removable medias, it is a pity for not having further upgrade possibility from Syquest. If you know how to make it work in W2K, please post. I have try their latest ever driver on W2K but without a clue. The system hust comes booting with a blue screen stating that the driver unload itself before it is allowed by the system oskernel to do so. What is the catch or tweak required?

OK, it is the specific model in question, my one is a Syquest EZ135 (EPP model) 135MB cartidge drive. I have it installed on the following machine: Abit BX6 1.01 Bios:JL Award 4.51PG, all serial ports and IR disabled, parallel port using EPP+ECP mode DMA channel 3, EPP version 1.7 128MB LGS 7J CAS2 PC100 SDRAM PIII-450 SL3CC MALAY Voodoo3-3000AGP BIOS1.0-SD, driver beta1 Hayes Accura K56-flex ISA pnp modem IBM DTTA-351010 10G HDD, dma enabled. Pioneer DVD-A01 firmware 1.01 DVD drive. Realtek RTL8029AS 10bast-T PCI NIC. SB Live value PCI soundcard, W2k WDM driver. USB ACER 310U scanner. USB HID compliant mouse. pS/2 keyboard. MAG XJ-700T pnp monitor. W2K build 2195 release version, install on primary NTFS boot partition, file level compression enabled. Cheers.

Only the version 2.55 lastest release of PowerDVD is W2k friendly, you can go there for some demo fisrt http://www.cyberlink.com.tw The older version 2.50 cannot detect ASPI layer in W2K unless you have ASPI driver layer installed somehow. cheers. [This message has been edited by tylau (edited 11 February 2000).]

I have try to connect W2K machie with w95 machine using crossover cable (i.e. direct connection of NIC withour using a hub) it seems the NIC and its associated protocol(IPX/SPX) works fine(my RTS6029AS is W2K certified though), but without any packet receiving from the other machine. I am suspecting that if W2K is actually not supporting such direct cable connecting and ouwld necessitate a hub connection for my two machine only LAN. PLease help, Thanks. tylau

There is always something missing when I cant see the whole thread while typing; I have try to use DHCP service on the W2K to allocate IP address for my machine, and I have try to make sure it is not the cause of the problem then I have remove modem card driver and TCP/IP from my W2K machine but still no luck. I have try also manually setting 802.3 frame type, auto packet size, duplex mode on and off, including 10base-T (as it is communicating with the other machine that has a RTS8129 NIC(10/100-baseT). whew!

Hi all, This is actually quite problematic as I cant really figure out where is the source of the problem. Here is further on this problem, I have been using exactly the same NICs and media(cable) on W98/W95 machines for over a year without a problem, and I have checked many times the hardware NIC driver, protocol IPX/SPX and MSN service are bounded properly to my NIC; and I have set exactly the same DOMAIN name, workgroup name and computer name for my W2K computer as before. Network properties show the NIC is working properly, the LAN card is shown started with packets trying to send out (but not coming in). No computer is shown inside Network Naightbourhood except the local machine. I have also tried to clear everything insider network properties and start everything allover again, including NIC driver, protocol, and MSN service but still no clue. I have login using ADministrator rights in W2K and no security options has been set for my installation of W2K. My NIC is using the W2K included shipping driver for RTS8029AS. I may be a little loose on the terms used, it is a "direct cable connection with NICs" used. cheers.

I think the problem you are at is W2K does not getting the IRQ table from BIOS polling, instead it lock all PCI devices into PCI steering IRQ9. Instead, try to enable PCI IRQ polling within the device manager(under the tab of system device-->PCI bus)