more Code 10..Firewire device

hi anybody?

Code 10 problems.....they definitely SUCK....I'm going start with a quick description of where I'm at.

I have two PC's.....both generate "Code 10 errors" when I try to re-install an External IEEE 1394 SBP2

BusLink CD_RW.

Both PC's are running Windows 2k Pro.

The Tyan Box is the newer of the two.....
Mboard is Tyan 2462ung....This is a AMD Dual 1400Mhz.Processor Server Board
1 Gbyte Ram.
Came with no Firewire Ports....so an add-on Pci Card is required.

The CD-RW actually worked at least for a short while....Then, I crashed the OS..I re-installed over existing

OS....w/ new SID ...(I forgot I had a backup stored on it...LOL) So, I've been re-establishing new links, etc to

all my OLD programs......(most were in other partitions...but not all).
Currently this box is nearly complete.

Service packs...yes up to SP4.....just chasing this problem.

++++++++++++++++++++++++++++++++++++++
The other box is my Intel Box....a little older
MBoard is a Intel L440GX.....(dual 700 Mhz processor)...A server board
256 Kbyte Ram
No Firewire ports...So add on is required.

This box has not been a problem....running fine. So I thought that if I could get the CD-RW to work
on it maybe I could fix the the Tyan Box....

So I've chased down most every SP pack and driver upgrade I can find...Still no LUCK....except BAD

++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++
I've seen some suggestion for the ASUS mother boards where re-setting the BIOS was successful for a

similar CODE 10 problem (different device).

I've also seen a successful Utility program with a file named "TOGGLE" (toggle.exe)...which was provided for

some Nvdia device. A guy in France has a FTP site.....It's still ther...so I down loaded it.

Haven't tryed it......

I've seen some discussion about a need for more resources (IRQ's). And some suggestions to pull all your

cards out and/or move the Firewire card to a different slot.

I haven't seen a real "Honest to goodness Fix".....

A lot of people have these Code 10 problems....some are USB...some Firewire....mostly different
External devices.....

So where am I at now.?....Pretty much lost I guess.

If I haven't tried to correct this (Code 10) on one machine, then I did tried it on the other. Still no real fix.

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

AS of now...I'm thinking to pull the firewire card...power up, power down, then reinstall firewire card.

First I'll try this on one box and thern maybe the other...
++++++++++++++++++++++++++++++++++++++++++++
If I find a sure fire fix ...I'll be back to post it....In the mean time if anybody else finds a real SURE Fire Fix

Let Me Know...

thanks in advance, to any and all

ron_of_orange
2:40PM, PST

more info associated with Code 10 errors
+++++++++++++++++++++++++++++++++++++++++++
Event ID: 9
Event Source: sbp2port
Event Type: Error
Event Description: The description for Event ID ( 9 ) in Source ( sbp2port ) cannot be found.
+++++++++++++++++++++++
application error Event 41
WMI ADAP was unable to create object index 2022 for Performance Library MSDTC because no value was found in the 009 subkey
++++++++++++++++++and similar+++++++++++++++++++++++++
event 41
WMI ADAP was unable to create object index 2136 for Performance Library IAS because no value was found in the 009 subkey
Comment: Keywords: kbprb w2000mm KB266416

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

ron_of_orange
3:08 pm
pst

more Code 10 info
this is from W2K file setupapi.log

This may be useful, or perhaps not.....I like too think that it shows the drivers being installed and or changed by Windows Device manager..


It also shows error 10.....occurring several times today. This Code 10 error is a result of Event 9 and/or Event 41...see in my earlier posts today.

Still no luck...

I did create one BSOD (blue screen of death) trying to reinstall the driver
on top of itself....

Card has been in and out of the same PCI slot as of now..

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

So next I'll try moving to a different slot

Ron_of_orange
4:20pm, PST

well I move the Firewire card...no help

+++++++++++++++++form a different Web site+++++++++++++++++

the following few posts describing same problem on an ASUS m.b.


************************************************** *****************
Comment from shekerra
Date: 07/26/2003 03:41PM PDT
Comment

Go to Start | run and type regedit

Remove the Upperfilters and Lowerfilters values completely from the
following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E965-E325-11C
E-BFC1-08002BE10318}
************************************************** ******************

I was having the exact same problem. You suggestion worked perfectly. Thank you!!



Comment from rayandmel
Date: 02/05/2004 06:50PM PST
Comment


edvardr did you solve the problem as i just purchased an Asus A7N8X-E Deluxe and have the same problem got the latest drivers form Asus but no go

