warpcafe (03 Apr, 2006 15:0:
although I'm glad to see the problems solved... I still am not sure about what the cause was. Was it some kind of "configuration mess" or what? It leaves me with some dull feeling of being still somehow "helpless"...
Never mind anyway. Greetings
I wonder if...
I'll take a guess on a possible cause:
On an eCS1.2R (or is it MR?) system that had been "migrated" from eCS1.1 USB seemed to be working fine, mouse printer and cardreader all working.
Then I attached a USB scanner which is working fine on 2 almost identical systems and tried to scan using Tame/2 - Yes, Tame is setup fine.
The result of trying to scan was a complete system lockup requiring a press of the Reset button.
Knowing that the USB drivers were up to date, setup as correctly as possible and that Tame should work with the Canon LiDE20 scanner - does on 2 other 1.2R systems here - I started looking for a "culprit"...
As an aside: This "investigative behaviour" is probably a result of developing the USBcfg app - I am trying to collate odd bits of USB setup data and problem resolution into an FAQ for addition to the Help file at some point. End aside.
As usbresmg.sys is also present on the system I had not installed the Tame/2 supplied version and realised that I had not checked what version was present - took it for granted that a migrate install would automatically install a later version.
Checking [BootDrive]:\ecs\boot\usbresmg.sys against versions installed on the 2 other systems and against the version supplied with Tame/2 (same as eCS) revealed that the migrate install had *Not* updated that file.
Updating to the current version resolved the issue.
I suspect that the problem experienced by Bobber could well be the same as the above: especially as a fresh install seems to have "cured" it.