InCD burns CMOS

hi all windrivers
hi NooNoo and Confus_ed as well.....

this is the new thread (8/24/04 10:34am Tues)

old thread was "more code 10 .. Firewire device" for anybody who wish for more history of Event 9....problems....which I've concluded were caused by InCD.

Most of yesterday was just more of the same...Event 9....caused as best I can determine by InCD...the older version 3.5.19.1 actually . So I went to Nero Website and downloaded the latest Version of InCD (version 4 and some more numbers, ending with 10) . I also downloaded a CleanInCD tool. Read some of thier propaganda.

MyAction :
* Ran Clean InCD (removal tool)...actually after running Remove InCD from Windows Control Panel.

RESULTS:
* It cleaned out the Folder and my new Zippped Downloaded New version as well which I had put in a Sub directory. So I went back and downloaded again. No Problem, Internet History folder had a the FTP link just waiting for me to click it. Very fast and it came un_zipped...not sure why...Anyway, I ran the "EXE" ...It installed.

Good, now reboot, OK cool, OK now open CD_RW drive, click on My Computer. BAD Idea I guess..> System FROZE.....now it won't even POST

I'm inputting this reply to you (windrivers) from my other PC...the Intel Box.

My ACTION:
* As per nero website propaganda...went to Task Manager and Ended process.

Note: This was the first time this version of InCD had been ran and it hung Explorer on the first click of the mouse when attempting to see CD_RW drive.

While at TASK Manager....there was also a new InCDsrv.exe process so I Stopped it as well.

I'll end this thread for now and look for any feedback...

I've already tried to boot the (Tyan Box) with all the drives disconnected and that didn't make any difference....No POST, NO verbose monitor info, NO Beeps,

The only thing I can report is that the IDE (atapi) CD-rom drive activity light blinks on and off every few seconds... assuming I plug-in the cable.


ron_of_orange

10:49am, PST

did you uninstall incd and try without it before your machine was toast?

Sounds like you unseated something when messing about... or gave it an unhealthy static zap.

There is NO WAY incd can flash/burn your bios.

Quote:

---

Originally Posted by NooNoo

did you uninstall incd and try without it before your machine was toast?

Sounds like you unseated something when messing about... or gave it an unhealthy static zap.

There is NO WAY incd can flash/burn your bios.

---

yes, I believe all you're asking is did I un-install InCD which is yes. This will not allow you to access the drive however...you need a Program.
No Program, no drive.

No physical removal of components. were made until after it Crashed on Explorer (mouse click) and several attempts to reboot. The machine had to be powered off from the power supply main switch...on soft-reset/stop button I/O ...which is indicative of un-resolved items causing the shutdown to drag out for who knows how long...you could wait for days......

Then came the NO POST


+++++++++++++++++++ info from TYAN +++++++++++++++++
Why does my system hang during POST with my Intel Pro/1000 MT Gigabit
Ethernet card installed?
This issue was fixed in an Intel® Boot Agent Firmware update. You need to
run Intel® Boot Agent v1.1.07. It can be downloaded from the following link:
http://www.intel.com/design/network/...s/sla_ibag.htm
++++++++++++++ end info from TYAN +++++++++++++

I've sent for support at TYAN "an explanation" of what's been going on with InCD and the Failure to POST.

I've also Reset the Bios (or just maybe) ...cause I really don't know if anything happened. The PC still doesn't POST. I've measured voltages I do have 5 and 12vdc at the drive Molex connectors...fans are running,etc. No smoke.

The Intel 1000 MT Pro Gigabit Nic card is a rather new addition to both of my PC's and both are having InCD problems. I do have the newer Boot Agent from Intel. But it does seem rather interesting that the Intel Boot agent could interrupt the POST. I know you can boot up a computer from a NIC...but I haven't set my PC's to do that...unless there's something being done auotmatically that I'm un-aware of.

So< the next thing I'm going to do is...remove the Firewire card and the Intel 1000MT pro Nic card.
I've now stripped the mobo down to just the dual CPU's, and fans,

I pulled the memory, no cable to the vga monitor...the drives do have the power cables but no data/control cable...still no POST, NO BEEP, nothing....it does power down from the power button after 4 seconds which is the way it was set up....the soft-reset doesn't have any effect.

You can hear the SCSI drives power up when you first turn on power and the lights activate on the drives+++...seems normal. I which it (MOBO) would do something besides just sit there.


I've been using an IOgear KVM cable so that I can share my keyboard, mouse and monitor between each PC....been working fine...anyway I disconnected that as well from the TYAN box ... no beep