Comment from edvardr
Date: 02/10/2004 09:35AM PST
Author Comment


No, I never found a solution. I have a addon FireWire card I use instad.

If you find any solution it would be nice if you post it here.



Comment from rayandmel
Date: 02/10/2004 05:39PM PST
Comment


After Hounding Asus they said the motherboard may be faulty and to have it replaced so i will let you if it solves the problem

Cheers Ray

Comment from BlindWolf8
Date: 03/27/2004 03:42PM PST
Comment


Hello all.

I'm actually having this same problem, only with an Intel mobo and CPU. I've never used my Firewire, but was curious about it. I can remember a few times when it didn't have the code 10 error. Strange that it would appear out of nowhere. I have XP Pro SP1. I tried the reg hack that shekerra suggested, and this lead me to my CD-ROM drives. Also, I have tried flashing my BIOS, but the installer keeps saying it's unsuccessful.

Comment from rayandmel
Date: 03/28/2004 04:36PM PST
Comment


Ok i got my new motherboard and guess what all was fixed and now firewire just works as to what BlindWolf8 has said thats what happened to me int errors so would not supprise me if it is faulty too.


Comment from BlindWolf8
Date: 03/28/2004 09:24PM PST
Comment


Looks like all firewire ports intergrated on mobos are having this problem? This has to be a problem with XP if its happened on multiple systems...it's just plain freaky! :-P
++++++++++++++++++++++++++++++++++++++++++++++++++ +

my thoughts....???? I have to try the REGISTRY HACK perhaps....???

Some how I don't see this working either..

__________________________________________________

If anybody has a suggestion.....now would be good time

thanks either way LOL

ron_of_orange
11:25PM, pst

Welcome to Windrivers ron

Code 10 errors are usually a problem with the HAL which is based on the bios ability to handle acpi. First suggestion would be to either downgrade the hal to a standard computer, the second would be to upgrade the bios.

If you have the pci card in slot1 you will get problems with it sharing with the agp card. All slots share with something, you have to do the slot shuffle to find out where it is happiest.

Some people report that these device will ONLY work if you format and install windows with the device already present.

There are a number of windows updates for usb/firewire, apart from sp4, what hotfixes do you have installed?

hi NooNoo,

thanks for responding.........

I'll hold off as regards "Hotfixes".....and just say none for now.

I'm going to attach (hopefully a wordpad "doc" file) if it makes it OK.

It contains print screen shots from SYSINFO (winmsd)....no conflicts.

It also shows the OHCI sbp2 firewire host controller... as running.

It also shows a list of all my IRQ's ....I'm using IRQ 16...(not shared).

I don't think a HAL issue is at fault here...

If you see anything here or have more suggestion please continue.

ron_of_orange
11:29am,PST

Hotfixes may be the key, there a few which sort out 1394 and usb2 problems. here is a few to start with

Quote:

---

..I'm going to attach (hopefully a wordpad "doc" file) if it makes it OK..

---

Err so no you won't have - sadly the facility is turned off ! - the only way is to host the files yourself..

Quote:

---

.. don't think a HAL issue is at fault here..

---

Well since code ten means no resources available; it is ! ;) (in a bios context) just whereabouts in the mechanism the error/misassignment lives though is a different matter so like Noo says anywhere from bios to hotfixes ..

Personally I'd start with bios, so clear nvram, then reset board, then new bios, then slot shuffle (different slots have different resources available to them) also make sure you have as much un-needed stuff as possible turned off in bios like comm ports etc, thus freeing resources & simplyfying the whole process (also make sure you assign IRQs to vga & USB if not done automatically{assuming you want usb on}) , if you are "using IRQ 16" then acpi is being forced to share something as 'real' IRQ's run 0-15, win 2k has this system of 'virtual' IRQs(1-50) which seems very problematical ! ;)

hi :to confused-ED

re: attachments out of order....whoops..I guess we'll save a load of of storage space if we leave this feature OFF...no hard feelings as regards this option.

Your other suggestions may prove useful, however I'm inclined to follow the leads provided to me throught the Events Viewer Tool. This may not be successful...but so far it's been at least a good lesson on the pro's and con's of Firewire.

to: NooNoo,

I've looked into the "Hot-fixes"....I had sort of overlooked this option...so it was good for me to go look at the rather long listing.

All Hot-fixes have been install per the the SP3 and or SP4 service Patches.

So then while at the Microsoft Website I plugged in Different Event ID's
to further my investigation into this problem.

