PRINT SELECTION FOR APAR - II06139 92/07/14 APAR= II06139 SER= DD DOC INFO APAR - OS/2 2.0 PROBLEMS RUNNING ON GATEWAY PC ( OS2INFOAPAR 2.0 R200 56107701 GATEWAY ) STAT= INTRAN FESN5NFO000-000 CTID= II0000 ISEV= 4 SB92/06/25 RC CL PD SEV= 4 PE= TYPE= I RCOMP= INFOPCLIB PC LIB INFO ITE RREL= R001 FCOMP= PFREL= F TREL= T ACTION= SEC/INT= DUP/ USPTF= PDPTF= DUPS 0 DW92/06/25 RT SC FT RE PT UP LP PV AP EN FL LC92/06/26 RU92/06/25 MCEASPSA CUST INST LVL/SU= FAILING MODULE= FAILING LVL/SU= SYSROUTE OF: RET APAR= PS= COMP OPER ENV= SYSRES= SYSIN= SYSOUT= CPU= RE-IPL= OPTYPE= SPECIAL ACTIVITY= REGRESSION= PRE-SCREEN NO.= RSCP= RS000 ERROR DESCRIPTION: Subject: OS/2 2.0 on Gateway 2000 machines - Here is an "official list" on what are known problems to look out for on Gateway 2000 machines. - Problem 1 - Country.Sys not found message on all Nomad "notebook" models. This is a problem with the BIOS on the Nomad machines according to Bill Williams. Nomad machines with Pheonix 1.02 BIOS will need to be upgraded. The Gateway 2000 Tech support group expects us to send the customer over to them on this problem. - Problem 2 - Gateway machines with a 486 can potential have DIVIDE UNDERFLOW errors. This problem is a bug on the 486 math coprocessor and will only be seen if the customer is running software that takes advantage of the coprocessor. The Rev E mother boards of 486 Gateway machines may exhibit this problem. If the customer is running into this problem we can send them to Gateway so they can upgrade to the Rev F version of the mother board. The Rev F board has a HW fix workaround for the coprocessor bug. - Problem 3 - Gateway machines that Trap 2 on boot or install This problem could be one of two things. The first is that the Read Ahead Cache on the mother board could be bad. Gateway has seen several cases of this. The workaround for this problem is to disable the external caching. This can be done by hitting Ctl-Alt-Esc during POST to activate CMOS Setup. The real solution however would be to get another board from Gateway or let them fix the one the customer has. The second thing that could cause the Trap 2 is bad memory. In this case the only thing that will consistently fix the problem is locating the memory sim that is bad and replacing it. Sometimes - just moving the sims around helps though. - For either of the versions of the Trap 2 problems it is also okay to refer them to Gateway. - Problem 4 - Machine hangs or screen goes blank when user goes into a DOS session on Gateway 386 machines. Here we have the TSENG video chip set problem. Most all of Gateway's 386 line has been shipped with the Diamond Speedstar video card that uses the TSENG chip set. Here Gateway asks that we work with the customer to try the VSVGA.SYS fix for the problem. They have the the fix module for this problem at Gateway and are helping customers that call there first without sending them to us. Bill Williams thinks that we can do the same here since it is not a problem specific to Gateway 2000 machines. LOCAL FIX: