Hello,
in our production line we're using Bit 8.1 (build 1015) via Windows PE 5.1.
The Burinintest directory is stored at a network share.
All Clients are accessing the same Bit.exe from this share.
Now we have often sporadically errors with the COM Ports.
The strange thing here is:
When trying with 1 client alone, everything works fine and as expected.
When trying with 50 clients, we had about 30 systems failing the test. (COM3 or COM4, hanging at 300 operations, saying we should check that the plug is connected.)
We've checked the system with an old WindowsPE USB-stick and local burnintest. -> all fine. No Hardware errors.
Important to say:
While Burinintest is starting, were using the "Executewait" command to load a "load.cmd".
This batchfile is reloading via "drvload" the msports.inf serialport driver. (This should prevent this COM errors)
The question is: Is BIT.exe limitated to a max number of clients accessing at same time? / Is there a special workaround for the comports?
Cause this error only occurs when we're testing 30-50 systems.
Ive tried making high networkload and only using one client, but i could not get the errors again.
So atm, i only get these errors with a bunch of clients.
Any ideas?
in our production line we're using Bit 8.1 (build 1015) via Windows PE 5.1.
The Burinintest directory is stored at a network share.
All Clients are accessing the same Bit.exe from this share.
Now we have often sporadically errors with the COM Ports.
The strange thing here is:
When trying with 1 client alone, everything works fine and as expected.
When trying with 50 clients, we had about 30 systems failing the test. (COM3 or COM4, hanging at 300 operations, saying we should check that the plug is connected.)
We've checked the system with an old WindowsPE USB-stick and local burnintest. -> all fine. No Hardware errors.
Important to say:
While Burinintest is starting, were using the "Executewait" command to load a "load.cmd".
This batchfile is reloading via "drvload" the msports.inf serialport driver. (This should prevent this COM errors)
The question is: Is BIT.exe limitated to a max number of clients accessing at same time? / Is there a special workaround for the comports?
Cause this error only occurs when we're testing 30-50 systems.
Ive tried making high networkload and only using one client, but i could not get the errors again.
So atm, i only get these errors with a bunch of clients.
Any ideas?
Comment