So, far I think I can ignore the Events 9 , 11, 134, 135, ...these are the Events that appear on my Tyan Box. None of these errors are of any use to the trouble-shooting required.....but are subsequent events generated from me trying to initiate access to a drive letter and perhaps an attempt to open a Folder.

Yesterday I did managed to Access the drive and open a folder and I might have actually copied a few "jpeg's" to the folder on that drive...

I'm not sure because I haven't been able to re-open the drive or folder with-out Explorer....locking up.....This will also cause Event 9....which is when the drive starts the repetitive spin-up/spin down cycling on a ten second interval. The systen then BOGS down to a crawl...usually forceing me to do re-start/re-boot. Event 134, and 135 are caused by me un-plugging the the firewire and or power cables....which I've done when I noticed the event 9 action.

The Event 4100 only shows up on my Intel box...

To re-cap on what a Event 4100 is ..I'm pasting here the Microsoft
information here ++++++++++
++++++++++++++
SYMPTOMS
On a computer running Windows 2000 Professional, the following information about event ID 4100 may appear one to two times a day in Event Viewer:

Event Type: Warning
Event Source: EventSystem
Event Category: Firing Agent
Event ID: 4100
Date: 3/4/2000
Time: 1:19:44 PM
User: N/A
Computer: NTWS2000K1
Description: The COM+ Event System failed to create an instance of the subscriber {6295DF2D-35EE-11D1-8707-00C04FD93327}. CoCreateInstanceEx returned HRESULT 8000401A.
RESOLUTION
To resolve this behavior, use the Regsvr32 tool to unregister the Mobsync.dll file from the server:
Click Start, click Programs, click Accessories, and then click Command Prompt.
Type the following line, and then press ENTER:
regsvr32 "%systemroot%\system32\mobsync.dll" /u

Quit Command Prompt.

+++++++++++++++++++end paste info++++++++++++++

The above infomation applys to The Synchronization Manager....

I've done just a little reading about this....and it may or may not be applicable to my Intel box....It appears to be assoiated with a different "Class" object.....

Then there's one more Event......which I've failed to mention so far...An Event 2002 offers the following:

Unable to open Redirector Service. Redirector performance data will not be returned. Error code returned is in data DWORD 0

Dword , info I believe is the following: c0000034

Source: PerfNet

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

That's it for now....Still chasing and still hoping to solve this problem

I tend to think that stripping down the Mobo and resetting the BIOS is not needed...after all...I did actually get it do operate at least for a brief time. The Explorer locking up is bothersome to me...



I cleaned out Roxio EZCD Creator 6.....

And I've now used RegscrubXp 3.25...which did clean-up the Registry and allowed me to get the TYAN box up and running...however briefly

for now....thanks

Ron_of_orange
8:36pm,PST

You know, somehow I think you maybe overcomplicating things....


Resetting the bios does not require stripping down the mobo.

Have you done the basic checks for spyware and virus? And before you say there isn't a chance you have a problem like that, think again!!

Quote:

---

Originally Posted by NooNoo

You know, somehow I think you maybe overcomplicating things....

---

Definately ! ;)

Many of the 'errors' will be as a result of the info being presented to the HAL, running your reg cleanup tool looked to correct that info briefly until another connected key sent is all 'screwey' again ..

Suggest at the very least you follow the 'turn off spurious devices' advice to free as many natural IRQs (0-15 inclusive) as possible, this gives the 'bios sum' (when any machine boots bios is required to arbitrate all the conflicting device resource allocations referencing bios, acpi info {gets changed by windows o/s} & the devices themselves - what all the constant re-tards are about with any new equipment & drivers), the best chance of working out right

Quote:

---

Originally Posted by confus-ed

Definately ! ;)

Many of the 'errors' will be as a result of the info being presented to the HAL, running your reg cleanup tool looked to correct that info briefly until another connected key sent is all 'screwey' again ..

Suggest at the very least you follow the 'turn off spurious devices' advice to free as many natural IRQs (0-15 inclusive) as possible, this gives the 'bios sum' (when any machine boots bios is required to arbitrate all the conflicting device resource allocations referencing bios, acpi info {gets changed by windows o/s} & the devices themselves - what all the constant re-tards are about with any new equipment & drivers), the best chance of working out right

---

++++++++++++++++++++ +++++++++++++++++++++++++++++
_____________________________ ________________________
hi con-fus ed,

Sorry about the delay...been doing things.

Briefly speaking the problem is still a problem...
Although I think I may have a found a slightly better definition....this one from Microsoft i think is pretty close...


