Custom Query (15 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (7 - 9 of 15)

1 2 3 4 5
Ticket Resolution Summary Owner Reporter
#1 NoChangeNeeded Test Ticket David Alexander
Description

This is a test ticket

#16 duplicate System crash when calling "full screen command line" dirk
Description

Dear Sirs, I'm testing the available eCS2.2 BETA II, which has included the Panorama 1.06. We are running HP Elite 8300 machines.

I'm getting crashes in form of a coloured sprangled Monitor together with the system completely hung. It's only possible to switch off power with the system.

The crash is reproducible. It appears, when I switch very soon (within 5 seconds) after booting to an eCS full command prompt. It doesn't appear, if you give the system more time after booting. It also can be avoided, if PSD=ACPI.PSD /MAXCPU=1 is used.

I reported this already last year in the eCS bugtracker (ticket: 0003501), where Mr. Roderick Klein asked me to wait for the Panorama Version 1.06. But this error is NOT eliminated with this 1.06.

As a workaround I'm forced to use the MAXCPU=1 solution, as my machines have to run certain scripts and programs in fullscreen mode!

With kind regards Dirk

#17 fixed System crash when calling "full screen command line" dirk
Description

Dear Sirs, I'm testing the available eCS2.2 BETA II, which has included the Panorama 1.06. We are running HP Elite 8300 machines.

I'm getting crashes in form of a coloured sprangled Monitor together with the system completely hung. It's only possible to switch off power with the system.

The crash is reproducible. It appears, when I switch very soon (within 5 seconds) after booting to an eCS full command prompt. It doesn't appear, if you give the system more time after booting. It also can be avoided, if PSD=ACPI.PSD /MAXCPU=1 is used.

I reported this already last year in the eCS bugtracker (ticket: 0003501), where Mr. Roderick Klein asked me to wait for the Panorama Version 1.06. But this error is NOT eliminated with this 1.06.

As a workaround I'm forced to use the MAXCPU=1 solution, as my machines have to run certain scripts and programs in fullscreen mode!

With kind regards Dirk

1 2 3 4 5
Note: See TracQuery for help on using queries.