Hellafax

I've got the 8x4x32 for about a year now. No coasters (except when I've screwed up :\ ). No problems with software - everything seems to support it, and I haven't had to worry about flash updates either Good job LG for building a sturdy, reliable and good looking burner. I'd reccomend LG burners to anyone, but I'd also suggest that you go to a barebones dealer and get an OEM model - why pay more for the box and software when you don't have to? Cheers, and good luck.

You'll have to reinstall...sorry. Theres a different executable and processor driver for Dual-Processor installs... Have fun

augh -- the PIII-700 will be more than adequate. I'm running XP Pro just fine on a Celeron-466 w/320meg ram. On a ABit VA-6... you will have no problems with speed. I've done many an upgrade from 2000 pro without a problem. Cheers.

Hey kids -- I seem to have fixed my problem, by hard-setting the DMA mode of the HDD. I have a Fujitsu MPG3204AT-E - which supports UDMA5, though my MoBo (Abit VA6) only supports UDMA4 at the max. So I checked the Fujitsu Canada website, and downloaded the DMA Mode program, and set the drive to UDMA4. No more timeouts. Cheers -- hopefully this helps someone else, too... 8Þ

Hey kids -- I seem to have fixed my problem, by hard-setting the DMA mode of the HDD. I have a Fujitsu MPG3204AT-E - which supports UDMA5, though my MoBo (Abit VA6) only supports UDMA4 at the max. So I checked the Fujitsu Canada website, and downloaded the DMA Mode program, and set the drive to UDMA4. No more timeouts. Cheers -- hopefully this helps someone else, too... )

I'm currently running Windows Media Services through a Windows 2000 Media Server -- it gives you the option to stream through HTTP (port 80) which is probably why you are able to listen to Windows Media and are having problems with Shoutcast. Check to make sure that you aren't behind a firewall, as that may disallow the ports that Shoutcast is using. What we're doing is running our playlists with Winamp, then piping that into the Windows Media Encoder, which gets sent via Unicast to the Streaming Server, which has both a unicast and multicast streams for Off-Site and Intranet access respectively. Winamp is a pain for dealing with playlists -- ie. we can't manage them dynamically Ah well...dunno if I answered your question... Cheers -- CFSM - Radio Saint Marys - http://cfsm.stmarys.ca/

Hey Hey -- Used to get this all the time -- mostly ended up being case/processor cooling, or a funky bios. Run only one chip, boot to dos, and flash to the latest stable bios. Make sure the processor fans are making contact in the right places.

Anyone have a clue as to why I would receive these errors in my system log every once in a while??? "The driver detected a controller error on \Device\Ide\IdePort0." "The device, \Device\Ide\IdePort0, did not respond within the timeout period." Both appearing concurrently, and usually after a cold boot, or when system files are changed. It causes my Primary chain devices to go from DMA to PIO modes, though uninstalling the Primary IDE device and rebooting seems to fix it, and return the devices to DMA modes. Any clue kids?? Cheers

Yah, thx -- uninstalling the primary IDE and doing a reboot seems to work, but a pain in the ***, to say the least. Now, if we could just figure out why we get the Timouts in the first place, that would seem to solve that problem, eh? Cheers...

Ok -- yet another problem here -- I can restore my settings to those of a few days ago, and my HDD and CDRom stay as a UDMA4 and MultiWord DMA-2 respectively, - as long as I don't shut it off. Restarts seem to be fine, though as the setting are retained. I do, however get these errors in the system log: Two ATAPI Errors: "The device, \Device\Ide\IdePort0, did not respond within the timeout period." "The driver detected a controller error on \Device\Ide\IdePort0." I get a few of these within 15-20seconds in the startup. I also have, though unsure if its relative -- an ACPI error (hehe) "AMLI: ACPI BIOS is attempting to read from an illegal IO port address (0xcfc), which lies in the 0xcf8 - 0xcff protected address range. This could lead to system instability. Please contact your system vendor for technical assistance." Anywho, anyone have any clue???

hrm... okie dokie. Makes sense, I suppose. Thx for the help... *grumble* MS seems to have done something right -- much to my chagrin, and embarassment.

Hey all -- Heres the scenario; I did a format/reinstall of Windows XP Pro on my c: drive. However, I didn't do a files/settings backup. I have an encrypted directory/files on my second hdd, that I can't seem to recover the files from. How in the world can I work around this without the proper certificates? Cheers

Okie dokie -- Two things I'd try -- check to make sure that the drive still works -- Try using a 98 bootdisk (get one @ http://www.bootdisk.com/ ), then if that doesn't work chances are its a hardware problem (could be something as small as a cable loose) -- try doing an "upgrade" by reinstalling if it works ok in dos... Give it a whirl... Cheers

okie dokie kids, I finally resolved my problem, and thanks for the responses -- I attempted to replace files from the CD, restoring with new ones -- nothing helped.....sooooo, I reinstalled (upgrade into the same directory), and it seemed to fix my problem Although I can't trace my problem to any specific action, it probably occured after a botched windows update or crash. Anywho, cheers

Good Lord -- I'm sure that would work -- If I had rsabase.dll Soooo, I guess somehow that was removed -- dunno what else I'd be missing, but I'll try to restore that file from the XP cd - that'll work, right??? Any other files I should check to see if they are missing tha have to do with Security/RSA Encryption? Only one I found was within the system32\rsaenh.dll, and rsaci. something.... Anywho, thanks - lots of help )