===== pasted below here from MicroSoft =======


Removable Storage may stop unexpectedly on a Windows 2000-based server
SYMPTOMS
When you use Removable Storage to manage your removable storage devices, Removable Storage may stop unexpectedly. This problem occurs on a Microsoft Windows 2000-based server.
CAUSE
This problem may occur if Removable Storage causes an access violation in Svchost.exe. Svchost.exe is a generic host process name for services that are run from DLLs.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.

Version Size File name
--------------------------------------------------------------
20-Apr-2004 23:37 5.0.2195.6921 53,520 Ntmsapi.dll
20-Apr-2004 23:37 5.0.2195.6921 170,256 Ntmsdba.dll
20-Apr-2004 23:37 5.0.2195.6921 39,184 Ntmsevt.dll
20-Apr-2004 23:37 5.0.2195.6921 438,032 Ntmsmgr.dll
20-Apr-2004 23:37 5.0.2195.6921 401,680 Ntmssvc.dll
19-Apr-2004 23:14 5.0.2074.6921 47,376 Rsm.exe
05-Feb-2004 20:18 5.0.2195.6896 5,869,056 Sp3res.dll

=========end====paste===========

I haven't as of this posting gone after this "HOTFIX"......I have accessed the CD_RW...I even burned a couple of disks...I'm running Burning NERO....I don't care for Roxio EZCD creator.....and I do believe it was contributing to some of my problems.

My best description of the problem is:



Problem caused when attempts to access SBp2port device (Ext. 1394, CD-RW) creates Event ID 9....and hangs "Explorer"

I've been able to clear the "Explorer - hang" my ending the process thru TASK Manager.

If, I'm lucky the Event ID 9 which is usually generated at this time may not be repetitive as I've stated in earlier posts. It would sometimes do a repetitive spin-up/spin-down on a 10 second or 20 second interval

Then by re-intializing "Explorer" I've been able to go back to the CD_RW and "mouse" click the DRIVE LETTER, which opens the root directory of the CD_RW.

I'm closing for now...more later....

thanks for all considerations so far

ron_of_orange 2:55pm pst 8/16/04

Quote:

---

Originally Posted by ron_of_orange

..
hi con-fus ed,

Sorry about the delay...been doing things.

Briefly speaking the problem is still a problem...

---

So me too ! (been doing things !) .. err is there a question in this reply somewhere's ? - I'm all for as 'much info as possible' - but there are limits ;) !

Can I have a 'summary' of what you are complaining about ? (I've gone & gotten confus-ed with all these cut & pastes from other forums ! :D & to some extent your 'style' of posting ;) ) or have you now fix-ed it ?

Quote:

---

Originally Posted by confus-ed

So me too ! (been doing things !) .. err is there a question in this reply somewhere's ? - I'm all for as 'much info as possible' - but there are limits ;) !

Can I have a 'summary' of what you are complaining about ? (I've gone & gotten confus-ed with all these cut & pastes from other forums ! :D & to some extent your 'style' of posting ;) ) or have you now fix-ed it ?

---

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

hi confus-ed,
not yet....did the hot fix...still hangs. I am currently pursueing solution through BusLink (manufacturer of the Firewire CD-RW.) I have a Case number with Microsoft as well...but time is on my side.

here's is a short description of what I can't do with my CD-RW without it hanging when I boot, or perhaps when I click on a drive to open access, or perhaps to rename a file, or perhaps edit a file, etc. This problem is repeatable on two different PC's...

Description of Tasks (unsuccessful) as presented to the manufacturer
+++++++++++ pasted here FYI +++++++++++++++
hi Buslink Support rep's,

I would like to research with your assistance the following options in regards to the use and procedures for copying "data" files to and from a PC to your External Firewire CD_RW.

The particular model I have is the RW5252FE



Equipment:

Items (3-devices) to be used:

Personal Computer (1) one: an intel (with dual processors) box running Windows 2000 pro/sp4 with plug-in pci firewire card)

Personal Computer (2) two: an tyan (with dual processors) box running Windows 2000 pro/sp4 with plug-in pci firewire card)

Buslink CD_RW (IEEE-1394a) with Wall Wart Power Supply

Tasks:

1 Create a new folder(directory) on a blank CD_RW (udf_formated) using Nero Burning ROM version 5.5)
from PC 1.

2 Unplug Buslink CD_RW from PC 1, Firewire cable only (wih permission form the Taskbar tool)