(FYI) Lights on the 2 NIC ports blick on and off.
Guess I'll plug in the built-in vga , then????

all suggestion are welcome....
it's too late to shoot it, maybe I should bury it. hopefully TYAN sends the RMA. then theres' InCD???? well I don't know how a program could cause such a thing either....I do know enough electronics to imagine a way for this to happen...but so-called better brains have been used for years to prevent this type of event....so I believe in the tooth fairy too perhaps.


ron_of_orange
4:14 pm, PST

INCD cannot possibly cause a motherboard not to POST. It is software.

Posting involves the bios talking to and receiving info from only the hardware.

Scenario 1 - you had a hardware fault coincidently that caused problems with the software which got progressively worse.

Scenario 2 - you suffered a mains dip/powerspike that caused a hardware failure

Scenario 3 - something is shorting out the mainboard - a foreign conductive object got inside the case.

Scenario 4 - the cpu overheated and the alarm has been turned off or the video card died.

All of the above are hardware related problems which cause the symptoms you describe.

Quote:

---

Originally Posted by NooNoo

INCD cannot possibly cause a motherboard not to POST. It is software.

Posting involves the bios talking to and receiving info from only the hardware.

Scenario 1 - you had a hardware fault coincidently that caused problems with the software which got progressively worse.

Scenario 2 - you suffered a mains dip/powerspike that caused a hardware failure

Scenario 3 - something is shorting out the mainboard - a foreign conductive object got inside the case.

Scenario 4 - the cpu overheated and the alarm has been turned off or the video card died.

All of the above are hardware related problems which cause the symptoms you describe.

---

+++++++++++++++++++++++


not a disbute about software being a cause....just sharing things I recieved from TYAN and describing problem as it presents itself to me.

Scenario 1 is under investigation...Nero and TYAN now online to review same info I shared here.

Scenario 2 I have a 700 va battery backup (simlar to UPS) from which all power is derived to both PC's and the shared monitor. Even the Wall Wart for the Firewire Drive is fed from this source. So dips are pretty well handled....I've never had a PC's go down for lack of power or a dip...over 10 years as of now...never. But I tested it today just to see how well it's holding up... The batteries are perhaps a year maybe two maximum old. They lasted a real long time the first go around.

scenario3 Could be a cause. Board and case have been blown out as of today....and were kept pretty clean on a semi-quarterly schedule or there-abouts....also in a home-office environment.

Two CPU"s have been swapped....everything removed including RAM, vga, mouse, Keyboard....and still no POST...NO beep.

But 1 Cpu had a loose heatsink.... and I found moisture on the actual CPU. So 1 bad CPU is now very suspect.

I don't know if anything is bad, but I'm looking very close now.

I'll most likely be getting an RMA from TYAN...seems they are being responsive so far.....

But that doesn't solve the question does it.

ron_of_orange

more later, maybe sooner
11:48pm, PST

Frankly ron, I don't know what your question is.

Quote:

---

Originally Posted by NooNoo

Frankly ron, I don't know what your question is.

---

Sorry for any confussion....let me re outline the situation with a little history.

++++++++++++++++
The original question started out as what I thought was a Code 10 error. (my original thread)

This problem was mis-interppreted and after some evaluation morphed onto an Event ID 9 which has

as best I can determine may be associated with InCD read/write commands. These events appear to

initiated by a mouse event calling for access to my CD-RW. This in-turn caused the "explorer

process" to hang, but no new events appeared in Event Viewer.

First three questions:
Why does the above happen? Is there a fix?. What is it?....

If I could answer these three questions I was hoping to go the next step and hope to find out why or

what may have contributed to the TYAN PC failing to POST. This was a catastrophic event...It

seemed to associated with the Event ID 9 events. But, perhaps as you have pointed out it may have

had a combination of causes. The preferred answer being something physically failed.

As a communication to you and any other who may choose to contribute I may have posted what

might qualify as a staus report of the current situation.

Namely, I'm in a HOLDING pattern, having exhausted all easily verifiable diagnostic tips. Or at least

with my limited resourses.

When the above Thread was thought to be a dead end I determined that perhaps a new thread would

be more beneficial.

So now were here as best I can tell and I apologize for not being very specific.
Fourth question:

Why doesn't my PC post?

The events ID 9 was repeatable on both of my PC's

