archmage@cbnewse.att.com (Raistlin Majere) (09/07/90)
I have been having some problems, recently, and have decided to pose my questions to the "collective" mind of the "NET". I am experiencing problems with an AMI 25mhz (no cache) motherboard, yet I am unsure whether the problem is the motherboard itself, or something I may have configured wrong in the CMOS, etc. To start, the board is a baby AT with the Chips and Technologies chip- set. When I received the board, and attempted to configure the CMOS, I found that the manual accompanying the board said to leave the settings for the "clock" stuff alone. It claimed that it was set at the time the system was assembled. Trouble is, I bought the board by itself, and the lithium battery wasn't connected, thus I have *no way* of knowing what the proper settings for the clock on this system are supposed to be! I played with various settings and found that most of them caused the disk drives to lock up at various points (like loading UNIX System V packages). At the third or fourth disk, the system would lock up, the drive light would stay on, and it would just keep spinning. I know that if the clock settings are wrong, it can cause the system to experience sporadic memory problems. Well, after much playing, I came up with the following settings in the CMOS; Processor Oscillator ATCLK SCLK This seemed to cure the "drive lock-up" problem. Here is where I ran in to more problems. I am running AT&T UNIX on the system, and have yet to experience any problems. However, while attempting to run Microsoft Windows 3.0 on my MS-DOS partition, I kept getting a "Parity Error ????" message, followed underneath by "System Halted". I had booted up DOS from my A: drive, I was *not* trying to run it from Simultask (VP/IX) under UNIX. While in "Windows", I would get an error message from Windows when trying to start certain programs, saying "Unrecoverable Application Error", at which point it would randomly kick me back to Windows or, occassionally(sp), straight out of Windows to the "Parity Error ???? System Halted" message. It all appeared to be random, and it didn't happen while trying to run any particular Windows application. The "Parity Error ????" message required me to reboot the system. I have noticed that if I decrease the amount of buffers in my "config. sys" file to a number under 20, this seems to stop the parity message during Windows, and the Windows program seems to run fine. However, if I then exit Windows and attempt to run another program, a game, whatever, I randomly get the parity message and the system lock-up. I also have discovered if I take out the Windows stuff from "config.sys" file ( the HIMEM and SMARTDRIVE lines) and then reboot....all my regular applications seem to work fine, and I get no lockups. This is all very wierd, and I am appealing to anyone else out here who might know anything about this, or who might have encountered any similar problems. The first thing I would like to know is, what should the clock settings for the board be? Do I have mine set right? Is this why I am getting the parity errors? The next thing I would like to know is if anyone knows of problems similar to the ones I encountered with MS-Windows 3.0? I would like to determine whether or not this is a problem with the software of the m-board before I pack the damn thing up and ship it back. The fact that I have had not *one* problem running UNIX, and that my problems have come up under MS-DOS, lead me to believe that it is probably something in the CMOS setup or in the setup of MS-DOS. (Also note that it is *isn't* the SIMMS. I have replaced the SIMMS three times, and the system did it under each new set of SIMMS. I have also made sure that the memory jumpers were set right, and they were.) Also, does anyone have an address or phone number for AMI??? The board is still under warranty and I'd much rather deal directly with AMI. I get this feeling that I'll never see the board again if I send it back to the place I bought it from. Much thanx in advance..................... ------------------------------------------------------------------------------- And these children that you spit on, as the try to change their world, are immune to your consultations. They're quite aware of what they're going through. Ch-Ch-Changes, Turn and face the strange, Ch-Ch-Changes, Don't tell them to grow up and out of it......... -David Bowie ******************************************************************************* Raistlin Majere - Tower of High Sorcery - Palanthas Disclaimer:The views above are my own and not AT&T's or my employers. -------------------------------------------------------------------------------
ucibic@orion.oac.uci.edu (UCI Brain Imaging Center) (09/10/90)
In article <1990Sep6.221657.8744@cbnewse.att.com> archmage@cbnewse.att.com (Raistlin Majere) writes: > > > > I have been having some problems, recently, and have decided to pose > my questions to the "collective" mind of the "NET". Don't have such experience with my ami 386-25 full size board but I do have the numbers for AMI : (404)263-8181 and (800)828-9264. good luck andrew ho
bote@csense.uucp (John Boteler) (09/11/90)
From article <1990Sep6.221657.8744@cbnewse.att.com>, by archmage@cbnewse.att.com (Raistlin Majere): > Well, after much playing, I came up with the following settings in the > CMOS; > > Processor Oscillator ATCLK SCLK Huh? Which one? ATCLK or SCLK. Or SCLK/2, for that matter. The lockup you described under UNIX while accessing the floppy drive smells very familiar to me...I am using a WD1006VSR2. When I run my 25MC system at full speed, accesses to the floppy drive accompanied by hard disk accesses lock the system up cold. At low speed (all three clock settings at their slowest possible) everything works, just slower. Try running it with every clock setting throttled back to the lowest possible setting. > (Also note that it is *isn't* the SIMMS. I have replaced the SIMMS > three times, and the system did it under each new set of SIMMS. I have also > made sure that the memory jumpers were set right, and they were.) It rarely is the memory anymore. These error messages were designed back in 1980 before any of the modern software tricks were implemented. Many times, software or system board configuration troubles will generate the parity error message. I have seen any number of supposedly hardware generated messages being generated in reality by software, for whatever reason. Re: MS Windows 3.0 troubles, ascertain that the motherboard math coprocessor selection jumper is properly set. Mine came shipped from the idiots at WIN Labs who had jumpered it for a 387 and checked the 'OK' box on their paper checklist provided with the system unit! It would not even boot Xenix and gave strange errors under DOS similar to yours. > Also, does anyone have an address or phone number for AMI??? The board > is still under warranty and I'd much rather deal directly with AMI. I get this > feeling that I'll never see the board again if I send it back to the place I > bought it from. Must have been one of those Computer Shopper specials :) I don't know AMI's policy on dealing with end users. I doubt the problem is necessarily something requiring shipment to AMI; save time and diagnose the problem using some of the tips here. -- John Boteler bote@csense.uucp {uunet | ka3ovk}!media!csense!bote SkinnyDipper's Hotline: 703-241-BARE | VOICE only, Touch-Tone(TM) signalling