3 Plug In Buslink CD_RW to PC 2, Firewire cable only

4 Copy and paste a file into the existing folder on the existing CD_RW disk still in the Buslink CD_RW drive.


5 Unplug Buslink CD_RW from PC 2, Firewire cable only (wih permission form the Taskbar tool)

6 Plug In Buslink CD_RW to PC 1, Firewire cable only

7 Open the existing file on the existing CD_RW disk, edit the file information, save it. Eject the CD_RW. Shutdown

8 Reboot, Repeat as needed, when needed.....until the Disk is full or re-formatted.

9 Shutdown

10 Reverse the sequence or repeat the procedure on either PC as desired.

11 etc

+++++++++++++++++++ end of paste +++++++++++
The attempts to perform the above tasks is Cause for an Event ID 9

I'm doing something wrong...anybody know what?

thanks for your responses to date
More later if this gets better sooner ....still pursuing

ron_of_orange
12:12AM PST

have you read this ron? it is important that you realise that while it apparently is only talking about scsi controllers the documents says "although the source can be any controller name (for example, Atdisk, Atapi, or Sparrow" and therefore should not be put aside without trying the recommendations.

Quote:

---

Originally Posted by NooNoo

have you read this ron? it is important that you realise that while it apparently is only talking about scsi controllers the documents says "although the source can be any controller name (for example, Atdisk, Atapi, or Sparrow" and therefore should not be put aside without trying the recommendations.

---

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

Yes, I've seen that and considered some Registry changes. A couple of them didn't help...but I'm still open to actual fix for Firewire changes.

Timing errors may be a cause...not real sure if there's a registry fix that addresses this problem....if anybody knows of one...please share..

for toady....here's a pasted NotePad file....i created today...which outlines
STEP BY STEP....my observation since Booting up my "TYAN BOX"

+++++++++++++++paste from here ***********+++++++

cd-rw troubling-shooting/research/notes 8/21/04 (sat)

Condition at time of successfull boot.
* no cd-rw firewire cable to C-rw, and no errrors in event viewer.

note: there is a non-finalized CD_RW disc in the drive from yesterday. power is available from Wall

wart.

MY ACTION:
* plug in cd-rw firewire cable

RESULTS:
*error in event viewer = Event ID 9

MY ACTION
*end "InCD" process at Task Manager

RESULTS:
* after some delay (1 minute approx) Event ID 9 stops its repetitive creation process which

was recurring every 10 seconds
*Event 134 (info) is presented...which is:
Received a device interface ARRIVAL notification for device:
\\?\SBP2#BUSlink_&CDRW____&LUN0#0006ca0200008189#{ 53f56308-b6bf-11d0-94f2-00a0c91efb8b}

MY ACTION:
* click on "MY COMPUTER"

RESULTS:
*Task Manager displays RUNDLL32.EXE

NOTE: THIS IS WHERE WINDOWS HANGS!!!!!!!!!!!!

*no cables are un-plugged yet.

MY ACTIONS:
* using Cont+Alt+Del > select Shutdown...

RESULTS:
* Windows Message dialog box presents "Rundll32.exe not responding and progress bar times

out.

MY ACTION:
* repeat "Cont+Alt+Del" to clear any other reluctant processes.

RESULTS:
*no effect...Wait, wait, wait wait...then use SOFT_RESET BUTTON ON PC...PC starts it normal

reboot and BOGS down as is apparent on the WINDOWS LOGO "Splash" Screen at approx. 70% progress

bar.
*at perhaps 3 minutes the "Windows is starting up...Message box displays, Logon Message box
*the system Task Bar indicates that several "TSR's"have not loaded as of yet...Wait, Wait,

Wait....Ahourglass can be presented when mouse hovers over task bar...wait, wait...clock at Task

Bar is Frozen...Wait, Wait, Wait, 5 minutes, then 4 more minutes pass
* finally a full Task bar

MY ACTION:
* go to Event Viewer and note the large quanity of Event ID 9 are listed. 11:31:45 to

11:45:15 and still counting (repetitive) on 10 second intervals.

MY ACTION:
* go to task bar an attempt to "UNPLUG" Firewire Device"...Unsuccessfully...!!!
* go to Task Manager, Open to view "Processes" note "RUNDLL32.EXE is still listed
* go to "MY COMPUTER" Icon on Desktop, click to OPen,,,,observe incomplete informtion.
* cLICK ON "x" TO CLOSE and get " Program not Responding... END NOW>>>> Message Box
* Wait a few minutes>>>try again, eventually "MY COMPUTER" closes