both are dual processor server boards.
both run on W2k Pro/ sp4...both have Scsi hard drive(s)
both have one CD-rom drive which is (IDE) Atapi
both have Intel 1000MT nic card with Boot Agent feature (Tyan support had reported problems)
both have pci firewire card
both have on-board VGA
both have on-board USB
both have built in NIC(s)
+++++++++++++++++++++++++++++++
The Intel Box has a L440GX mobo
The TYAN box has a TYAN S2462ung mobo
+++++++++++++++++++++++++++++++++++
The common device was the CD_RW which I had hoped to use as a common storage device.
==========================
Both PC's had at one time the Roxio EZCD Creator 6 programs. The usual concerns associated

with this ( per the Nero and Roxio Website Q & A) is that they do not recommend running both

programs on the same PC. Conflicts may occur!!!. I was guilty of this error, and have done what I

think is a thorough removal of Roxio drivers, even those not easily associated with my problem(s)

So, does this help...I think so and perhaps it will help anybody else who follows this subject.

ron_of_orange
11:23am PST

As to why these things happen, unless you reverse engineer the code, you will never know.

The fix is up to the software company involved

Roxio are well known for producing less than perfect software for all situations.... Roxio wrote xp native burning, you would have thought that Roxio Easy CD 5 would be compatible wouldn't you? It wasn't.

Reasons for your pc not posting I went through before.

Quote:

---

Originally Posted by NooNoo

As to why these things happen, unless you reverse engineer the code, you will never know.

The fix is up to the software company involved

Roxio are well known for producing less than perfect software for all situations.... Roxio wrote xp native burning, you would have thought that Roxio Easy CD 5 would be compatible wouldn't you? It wasn't.

Reasons for your pc not posting I went through before.

---

Late statements...very late...Sorry

The efforts to remedy the Event ID 9 errors on my two PC's
has finally exhausted itself. The results are disappointing.

Nothing I did worked.

Efforts included:

Replacing a mother board in my TYAN box.
Two (2) RMA's for the Firewire CD_RW.(they replaced the Drive and the Logic board)

I tried virtually every Microsoft "Hot Patch".

My conclusions:

The product provided by Ahead (Nero) named InCD is bad.
The product provided by Roxio "Drag & Drop" is bad as well but might be less so

I can only say one thing in thier defense. They may open once, run once, maybe twice, if you're lucky.

You might get better milage then I did, if so I'm happy for you.

The UDF format including Mt Rainier variations is at best a single stand-alone software attempt
to rectify a bad situation.

Compatablity doen't exist between Roxio's Drag & DROP and Ahead's InCD program.

I'm totally disappointed with the UDF format.
The whole idea of accessing a CD disk and using it like a floppy is still a dream in my opinion.

The second next best choice for "wann_abe CD_RW user's" is CDR...end of story.

This experience was provided via Windows 2000 Pro SP4 including updates.
I've been trouble-shooting Windows and the programs/devices for 10 years PLUS...
I'm no expert...nor am I a rooky...MCSE, A+cert...etc

Final notes:

I just recreated the same error messages in Event Viewer today..
Event ID 9.....Source sbp2port
The description for Event ID ( 9 ) in Source ( sbp2port ) cannot be found. The local computer may not have the necessary registry information

or message DLL files to display messages from a remote computer. The following information is part of the event: .

followed by Event ID 51....cdrom
An error was detected on device \Device\CdRom1 during a paging operation.

followed by Event 11....cdrom (55) Fifty-Five times in a row
The driver detected a controller error on \Device\CdRom1.

followed by Event Id 9...same (30) Thirty times in a row

The OS was hangin...extremely slow response to "click-events"

I had to unplug the Firewire cable and the DC power to terminate the ID 11 events
then the OS recovered.....

This was seen as two Events ID 11
followed by event 135
Received a device interface REMOVAL notification for device:
\\?\SBP2#BUSlink_&CDRW____&LUN0#0006ca0200006810#{ 53f56308-b6bf-11d0-94f2-00a0c91efb8b}
followed by Event 134
Received a device interface ARRIVAL notification for device:
\\?\SBP2#BUSlink_&CDRW____&LUN0#0006ca0200006810#{ 53f56308-b6bf-11d0-94f2-00a0c91efb8b}

This time Roxio was reading a UDF created disk....It's still operational after the recovery, but
I'm not happy......perhaps the UDF format and Microsoft driver "sbp2port" over firewire are the real problem????

Maybe a new OS???? ...

LOL
good luck to u all\
thanks

PS the file transfer over the 1 gig Peer to Peer Lan (crossover cable/no router) to the CD-RW works really good...

this is my work around solution to swapping the firewire cable between the 2 PC's
+++++++++++++++++++++++++++++++++++++++++
ron_of_orange

11/20/2004 3:24pm PDT