anderson@vms.macc.wisc.edu (Jess Anderson) (11/16/89)
I'm having a problem with Windows 386. I have a new machine, Club American 333C (AMI Bios) with a Sigma Laserview 19" monitor and an MSC PC Mouse II. First problem: during Win386 setup, my machine is not listed on the machine options, so I chose Compaq. Installing screen drivers is a bit of a complex deal, but Sigma provides an instruction sheet and a disk with the Windows/386 drivers etc on it. I install the mouse drivers in the prescribed fashion. I'm configured the right way, I think. The behavior is this. I get in directory WIN386. I start the thing by typing WIN386. The cursor goes down one line, about a half second passes, and the screen in cleared and I'm back at the DOS prompt (not very useful, eh?). I called Microsoft (it's Windows 386, v. 2.11); no help there (nice person, but no help). I called Sigma, they tell me I have the latest version of their stuff (the monitor is brand new). I called Club American, where so far nobody has gotten back to me (maybe they're looking into it). Any suggestions? (By now, I don't even swear at the way Windows installation has to be done anymore.) I'm up for anything. Because I *have* to have Windows up to do my job, I installed Windows 286 too, and that works fine. ==Jess Anderson===Academic Computing Center=====Univ. Wisconsin-Madison===== | Work: Rm. 2160, 1210 West Dayton St., Madison WI 53706, Ph. 608/263-6988 | | Home: 2838 Stevens St., 53705, 608/238-4833 Bitnet: anderson@wiscmacc | ==Internet: anderson@macc.wisc.edu====UUCP:{}!uwvax!macc.wisc.edu!anderson==
don.roy@canremote.uucp (DON ROY) (11/21/89)
Jess - you may find that the Version of the AMI BIOS used in your computer is not compatible with Windows/386. The following may be of some help: AMI BIOS shows a 16-digit identification number near the bottom of the screen when the machine is warm- or cold-booted. The following is an example ID number: . DAMI 3601 092588 K8 . The first character is a "D" if the BIOS includes advanced diagnostic routines built into the CMOS RAM setup program of the BIOS. The next three characters indicate the type of motherboard in which the BIOS is installed (e.g. "AMI" for an AMI motherboard, "CNT" for a Chips and Technology motherboard). . The next four digits are the license code of the manufacturer of the motherboard and/or computer for which the BIOS is supplied (e.g. Code 3601 is a Mylex motherboard). . The next six digits are the date code (AMI uses a date code rather than a version number to identify its BIOS versions). This date code is in an "mmddyy" format (e.g. 092588 for September 25, 1988). The latest GENUINE AMI date code in use as of 5/16/89 is 033089. . The last four digits comprise the keyboard-controller identification number, which is K0 for a non-AMI keyboard controller or K1 through K8 for an AMI keyboard-controller version number. The latest keyboard controller version is K8. Version K7 definitely causes problems with Windows and/or network software and should be upgraded. An Identification Number of K0 indicates a non-AMI keyboard controller which may not work properly. . To obtain an upgrade to an AMI BIOS, contact the manufacturer of your computer system or motherboard. If you need assistance in determining the correct firm to contact for the upgrade, call American Megatrends at (404) 263-8181. This is information provided by Microsoft. Hope it helps. Rgds...DON --- * Via ProDoor 3.1R
claude.vidal@canremote.uucp (CLAUDE VIDAL) (11/27/89)
//]I'm having a problem with Windows 386. I have a //]new machine, Club American 333C (AMI Bios) with //]a Sigma Laserview 19" monitor and an MSC PC Mouse II. //] //]I'm configured the right way, I think. The behavior //]is this. I get in directory WIN386. I start the //]thing by typing WIN386. The cursor goes down one //]line, about a half second passes, and the screen //]in cleared and I'm back at the DOS prompt (not very //]useful, eh?). Can't give you that bottom line answer, but at least some thoughts... I believe the first thing WIN386.EXE does is have its LIM EMS manager do its thing (assessing how many K's of EMS, initializing, setting vectors, etc.); all this occurs before you even see the (blue) title screen. So chances are you're bombing out during that process; the 286 version doesn't have that 'EMS manager' front end, as far as I know, which would explain how it runs on your system. Suggest you check for EMS drivers in your config.sys: Windows is not sociable with other EMS managers. I presume you're not running under another protected mode piece of software. How did you respond to the memory configuration part during Windows/386 installation? --- ~ EZ-Reader 1.21 ~ Windows/386...faut l'faire! * QNet 1.04a1: DAT-A-REA - St-Bruno,Quebec (514)441-3229