more Code 10..Firewire device

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.