OS/2 install problems \ VOGONS

OS/2 install problems

Topic actions

First post, by Partaxx

Posted on 2024-06-20, 16:32

Partaxx Offline

Rank Newbie

Rank: Newbie
Posts: 9
Joined: 2024-06-11, 05:21

Hey everyone,

I have this nice little 386SX 25MHz box with 4mb ram. I just went through the painstaking process of getting OS/2 2.0 installed on it, but as soon as it finished and rebooted, it immediately says "c0000005" in the upper left right after the OS/2 splash screen.

From what I can tell from research, this is a buffer overflow error - but I am not finding a lot on how to address this on an old machine like this. Is there some AUTOEXEC or CONFIG magic I need to work to get around this? Is there a problem since I had DOS installed previously? Do I just need more ram? Do I need to start from scratch? The machine meets requirements for the OS as far as I can tell. Not sure where to go from here!

Thank you for any ideas!!

Reply 1 of 7, by darry

Posted on 2024-06-20, 16:42

darry Offline

Rank l33t++

Rank: l33t++
Posts: 6536
Joined: 2014-01-20, 06:27
Location: Canada

You might be hitting this, especially if your VGA card uses a Western Digital chip.

Q. I'm getting a C000005 error during installation and can't continue.
A. The problem results from a conflict with some SVGA cards. There is a replacement BVHSVGA.DLL file available on the IBM NSC BBS (404-835-6600) that allows installation.

Source: https://www.os2world.com/wiki/index.php/OS/2_ … ons_and_Answers

Potential fix:
https://www.os2site.com/sw/drivers/video/misc/bvhsvga.zip

The attachment bvhsvga.zip is no longer available

Reply 2 of 7, by Grzyb

Posted on 2024-06-20, 16:53

Grzyb Offline

Rank l33t

Rank: l33t
Posts: 2480
Joined: 2019-05-08, 13:47
Location: CET-1CEST-2

I recall 8 MB RAM quoted as the minimum - with 4 MB, it may run, but painfully slow.

Kiełbasa smakuje najlepiej, gdy przysmażysz ją laserem!

Reply 3 of 7, by Partaxx

Posted on 2024-06-20, 16:54

Partaxx Offline

Rank Newbie

Rank: Newbie
Posts: 9
Joined: 2024-06-11, 05:21

Darry, you are awesome, I appreciate it! I will try this out and report back.

Reply 4 of 7, by Partaxx

Posted on 2024-06-20, 16:54

Partaxx Offline

Rank Newbie

Rank: Newbie
Posts: 9
Joined: 2024-06-11, 05:21

Grzyb, good to know, thanks for the heads up - I think I will end up upgrading either way!

Reply 5 of 7, by Partaxx

Posted on 2024-06-20, 17:09

Partaxx Offline

Rank Newbie

Rank: Newbie
Posts: 9
Joined: 2024-06-11, 05:21

Darry, that did it!!! Really appreciate the help man! 😁

Reply 6 of 7, by darry

Posted on 2024-06-20, 17:35

darry Offline

Rank l33t++

Rank: l33t++
Posts: 6536
Joined: 2014-01-20, 06:27
Location: Canada

Glad it worked.

I ran either OS/2 2.1 or 3.0 with 5MB of RAM on a 486 SX/25 for a while back in the day.

It swapped a fair amount, but it did work.

Oh, and random advice: do not leave a copy of a DOS executable named mouse.com (typically a mouse driver) in the root of your boot drive. On at least some releases of OS/2, that breaks mouse functionality as OS/2 tries to load that mouse.com instead of its own. AFAICR, this stemmed from c:\ being earlier in the path statement than the expected path. Pretty sure it was the default config, but maybe I was doing something wrong/unexpected.

Reply 7 of 7, by Partaxx

Posted on 2024-06-20, 21:24

Partaxx Offline

Rank Newbie

Rank: Newbie
Posts: 9
Joined: 2024-06-11, 05:21

Lol, good to know! I was surprised that it actually found my old Microsoft Mouse so flawlessly. I feel like Windows is always a pain at first for that.

Honestly, I am pretty impressed with this little OS! Lots of cool things included!

Go to top of page Go to top of page

Back to Software