NOTE: System is basically non-responsive now. Event ID 9 is still be craeated at Event Viewer which

is available if you don't rush things too much

MY ACTION:
*un_plug (1) firewire CABLE ONLY....
RESULTS:
* System SNAPS BACK TO LIFE....
* two Event 11, and one Event 168 are presented at Event Viewer
* two RUNDLL32.EXE are listed in Task Manager
* all old "Dialog Message Boxes are now presented on the Desktop that were previously being

delay by hung system.

MY ACTION:
* Click on "CLOSE or OK to close old message dialox boxes to clear Desktop.
My Action:
*click on "MY COMPUTER"...it opens normal... go to Task Manager...note RUNDLL342.EE has

been cleared out

RESULTS:
* no Event ID 9 at Event Viewer

FINAL NOTES...THIS sESSION:

* a non-finalized cd-rw disk was in the C-rw drive for this entire session
* THE "InCD" processs (Nero Burining ROM Version 5.5) was present and running during this

entire session
* System is fully operational and is now in notepad where I'm creating this document for

pasteing...except CD-RW is not available.

ron_of_orange 1:12pm
+++++++++++++++end of pasted info+++++++++++++

more later...maybe sooner

ron_of_orage
1:23pm PST

So another thing worth mentioning (both for Ron & anyone who passes by also confus-ed by this) is that as far as windows is concernced All cdrw writing is done via scsi - oh no it ain't I hear you all cry, I've only got IDE or something else that ain't scsi, anyway nothing that is, so how can they all be 'scsi' writes ? ...

Well every single writing application there is ennumerates a scsi device for any atapi type writing, they all introduce a proprietry driver to ennumerate the scsi bus & take advantage of the direct functions of that interface, try starting any machine in safe mode & you'll find a 'non windows driver' {it says press 'esc' to avoid loading} hanging about, these 'drivers' though can be a nightmare .. (strictly they aren't really drivers, as they ennumerate a device class to take advantage of that classes features)..

Methinks this will get more solveable if we figure out whether ANY writing s/w is at fault or not - so I think that's relatively easy to figure out, take all your writing software off for now (also check via my 'safe mode trick' that we still haven't got some non-windows driver hanging about) & then see if we get all these reconnect issues ..

BTW all these other TSRs mentioned 'not loading' at various points can't be helping either, for troubleshooting purposes, the less running at any time the better .. RUNDLL32 simply runs a dll as a seperate process (makes it like an .exe or near enough) its never a very reliable way to fire anything due to how encapsulation works in an embedded programming environment (can't get released program hooks as not 'parent' process - leads to lots & lots of 'timing' issues !)..

& I just realised you've got INCD running all the time - this is packet writing s/w (makes a cdr type device 'behave' as a hard disk) - for now lets also be rid of this complication, first we want to know if the 'reconnecting bit' is getting done right, never mind buring s/w going 'screwey'..

INCD - wanna bet it is trying to "detect" the new device?

Quote:

---

Originally Posted by NooNoo

INCD - wanna bet it is trying to "detect" the new device?

---

.. & not doing a good job ! - In-CD is one of those 'nightmare' products, its not actually that bad itself, but because its completely reliant on o/s services for its feeds & working (its busy pretending that a cd is hard-disk via a 'driver' which is making IDE cd behave like SCSI) , so any 'not quite so' issues get blamed on it, but definately a spurious complication at this point !

If the 'removable drive bit' ain't working right (so how windows deals with refreshing removeable media catalogues & directories - what we apparently have issues with) then IN-CD has zero chance of working right.

btw the event log entries referenced in Ron's last post ..

Quote:

---

..Event 134 (info) is presented...which is:
Received a device interface ARRIVAL notification for device..

---

Is most definately meant to happen with any external device connection, this is the unit, signalling new media, its what then gets done with that, that's the issue, when it gets passed to the device driver, which here is the burning s/w's own proprietry driver..

Quote:

---

Originally Posted by NooNoo

INCD - wanna bet it is trying to "detect" the new device?

---

You're on the right track I think NooNoo and Confus-ed

Pasting here my "Daily LOG" (sic) of research events

+++++++++++++++++pasted+++++++++++++++++
hi all at windrivers

I been busy....going on 5 hours...just today and still counting..

read Confus-ed and NooNoo posts...

I think you're both getting closer to the Problem and the Answer.

Here's a little fuel for the FIRE from Dr Watson
It not current ...but still I think applicable to problem

