If it is a Microsoft Crytical Update then it is before 9-11-03
because I have uninstalled updates after that to see if that
helped ... it didn't.
Also after having one of the worst experiences, bar none, calling
Dell-Support, I am finaly going to be sent a new D/Port . The
first "Edited" that I talked to today could not understand me and
persisted in running me through everything known to fix problems...
step by step ... after I put the batteries back into the mobile
phone and it located the base station again, I called and actualy
got a great tech support member, who in a matter of minutes understood
and had me check a couple things in BIOS, and then started to
get info to replace my existing D/Port.
Here's where it got interesting and why I'm posting, the actual
product # for the Inspiron 8500 V/Dock D/Port combo was P/N:2U442
.. what I have, that is not working, is P/N: 2U444 I'm not sure
what the difference is and neither did Rich the support guy and
he is sending me the P/N:2U442, maybe this will do the trick!
Time will tell and I'll keep you posted.
Thanks for your time.
PS. In case you get a bad support guy - it happens - try calling back - there are
good ones out there !!!
Karell, my apologies for braking any rules, I am on several forums as a Moderator and Administrater and sometimes forget what is and is not allowed.
Thanks for your patience.
Message Edited by ShortBusRider on 09-19-2003 12:46 PM
That is a great news and thank you for sharing that.
Please do post when you get your new docking station to let us know if that fixed the problem. I do not plan on speaking to tech support until I am sure that replacing the unit is the solution. So far, I've been with tech support 2 times and about 1 hour once and 2-3 hours on other time. Besids that, spending 1 hour on Repairing OS, doing this and that til 2-3 AM in the morning few times, finally format the dang thing and install everything again which took me entire day, oh and not to mention not being able to work -(
But with your post, I hope all this can go away soon.
Well don't hold your breath , recieved the replacement APR and it did not fix the problem!
Back to square one.
I guess I'll start chasing my tail again, man is this getting on my last nerve!!!
Please post if there is anything new on this.
I'll do the same...
Try the following.
Undock the system.
Remove all external devices, usb, pcmica, and cdrom drives from the system.
Blow away the docking profile.
Redock the system and let it rebuild the docking profile with all the devices
still out of the system.
Turn the system off, and attach one device, then reboot while still docked.
turn the system back off, add the next device and boot up.
Keep doing this until all devices are back in the system.
Does the IRQ conflict still occur?
OK, even though I believe I have already dune this I tried again.
I have tried what you suggested Karell with no change, the minute I Dock the 8500 it imediatetly shows the conflict . There is nothing connected to the APR when I dock it just the power. After trying everything that tech support suggested and what I have read in these forums, I have been told that I have to send my Laptop back to Dell, to replace the motherboard, it is the last resort and I am not verry happy about having to live without my Laptop for 8-10 days. This is a desktop replacement, so I have to live without a computer of my own for that length of time.
I'll post back if anything new occurs
I found the following article and it may help.
Check your Boot.ini for the /Debug entry like the article states.
---------------------------------------------------------------------
SYMPTOMS
When you open Device Manager, one of the COM ports may have a yellow circle and exclamation point next to it, even though the COM port is not in use. The following status message may be displayed on the General tab of the COM port properties:
This device cannot find enough free resources that it can use. (Code 12)
CAUSE
This issue can occur if the /debug switch is appended to an Advanced RISC Computing (ARC) path in the Boot.ini file.
RESOLUTION
To resolve this issue, remove the /debug switch from the ARC path in the Boot.ini file.
STATUS
This behavior is by design.
MORE INFORMATION
Device Manager is reporting that something else is using the resources normally held by com1. This is true because the debugger has exclusive access to this port in order to pipe the debug output.
---------------------------------------------------------------------
Well I am still waiting to get my 8500 back from DELL, who is replacing my motherboard at this time.
If this is the solution could you please either post the link to this other article, or the how to step by step.
If it is as simple as going into msconfig and changing then rebooting or if this is dune in the bios [F8].
What is still confusing me is that the D/Port worked for a couple months before this accured and I'm hoping it is this simple a fix ...
Thanks.
RESOLUTION To resolve this issue, remove the /debug switch from the ARC path in the Boot.ini file. STATUS This behavior is by design.
------------------------------------
Just to make sure before I try this, am I looking for "/debug" in boot.ini and simply erase it? I have not done this before. If I am wrong, please detail me as to what I need to do.
Thank you for getting back to us. I would really like to try this safely.
Find your boot.ini file under the C:\ drive.
Right click on it and choose "Open With".
Choose Notepad and click ok.
Look for any lines that may have the switch /debug...
Do you have such a listing, don't delete it just yet?
If it is listed, what does the complete line state?
I do not see that statement in the ini file. This is what I have.
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
I don't think I can add much to this thread except to say that I have this problem also. I was hoping to see "/debug" in my boot.ini but did not.
My system worked fine while connected to the APR for 6 weeks or so until I noticed just last week that the system no longer detected the CDROM drive when I tried to play a CD.
I don't think this has anything to do with it, but the only "change" I can recall around the time of failure was that I plugged a CF card reader in the side USB port instead of the back port(s).
Well still waiting on the Laptop to get back from DELL , but if you have XP-Pro; go into "START" > "RUN" > type "MSCONFIG" > then choose the "boot.ini" tab > then "advanced Options", you'll find the /debug feature. After looking at this on my desktop Computer,it appear's to be able to be set to "debug" your choice of com ports. I have no Problems with this computer so I can't test to find out if this in fact could help solve the problem. If nothing else, if what Karell is saying is true , if checked uncheck see what happens, if not checked check it and choose the com port in conflict and see if that helps . Man I wish I had my Laptop to test this!
ShortBusRider
23 Posts
0
September 19th, 2003 15:00
because I have uninstalled updates after that to see if that
helped ... it didn't.
Also after having one of the worst experiences, bar none, calling
Dell-Support, I am finaly going to be sent a new D/Port . The
first "Edited" that I talked to today could not understand me and
persisted in running me through everything known to fix problems...
step by step ... after I put the batteries back into the mobile
phone and it located the base station again, I called and actualy
got a great tech support member, who in a matter of minutes understood
and had me check a couple things in BIOS, and then started to
get info to replace my existing D/Port.
Here's where it got interesting and why I'm posting, the actual
product # for the Inspiron 8500 V/Dock D/Port combo was P/N:2U442
.. what I have, that is not working, is P/N: 2U444 I'm not sure
what the difference is and neither did Rich the support guy and
he is sending me the P/N:2U442, maybe this will do the trick!
Time will tell and I'll keep you posted.
Thanks for your time.
PS. In case you get a bad support guy - it happens - try calling back - there are
good ones out there !!!
Karell, my apologies for braking any rules, I am on several forums as a Moderator and Administrater and sometimes forget what is and is not allowed.
Thanks for your patience.
Message Edited by ShortBusRider on 09-19-2003 12:46 PM
nedor
49 Posts
0
September 19th, 2003 16:00
That is a great news and thank you for sharing that.
Please do post when you get your new docking station to let us know if that fixed the problem. I do not plan on speaking to tech support until I am sure that replacing the unit is the solution. So far, I've been with tech support 2 times and about 1 hour once and 2-3 hours on other time. Besids that, spending 1 hour on Repairing OS, doing this and that til 2-3 AM in the morning few times, finally format the dang thing and install everything again which took me entire day, oh and not to mention not being able to work -(
But with your post, I hope all this can go away soon.
Nedor
ShortBusRider
23 Posts
0
September 19th, 2003 19:00
Back to square one.
I guess I'll start chasing my tail again, man is this getting on my last nerve!!!
Please post if there is anything new on this.
I'll do the same...
Karell
2 Intern
•
2.5K Posts
0
September 22nd, 2003 14:00
Try the following.
Undock the system.
Remove all external devices, usb, pcmica, and cdrom drives from the system.
Blow away the docking profile.
Redock the system and let it rebuild the docking profile with all the devices
still out of the system.
Turn the system off, and attach one device, then reboot while still docked.
turn the system back off, add the next device and boot up.
Keep doing this until all devices are back in the system.
Does the IRQ conflict still occur?
ShortBusRider
23 Posts
0
September 22nd, 2003 18:00
I have tried what you suggested Karell with no change, the minute I Dock the 8500 it imediatetly shows the conflict . There is nothing connected to the APR when I dock it just the power. After trying everything that tech support suggested and what I have read in these forums, I have been told that I have to send my Laptop back to Dell, to replace the motherboard, it is the last resort and I am not verry happy about having to live without my Laptop for 8-10 days. This is a desktop replacement, so I have to live without a computer of my own for that length of time.
I'll post back if anything new occurs
nedor
49 Posts
0
September 22nd, 2003 19:00
Sigh,
Big bummer. When will this nightmare end? If replacement does not work, where is the problem coming from?
Nedor
nedor
49 Posts
0
October 6th, 2003 02:00
Has the problem taken care of? I am having the same problem and not getting any where with Dell.
Dell, please advise me what to do. I've done everything I was told to do except exchange and by the looks of it, it won't help..
Nedor
Karell
2 Intern
•
2.5K Posts
0
October 6th, 2003 13:00
I found the following article and it may help.
Check your Boot.ini for the /Debug entry like the article states.
---------------------------------------------------------------------
SYMPTOMS
When you open Device Manager, one of the COM ports may have a yellow circle and exclamation point next to it, even though the COM port is not in use. The following status message may be displayed on the General tab of the COM port properties:
This device cannot find enough free resources that it can use. (Code 12)
CAUSE
This issue can occur if the /debug switch is appended to an Advanced RISC Computing (ARC) path in the Boot.ini file.
RESOLUTION
To resolve this issue, remove the /debug switch from the ARC path in the Boot.ini file.
STATUS
This behavior is by design.
MORE INFORMATION
Device Manager is reporting that something else is using the resources normally held by com1. This is true because the debugger has exclusive access to this port in order to pipe the debug output.
---------------------------------------------------------------------
ShortBusRider
23 Posts
0
October 6th, 2003 15:00
If this is the solution could you please either post the link to this other article, or the how to step by step.
If it is as simple as going into msconfig and changing then rebooting or if this is dune in the bios [F8].
What is still confusing me is that the D/Port worked for a couple months before this accured and I'm hoping it is this simple a fix ...
Thanks.
nedor
49 Posts
0
October 7th, 2003 02:00
RESOLUTION
To resolve this issue, remove the /debug switch from the ARC path in the Boot.ini file.
STATUS
This behavior is by design.
------------------------------------
Just to make sure before I try this, am I looking for "/debug" in boot.ini and simply erase it? I have not done this before. If I am wrong, please detail me as to what I need to do.
Thank you for getting back to us. I would really like to try this safely.
Nedor
Karell
2 Intern
•
2.5K Posts
0
October 7th, 2003 17:00
Find your boot.ini file under the C:\ drive.
Right click on it and choose "Open With".
Choose Notepad and click ok.
Look for any lines that may have the switch /debug...
Do you have such a listing, don't delete it just yet?
If it is listed, what does the complete line state?
nedor
49 Posts
0
October 7th, 2003 20:00
Karell,
I do not see that statement in the ini file. This is what I have.
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect
Nedor
davidstx
2 Posts
0
October 8th, 2003 14:00
I don't think I can add much to this thread except to say that I have this problem also. I was hoping to see "/debug" in my boot.ini but did not.
My system worked fine while connected to the APR for 6 weeks or so until I noticed just last week that the system no longer detected the CDROM drive when I tried to play a CD.
I don't think this has anything to do with it, but the only "change" I can recall around the time of failure was that I plugged a CF card reader in the side USB port instead of the back port(s).
ShortBusRider
23 Posts
0
October 8th, 2003 21:00
Diether
14 Posts
0
October 11th, 2003 09:00
Hello,
Im having the same issue here , but with a dell inspiron 8600
when docked , the Second IDE controller ( & the CDROM ) doesnt work anymore as it says the IRQ15 is used by the COM1.
Changing the configuration of the COM1 manually to another IRQ (4) doesnt help.
Removing the devices and retrying doesnt help
When undocked , everything works fine. ( & COM1 uses IRQ 4)
I hope that dell fixes this soon. ( I also have no /debug option in my boot.ini )
Dell , can we get an answer please ?
Diether