View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000416 | PicoCOM2 | Kernel | public | 2010-10-22 14:56 | 2010-10-27 07:55 |
| Reporter | Assigned To | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Product Version | unspecified | ||||
| Target Version | unspecified | ||||
| Summary | 0000416: CMD files in startup directory sometimes will not be started | ||||
| Description | I have already heared about such problems by some customers. It looks like that the command shell hangs in this case. The script will not be executed correctly and it will not be possible to open another command shell afterwords. It seems to occure on PicoCOM2 only. | ||||
| Forum Link | |||||
| Found Driver Version | |||||
| Fixed Driver Version | |||||
|
|
Created a small startup applciation that replaces this functionailty and also includes some benefits. More information are available at http://forum.fs-net.de/viewtopic.php?f=3&t=2690 Tool not tested yet. Maybe there is the same problem. |