+++++++++++ pasted fron Dr Watson ++++++++++++++++
Application exception occurred:
App: (pid=1232)
When: 8/18/2004 @ 19:22:00.375
Exception number: c0000005 (access violation)

*----> System Information <----*
Computer Name: MEANTYAN
User Name: capt ron
Number of Processors: 2
Processor Type: x86 Family 6 Model 6 Stepping 2
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 4
Current Type: Multiprocessor Free
Registered Organization: 3D_6Deep
Registered Owner: ron_of_orange

*----> Task List <----*
0 Idle.exe
8 System.exe
140 smss.exe
168 csrss.exe
188 winlogon.exe
216 services.exe
228 lsass.exe
500 svchost.exe
540 spoolsv.exe
620 CDANTSRV.exe
640 svchost.exe
672 persfw.exe
760 SCardSvr.exe
768 stisvc.exe
816 MsPMSPSv.exe
828 svchost.exe
928 locator.exe
1148 Explorer.exe
1232 InCD.exe
1200 vsaccess.exe
1060 IEXPLORE.exe
1228 mmc.exe
1380 drwtsn32.exe
0 _Total.exe

+++++++++++++++++++++ end of pasted info ++++++++++++++

note from above info

PID 1232 = Incd
__________________________________________________ ___
Confus-ed posted Quote....
& I just realised you've got INCD running all the time - this is packet writing s/w (makes a cdr type device 'behave' as a hard disk) - for now lets also be rid of this complication, first we want to know if the 'reconnecting bit' is getting done right, never mind buring s/w going 'screwey'..

__________________________________________________ ______
__________________________________________________ ________


Here's today effort from my house

Sun ( AM ) 8/22/04

Condition Prior to Booting PC

*Disc still in CD-RW drive and all cables connected.

MY ACTION:
* Boot up PC
* Push Eject Button on Faceplate of CD-RW while PC is still Booting

RESULTS
* no effect

PC ACTION
PC continues to attempt to Boot To Windows, is dragging it butt badly (slow)

NoTE
* this is a surefire clue that Event ID 9 has began...( I can document this and see in Event Viewer every time it happens)

