Hi Everybody, Here's the highlights of my system errors. If only I could resolve my DVD issues. I'm pretty sure the VMIS ones are due to my removing VAIO Media Integrated Server program and then doing a system restore point to replace it. But had DVD issues before that too. The F (optical) drive has been quirky ever since I bought the laptop new, and will only play about one out of 50 DVD's I put in it. The drive will however still playback CD-R's I burnt tunes, so I don't think the drive's dead, just bunked up for some reason. As noted in the error log, I tried the check disc thingy for the f drive, but I'm a little at a loss about the rest of the recommendations. The f drive's DVD problems existed since the day I bought this machine and have grown steadily worse even though when it does play DVD's, they play flawlessly. I was going to try using RK Detector 2 even though its still in Beta, but I can't make heads or tailes out of even the screenshots of what the thing does. Same for the associated IATHooksAnalyzer. WOuld like to at least identify if I have Chrony's Trojan(s) on my OS as I hear they are causing DVD issues like mine. I'd hoped to see if I had XCP or MediaMax Trojans on my system because somethings been very weird even after I formatted this September, but then I did reinstall both Chrony's (I mean Sony's) SonicStage and Sony CONNECT (only to free my hostage held paid for tunes and get them into iTune, which I did only by burning them and downloading them that way). The discs won't play on my car CD player, but do on the computer. And I'm thinking I'm a victim of XCP or MediaMax Trojans. So many issues and so little time. Any (A-N-Y) contributed help would be appreciated. Except for the foul up of the VAIO Integrated Media Server program, I have done nothing to thrash my machine. I'm pretty sure it's simply having fits from too many programs all demanding dominance. Resources aren't an issues either. Anyway, here the worst of the worst on the error log: Thursday, January 12, 2006 MsiInstall er Product: Microsoft Office Standard Edition 2003 -- Error 1309. Error reading from file: F:\YI561403.CAB. System error 21. Verify that the file exists and that you can access it. Saturday, February 11, 2006 Application Error Windows cannot access the file F:\Setup_ST.exe for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Microsoft Office Setup Bootstrapper because of this error. Program: Microsoft Office Setup Bootstrapper File: F:\Setup_ST.exe The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C000009C Disk type: 5 Monday, February 13, 2006 Service Control Manager The Application Management service terminated with the following error: The specified module could not be found. Tuesday, February 14, 2006 Cdrom The device, \Device\CdRom0, has a bad block. Tuesday, February 14, 2006 PlugPlayMa nager The device 'PIONEER DVD-RW DVR-K12D' (IDE\CdRomPIONEER_DVD-RW__DVR- K12D________________1.10____\5 &1c4c23a3&0&0.0.0) disappeared from the system without first being prepared for removal. Tuesday, February 14, 2006 NetDDE Listen failed: 23: The ncb_lana_num member did not specify a valid network number. Tuesday, February 14, 2006 NetDDE Listen failed: 15: Wednesday, February 15, 2006 NetDDE Listen failed: 09: No resource was available. Wednesday, February 15, 2006 DCOM DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B 726-00C04FB926AF} Wednesday, February 15, 2006 Service Control Manager The DHCP Client service depends on the NetBios over Tcpip service which failed to start because of the following error: A device attached to the system is not functioning. Wednesday, February 15, 2006 Service Control Manager The DNS Client service depends on the TCP/IP Protocol Driver service which failed to start because of the following error: A device attached to the system is not functioning. Wednesday, February 15, 2006 Service Control Manager The TCP/IP NetBIOS Helper service depends on the AFD Networking Support Environment service which failed to start because of the following error: A device attached to the system is not functioning. Wednesday, February 15, 2006 Service Control Manager The IPSEC Services service depends on the IPSEC driver service which failed to start because of the following error: A device attached to the system is not functioning. Wednesday, February 15, 2006 Service Control Manager The VAIO Entertainment File Import Service service depends on the VAIO Entertainment Database Service service which failed to start because of the following error: The dependency service or group failed to start. Wednesday, February 15, 2006 Service Control Manager The following boot-start or system-start driver(s) failed to load: AFD BANTExt DMICall Fips intelppm IPSec MRxSmb NetB IOS NetBT RasAcd Rdbss SAV RTPEL SYMTDI Tcpip Tcpip6 Friday, February 17, 2006 DCOM The server {F3A614DC-ABE0-11D2-A441-00C04 F795683} did not register with DCOM within the required timeout. Saturday, February 18, 2006 Cdrom The device, \Device\CdRom0, has a bad block. Saturday, February 18, 2006 PlugPlayMa nager The device 'PIONEER DVD-RW DVR-K12D' (IDE\CdRomPIONEER_DVD-RW__DVR- K12D________________1.10____\5 &1c4c23a3&0&0.0.0) disappeared from the system without first being prepared for removal. Saturday, February 18, 2006 Service Control Manager The ISSVC service terminated with service-specific error 4294967295 (0xFFFFFFFF). Thursday, March 09, 2006 Microsoft Fax The Fax service failed to receive a fax. From: . CallerId: . To: Fax. Pages: 0. Device Name: CXT AC-Link Modem for ALi. Regards and hap-e-trails, Steve Hopper

Did it ever work? Was this a new system or did you make it in pieces? I think I'd consider a linux memtest or any of the many hardware diag test suites. Might consider using bios's safe or default settings. Might be time for a clean install. Might be an unsupported device or driver. If it came with a system recover cd/dvd then you might have to start over that way. Backup what you have first just in case.

Don't know if you've got a floppy or not but if so it might be worth booting from a Windows Startup floppy which has CD/DVD drivers on therefore you should be able to see and access your CD's and DVD's under DOS. You should at least be able to do a dir and see their contents etc. If the majority read OK then your problem is something broken in Windows, if they don't then the drive is probably iffy. PS: It's a laptop jefro so doubt he made it "in pieces"...!

Note that dual CD/DVD drives use different lasers and circuits for DVDs then CDs. So it's not unusual for a drive to read/write CDs but not DVDs or vice versa. Sorry, I do not check for private messages

Restored drivers (now) simply by using device manager to unistall the DVD/CD-ROM drive and rebooting seems to have restored all CD & DVD functions in the OEM optical drive. Regards and hap-e-trails, Steve Hopper