Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+RE\:\s+User\s+Port\s+appears\s+to\s+have\s+destroyed\s+aDellInsprion8100\s*$/: 3 ]

Total 3 documents matching your query.

1. [WriteLog] RE: User Port appears to have destroyed aDellInsprion8100 (score: 1)
Author: ve3gsi@sympatico.ca (Eric - VE3GSI)
Date: Tue May 27 18:16:55 2003
Hi Gang, I also am thinking it is not a S/W problem, unless someone could logically explain otherwise. Perhaps RFI or Ground Loop? In these cases, I am sure nobody 'hot plugged' devices with either t
/archives//html/WriteLog/2003-05/msg00185.html (8,334 bytes)

2. [WriteLog] RE: User Port appears to have destroyed aDellInsprion8100 (score: 1)
Author: dick.green@VALLEY.NET (Dick Green)
Date: Wed May 28 12:34:48 2003
I think it may be possible for a bad combination of software and cable/device to burn out a parallel port. For example, if the UserPort software happens to hold a particular parallel port output sign
/archives//html/WriteLog/2003-05/msg00212.html (13,299 bytes)

3. [WriteLog] RE: User Port appears to have destroyed aDellInsprion8100 (score: 1)
Author: n3hs@qsl.net (Stan Staten)
Date: Sat May 31 13:46:15 2003
I am used to the problem that if there is too much load (i.e. too low of a resistance) on a TTL circuit that it simply loads it down and the signal levels decrease, eventually to the point where they
/archives//html/WriteLog/2003-05/msg00238.html (10,177 bytes)


This search system is powered by Namazu