Thread View: alt.msdos.programmer
4 messages
4 total messages
Started by Duane Morin
Wed, 06 Jan 1993 21:47
"GP" Errors with BC 3.1
Author: Duane Morin
Date: Wed, 06 Jan 1993 21:47
Date: Wed, 06 Jan 1993 21:47
51 lines
2998 bytes
2998 bytes
Perhaps someone recognizes this problem. My BC compile, which used to work just dandy, now randomly crashes with "FATAL ERROR: GP fault" or somesuch similar message. Not always on the same file, and not necessarily occurring at all, although it pretty regularly comes up at least once every batch. Once it even went as far as dumping all my registers to the screen and telling me "Press [T] to terminate, but you should reboot as soon as possible as the system has become unstable..." I liked that one. Not. Here's a quick chronology of what's changed: Original - 386/40, 8meg ram (100ns), BC 2.0 Works fine. 1) Changed to a 486 (re: problem calculating logs, for those that remember THAT post). Brought the SIMMs and hard drives over from the 386. Ok. Start to see lots of "GP errors". These crash BC (note, 2.0) completely, hanging most of my memory and requiring a reboot. ADVICE FROM BORLAND: Oh, 2.0 is too old, get 3.1. 2) Got 3.1. Can't even install the damn thing. ZIPs are intermittently corrupted. Little examination shows that, with cache memory off, I have no problem unzipping, with it on, sometimes they get CRC errors. Suggestion from my tech: 100ns memory is probably too slow for the new machine. Get some 70ns SIMMs and try it. Interim solution: Running w/ cache turned off. Problem not occurring. 3) Got 70ns SIMMs. Same problem as before. If anything, now more rampant than before. 4) Changed motherboards. Problem persists. Now, I realize that I can't relay all important information about my system in this post. I'm just hoping that maybe someone recognizes this problem and can point me in the right direction. Borland offers little help, even calling their wonderful 900 number gets me a customer service robot who tells me (note, every time I call he tells me this): Set up a virgin boot, kill your config sys and your autoexec, go into borland directory slash bin, run dpmi inst, you'll get a message saying machine is in the database, it should work, if not please send us the offending file. I keep telling them that it's not necessarily the same file every time. At least one of their guys didn't even believe me when I said "Did that. Still happens." Can anybody help with this problem? Please email responses, as my newsfeed has been flakey lately and I'd like to get the information as quickly as possible. Thank you. Thanks in advance, Duane Morin Software Development Manager Walker Sonix, Inc Worcester, MA 01604
Re: "GP" Errors with BC 3.1
Author: BOGGS RICHARD GRAN
Date: Thu, 07 Jan 1993 07:02
Date: Thu, 07 Jan 1993 07:02
23 lines
1587 bytes
1587 bytes
In article <1993Jan6.214710.26976@schunix.uucp> sonix@schunix.uucp (Duane Morin) writes: >Perhaps someone recognizes this problem. My BC compile, which used to work >just dandy, now randomly crashes with "FATAL ERROR: GP fault" or somesuch >similar message. Not always on the same file, and not necessarily occurring I've encountered the same problem with BC++ 3.1 IDE version. I was rather confused since BC++ 3.0 worked just fine with the same program. The tech guys at Borland told me that BC++ 3.1 barfs on some compile-time errors. The tech I spoke to recommended running prj2mak to convert the .prj file to a make file and use the commandline version bcc.exe instead. Turns out he was right. The commandline compiler gave me some error messages before bombing out with a GP Fault. I fixed the errors in the source, and it works just peachy. Odd that 3.0 doesn't do that... Try running the commandline version and see if that gets any farther during the compile process. Worked for me. -- Grant Boggs boggs@a.cs.okstate.edu Oklahoma State University Stillwater, Oklahoma
Re: "GP" Errors with BC 3.1
Author: Chuck Harris - WA3UQV
Date: Thu, 07 Jan 1993 20:11
Date: Thu, 07 Jan 1993 20:11
37 lines
2497 bytes
2497 bytes
In article <1993Jan6.214710.26976@schunix.uucp> sonix@schunix.uucp (Duane Morin) writes: ... Stuff about GP errors deleted ... >2) Got 3.1. Can't even install the damn thing. ZIPs are intermittently > corrupted. Little examination shows that, with cache memory off, > I have no problem unzipping, with it on, sometimes they get CRC This is fair proof that your motherboard is not functioning in a happy way. 486 motherboards are often very sensitive to the 5volt power supply voltage. If the 5volt supply is running at the low end of tolerance, the cache controller chips might not be able to function quickly enough. Check to see that you have 5.00volts -0%, +5% on the motherboard's power connector (red and black leads), when you have all of your system's cards/disks installed. If you aren't getting 5.00volts you should either adjust your supply (HA HA HA, good luck!) or get a new supply that does give you 5.00volts. You wouldn't have this problem if the motherboard suppliers wouldn't cheat. What they do is buy all 25MHz 486 motherboards, without CPU or RAM. They then plug in the proper speed parts to get either 33MHz or 50MHz. Well, this would work, except that the motherboard manufacturer's grade the motherboards for speed. The ones that fail 50MHz become 33MHz boards, the ones that fail 33MHz become 25MHz... Now, you ask, "Why does the board work sometimes on my system?" Well, It's like this, the boards are designed to run at 5v +/- 5%, and from 0-70degrees C. Logic chips such as the cache controller run their fastest when they are cold and at the high voltage margin, and at their slowest when they are hot, and at their low voltage margin. Most of the time, the power supplies will provide 5.0v on the nose, and you all will run your machines in comfortable rooms, so you can get away with using parts that failed to run full speed at 4.75v and 70C. The clone builders are banking on this happy coincedence. Chuck Harris - WA3UQV chuck@eng.umd.edu
Re: "GP" Errors with BC 3.1
Author: Brian C. Anderson
Date: Fri, 08 Jan 1993 15:11
Date: Fri, 08 Jan 1993 15:11
41 lines
2896 bytes
2896 bytes
|> |> In article <1993Jan6.214710.26976@schunix.uucp> sonix@schunix.uucp (Duane Morin) writes: |> ... Stuff about GP errors deleted ... |> >2) Got 3.1. Can't even install the damn thing. ZIPs are intermittently |> > corrupted. Little examination shows that, with cache memory off, |> > I have no problem unzipping, with it on, sometimes they get CRC |> |> This is fair proof that your motherboard is not functioning in a happy way. |> 486 motherboards are often very sensitive to the 5volt power supply voltage. |> If the 5volt supply is running at the low end of tolerance, the cache |> controller chips might not be able to function quickly enough. |> |> Check to see that you have 5.00volts -0%, +5% on the motherboard's power |> connector (red and black leads), when you have all of your system's |> cards/disks installed. If you aren't getting 5.00volts you should either |> adjust your supply (HA HA HA, good luck!) or get a new supply that does |> give you 5.00volts. |> |> You wouldn't have this problem if the motherboard suppliers wouldn't cheat. |> What they do is buy all 25MHz 486 motherboards, without CPU or RAM. They then |> plug in the proper speed parts to get either 33MHz or 50MHz. Well, this would |> work, except that the motherboard manufacturer's grade the motherboards for |> speed. The ones that fail 50MHz become 33MHz boards, the ones that fail |> 33MHz become 25MHz... |> |> Now, you ask, "Why does the board work sometimes on my system?" |> |> Well, It's like this, the boards are designed to run at 5v +/- 5%, and from |> 0-70degrees C. Logic chips such as the cache controller run their fastest |> when they are cold and at the high voltage margin, and at their slowest when |> they are hot, and at their low voltage margin. Most of the time, the power |> supplies will provide 5.0v on the nose, and you all will run your machines |> in comfortable rooms, so you can get away with using parts that failed to |> run full speed at 4.75v and 70C. The clone builders are banking on this |> happy coincedence. |> |> Chuck Harris - WA3UQV |> chuck@eng.umd.edu |> |>
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads