Re: [GENERAL] Windows Crash
On 26/06/2008 17:43, Ludwig Kniprath wrote: As far as I know pgadmin uses gtk, Correct me if I'm wrong, but I don't think PgAdmin uses gtk on Windows. Ray. -- Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland [EMAIL PROTECTED] Galway Cathedral Recitals: http://www.galwaycathedral.org/recitals -- -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Windows Crash
On Fri, Jun 27, 2008 at 3:37 PM, Raymond O'Donnell [EMAIL PROTECTED] wrote: On 26/06/2008 17:43, Ludwig Kniprath wrote: As far as I know pgadmin uses gtk, Correct me if I'm wrong, but I don't think PgAdmin uses gtk on Windows. No, it most certainly doesn't. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Windows Crash
Hi I'm copying PostgreSQL discussion group in case the following problem involves their efforts. I am running Postgresql 8.3 with Postgis latest version and PGAdmin 1.8.2 on Windows XP. I imported a shapefile using conversion and upload and it installed with no problem. When I viewed the table through PGAdmin and scrolled, Windows crashed with a message that the graphics driver had an error. I downloaded and installed the latest graphics driver and tried to view the table again. This time I used the Select * option and the table opened normally, but when I attempted to scroll, Windows again crashed. This time I got the blue screen with the error message Page_Fault_In_NonPaged_Area. I restarted and again used Select * all and was able to read the table. Very slow scrolling allowed me to read a few rows, some of which had distorted views of the information in the geometriy column. Would anyone have any thoughts - other than to buy new hardware?? Bob -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Windows Crash
MS's web site has a good summary at http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/60 93.mspx?mfr=true . Their bottom line: Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error. If you haven't installed anything else recently or changed any other drivers (and you've tried the same w/your AV turned off), I'd strongly suspect a hardware error. Run a CHKDSK to check the system drive volume and a RAM test to rule out bad RAM (bad RAM would be the first thing I'd check). - Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Pawley Sent: Thursday, June 26, 2008 11:57 AM To: PostGIS Users Discussion Cc: PostgreSQL Subject: [GENERAL] Windows Crash Hi I'm copying PostgreSQL discussion group in case the following problem involves their efforts. I am running Postgresql 8.3 with Postgis latest version and PGAdmin 1.8.2 on Windows XP. I imported a shapefile using conversion and upload and it installed with no problem. When I viewed the table through PGAdmin and scrolled, Windows crashed with a message that the graphics driver had an error. I downloaded and installed the latest graphics driver and tried to view the table again. This time I used the Select * option and the table opened normally, but when I attempted to scroll, Windows again crashed. This time I got the blue screen with the error message Page_Fault_In_NonPaged_Area. I restarted and again used Select * all and was able to read the table. Very slow scrolling allowed me to read a few rows, some of which had distorted views of the information in the geometriy column. Would anyone have any thoughts - other than to buy new hardware?? Bob -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Windows Crash
Hallo Bob, I also use pgDmin on XP with postGIS and imported Shape-Files, but without problems. As far as I know pgadmin uses gtk, and there are some google-hits for searchvalues pgadmin and gtk reporting hardware-crashes on windows and linux Systems. Perhaps the same problem? Ludwig MS's web site has a good summary at http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6 0 93.mspx?mfr=true . Their bottom line: Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error. If you haven't installed anything else recently or changed any other drivers (and you've tried the same w/your AV turned off), I'd strongly suspect a hardware error. Run a CHKDSK to check the system drive volume and a RAM test to rule out bad RAM (bad RAM would be the first thing I'd check). - Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Pawley Sent: Thursday, June 26, 2008 11:57 AM To: PostGIS Users Discussion Cc: PostgreSQL Subject: [GENERAL] Windows Crash Hi I'm copying PostgreSQL discussion group in case the following problem involves their efforts. I am running Postgresql 8.3 with Postgis latest version and PGAdmin 1.8.2 on Windows XP. I imported a shapefile using conversion and upload and it installed with no problem. When I viewed the table through PGAdmin and scrolled, Windows crashed with a message that the graphics driver had an error. I downloaded and installed the latest graphics driver and tried to view the table again. This time I used the Select * option and the table opened normally, but when I attempted to scroll, Windows again crashed. This time I got the blue screen with the error message Page_Fault_In_NonPaged_Area. I restarted and again used Select * all and was able to read the table. Very slow scrolling allowed me to read a few rows, some of which had distorted views of the information in the geometriy column. Would anyone have any thoughts - other than to buy new hardware?? Bob -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
