If the graphics card is using shared memory, you may want to check the
quality of your system RAM. There is high traffic on shared memory when
scrolling large bitmaps in video ram which can reveal faults in
otherwise dependable ram chips.
Good luck.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
Pawley
Sent: Thursday, June 26, 2008 3:40 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] Windows Crash
Having spent the day looking at my problem it appears to be a
fault in the Intel graphic driver. Word has it that long text lengths
(the shapefiles I downloaded fit that description) apparently causes a
fault in the driver.
So there doesn't seem to be any problem with Postgis except,
perhaps, verbosity.
Thanlks for the help.
Bob
----- Original Message -----
From: Obe, Regina <mailto:[EMAIL PROTECTED]>
To: PostGIS Users Discussion
<mailto:[email protected]>
Sent: Thursday, June 26, 2008 1:29 PM
Subject: RE: [postgis-users] Windows Crash
Slightly off topic. Has anyone seen this Linux Haters
Blog. All Linux users should read it to understand how the mind of a
windows user works so that we can interoperate.
http://linuxhaters.blogspot.com/
Similarly I would like to see a windows haters blog so I
can form a fully unbiased opinion of the various factions. Is there
such a thing?
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Bruce Rindahl
Sent: Thursday, June 26, 2008 3:53 PM
To: PostGIS Users Discussion
Subject: Re: [postgis-users] Windows Crash
Also on a long shot - do you have any hardware
conflicts?
Start->Control Panel->System->Hardware->Device Manager
Are there any little yellow info symbols?
Bruce
Paul Ramsey wrote:
This is in no way a PostGIS problem, certainly
nothing we can ever
fix, just something that the particular
combination of PgAdmin, the
geometry we are feeding it, and the way the
Windows rendering system
are interacting.
My experience has been that these days the thing
that causes a modern
operating system (Windows, Linux, whatever) to
crash is bad hardware,
usually bad memory, but sometimes other things.
Basically, the
operating system itself is usually rock solid
until you shake the
foundations it sits on, the hardware.
So basically, all I can offer is the doctor's
advice to the patient
who said "doctor, doctor, it hurts when I raise
my arm over my
head!"... "don't raise your arm over your head".
In the meantime, if you want to fiddle with
things, swapping the order
of your memory in the sockets, changing out the
video card, even
changing your screen resolution, might change
the interaction such
that you can exercise this particular use case
without dropping your
OS to the floor.
P.
On Thu, Jun 26, 2008 at 10:31 AM, Obe, Regina
<[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> wrote:
I second Bruce's comment about unhelpful
comments.
It may actually have nothing to do with
Windows in fact.
Now getting back to the crash issue.
Bob if you are still having the same
issue with that file, maybe you can post
that (or provide a link to the
shape file you loaded). It could be
something to do with the shapefile.
I recall having this same issue with one
particular geometry file way back
in PgAdmin 1.6 and it was when I
scrolled to a specific record it would
crash, but then later additions (I
either maybe never selected the geometry
field again) or it was fixed in later
versions. Doing an AsText
always seemed to work where as
displaying the raw binary was where I ran
into issues.
The other possibility is that it could
be a defective graphics card. I
forget which video cards I had bad runs
with, but I remember having this
same exact issue with my favorite
programming editor JEdit. I had 2
identical computers with same drivers
etc and for some reason I would get
intermittent crashes on one of them. I
finally just got fed up and replaced
the graphics card and then it worked
fine.
Just some thoughts.
Thanks,
Regina
________________________________
The substance of this message, including
any attachments, may be
confidential, legally privileged and/or
exempt from disclosure pursuant to
Massachusetts law. It is intended solely
for the addressee. If you received
this in error, please contact the sender
and delete the material from any
computer.
________________________________
Help make the earth a greener place. If
at all possible resist printing this
email and join us in saving paper.
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
________________________________
The substance of this message, including any
attachments, may be confidential, legally privileged and/or exempt from
disclosure pursuant to Massachusetts law. It is intended solely for the
addressee. If you received this in error, please contact the sender and
delete the material from any computer.
________________________________
Help make the earth a greener place. If at all possible
resist printing this email and join us in saving paper.
________________________________
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
[email protected]
http://postgis.refractions.net/mailman/listinfo/postgis-users
