PGADMIN2 caused an invalid page fault

Ever since upgrading from PostgreSQL 7.2 and pgAdmin 1.2, I get one of
those "This program has performed an illegal operation and will be shut
down" errors when attempting to connect, after entering my username and
password. I need help with a work around or news that this is a problem
the programmers are working on. The Windows error dialog Details window
reads:

PGADMIN2 caused an invalid page fault in
module <unknown> at 0000:20302e38.
Registers:
EAX=008b0000 CS=017f EIP=20302e38 EFLGS=00010202
EBX=00000000 SS=0187 ESP=008be30c EBP=008be340
ECX=0000008a DS=0187 ESI=03ad4240 FS=129f
EDX=bffc9490 ES=0187 EDI=03ad6d04 GS=0000
Bytes at CS:EIP:

Stack dump:
008be3e0 031b08ac 00000000 1f70bcdc 03ad4240 00000012 00000000 00000000
008be3e0 00000000 031b08ac 00000012 00000000 008be3a8 1f701250 032afd74



I'm running:

pgAdminII version 1.4.12
psqlodbc-07_02_0005
Windows 98SE client
PostgreSQL version 7.3
Redhat Linux 7.3


Please don't shoot me if this is a common question that's already been
answered numerous time. Just point me in the right direction. I've done
searchs on Google and PostgreSQL sites for relevant topics and got no
close hits. I've tried some of the standard MS-debugging tricks like
deleting all my *.pwl files, for instance. This error occurs identically
on three different computers, two on the local subnet, one from outside,
and as mentioned above began only AFTER upgrading to new versions of
PostgreSQL and pgAdminII. I need (or, at least, was interested in) the new
versions because of the ability to run stored procedures with owner
privileges.

I CAN connect at the Linux console using psql, and also using a generic,
Windows-based ODBC query-builder program (which uses ODBC and the Borland
Database Engine), as well as with the application I'm working on, but I
rely on pgAdminII to work with the database.


Regards,
Berend Tober