* after about 9 minutes....the Task Bar (TSR's) are loaded and I'm able to open Event Viewer.
* Click on Unplug/Eject Hardware at Task BAr....no efffect (system Is basicallY hanging)
* Push Eject Button on Face plate...no effect

MY ACTION (reluctantly)
* Unplug Firewire cable only...power still on

RESULTS
* System Springs back to LIFE!!!
* WINDOWS open which were hanging From prior User Input attempts to Unplug/eject FW CD+RW
* Event ID 135 @ 11:14:05am

REF: Event 135 (info)
Received a device interface REMOVAL notification for device:
\\?\SBP2#BUSlink_&CDRW____&LUN0#0006ca0200008189#{ 53f56308-b6bf-11d0-94f2-00a0c91efb8b}

MY ACTION
*Close old windows...(now out of date)
*Push Eject Button on Faceplate... no effect
*Plug In FW cable PUSH Button on Face plate...NO effect
* Check Event Viewer...and now See Event ID 9 starting to accumalate at 10 second intervals
* Mouse click on Task BAR "Unplug/Eject" no effect...no Window or Dialog message boxes
* Wait...be patient...Wait be Patient...no effect

Next ACTION
* Unplug both power and FW cable..

RESULT;
*Event 134 now listed in Event Viewer (time) 11:19:59

REF: Event 134 (info)
Received a device interface ARRIVAL notification for device:
\\?\SBP2#BUSlink_&CDRW____&LUN0#0006ca0200008189#{ 53f56308-b6bf-11d0-94f2-00a0c91efb8b}

Miscellaneous Events while scratching my butt....

I thought it a good time to check email....read Confus-ed feedback... then> thought to do SEARCH for a file or two. no success

RESULTS:
* system boggs down...> So I go to TASK MANAGER to check situation/status

MY ACTION:
*End TASK " Search Application" >> then I notice that I now also have another application open.

INFO
* Somehow the "UNPlug/Eject" Dialog box have opened themselves on the Desktop and appear in Task Manager (App's) as well.....not my doing...but there they are.

THOUGHTS:
* The "UNPlug/Eject" application shown (owned by InCD) in the task bar is believing the CD-RW is still on line.

My ACTIONS:
*Plug in the cables to the CD-RW and pushed the Eject button on the faceplate

RESULTS:
*WALLA...or Hooray or maybe...LA TEE DA....your choice!!! THE CD_RW media has exposed itself!!!

MAJOR CONDITION NOW DIFFERENT

DESCRIPTION:
*CD-RW Drive is Plugged in without a disc....Slide tray is open
*
* A mouse over event above the UNPlug/Eject Hardware Icon creates an hourglass
* two Windows are hanging open as well (UNPlug/Eject which are parent/child group)
* Window TASK MANAGER open window...hanging
* Search Window open...hanging
* Cannot open Event Viewer...due to Event ID 9 now being generated due to CD-RW cables now still plugged in.

MY ACTION:
* Alt+f4...2 or 3 should do and throw in a Cntl+Alt+Del for good measure.
* select "Restart"...after closing door on CD-RW drive....No Disc inside

RESULTS:
* TWO windows HANGING OPEN (unplug/Eject...parent/child group)

* PC slowly shutsdown....slowly, very slowly.

* Reboot begins in Verbose mode...no unusal info....(I always boot this way).

MY THOUGHTS:
* thinking about CONFUS_ED comment....perhaps a Bootlog would furnish some insight about connecting BITS

My ACTION;
* Use F8....select Bootlog option... continue to boot to Windows.
* Repeat F8 select Bootlog option...continue to Boot into Windows

RESULTS:
* both boot-ups are normal; Taskbar is Full of TSR's....(not in SAFEMODE)....but a log is created.

*InCD autofires into action...which is its normal mode of operation

MY ACTION:
* check Event Viewer for status... all good

REF: actual events are: 6oo6, 6009, 6005, 32003, 32003 not a problem to the best of my knowledge.

COMMENTS
* were good to go here.

*options are: put in a new disc or put in an old disc
* My computer sees the CD-RW as a valid drive (empty)

MY ACTION:
*Still need to boot into SAFEMODE...

IDEA:
*Thinking perhaps Dr Watson might could play a roll here as well.

NOTICE ERROR in DR Watson

REF: Application Error c0000005<no symbol>(008d21D)



My ACTION:
* Shutdown/re-boot/F8 with a log file...maybe
* OK, GO, Boot to Safemode...all good
RESULTS:
*eVENT vIEWER... 6006, 7001,6009, 6005, 7001(10 times), 7025, 10010 = good I believe and non applicable to the task at hand .... IMHO

MY ACTION/RESEARCH:
* check system info (winmsd) to view "Running Tasks" do a screen shot, save to WINWORD file for future reference.
* Go to System/device manager > review > all cd-rw,, 1394.. SBP2port device is grayed out and seems fine

INFO:
*Explorer (my computer doesn't see CD-rw drive....which is expected in this condition.

NEXT ACTION:
* re-bOOt TO nORMAL mODE.

cONDITION:
* cd-RW CONNECTED (NO DISC)
* BOOTLOGS NOW AVAILABLE....2 FILES: See me whan ready or request as desired...they add up

to only about 5 pages total... after I trimmed out old infomation.
* No Dr WAtson Logs ...I didn't do this correctly....
*Event Viewer lists are good at (back to 6006, 6009, 6005, 32003, 32003)

++++++++++++ end of my daily log +++++++

Back to Confus-ed.

Perhaps the reconnecting hardware (bits) you mentioned....you could confirm if I post the bootlog files I created?

The only IDE (atapi) device in my PC is a cdrom...All Hard drives are SCSI (only two Seagate 15K

Cheetahs)

I'm guessing you and NooNoo are dialing in on "InCD" as the culprit....being that it's running as a TSR.

Hopefully some of what I just posted is helpful

more later, maybe sooner?

ron_ of_orange
6:00 pm , PST

whew... a long day...

so did you actually unistall INCD?

Quote:

---

Originally Posted by NooNoo

so did you actually unistall INCD?

---

Yes, and it's may be a big mistake.....

Most of yesterday was just more of the same...Event 9....caused as best I can determine by InCD. So I went to Nero Website and downloaded the latest Version of InCD. I also downloaded a CleanInCD tool. Read some of there 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.

So now I have a broken PC.....

I'm going to stop this thread here and open a new forum/subject.

" InCD burns CMOS? "

Of course we can continue here as well I guess if someone has a real good explanation I could use one about now. I hate InCD....

thanks for all responses to date 8/24/2004
++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++

November 20, 2004 addendum

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
Nov, 20, 2004 3:34pm PDT

just wondering. Has this forum answered this question?

"How do you fix the code 10 error when trying to install a firewire IEEE 1394 pci slot?"

I was looking through this thread and got confused.