Author Topic: PCL Win32 System Exception  (Read 2997 times)

Offline lage

  • Newcomer
  • Posts: 22
PCL Win32 System Exception
« on: 2017 March 30 13:53:14 »
See attachments.

Offline Niall Saunders

  • PTeam Member
  • PixInsight Jedi Knight
  • *****
  • Posts: 1456
  • We have cookies? Where ?
Re: PCL Win32 System Exception
« Reply #1 on: 2017 March 30 16:04:21 »
Can you provide further information?
Cheers,
Niall Saunders
Clinterty Observatories
Aberdeen, UK

Altair Astro GSO 10" f/8 Ritchey Chrétien CF OTA on EQ8 mount with homebrew 3D Balance and Pier
Moonfish ED80 APO & Celestron Omni XLT 120
QHY10 CCD & QHY5L-II Colour
9mm TS-OAG and Meade DSI-IIC

Offline lage

  • Newcomer
  • Posts: 22
Re: PCL Win32 System Exception
« Reply #2 on: 2017 March 30 16:29:26 »
sure, what kind of info is relevant?

Offline Niall Saunders

  • PTeam Member
  • PixInsight Jedi Knight
  • *****
  • Posts: 1456
  • We have cookies? Where ?
Re: PCL Win32 System Exception
« Reply #3 on: 2017 March 30 16:39:47 »
What are/were you doing, or trying to do, when the error message(s) were displayed?

Have you described the issues elsewhere? Is this a follow-up post, and so readers of this thread are only seeing part of the story?

Are you aware that PixInsight no longer supports 32-bit operating system environments - is that perhaps causing the problem?

If you need help, there are plenty of PixInsight users here who are willing to help, but we do need as much information as you can provide!
Cheers,
Niall Saunders
Clinterty Observatories
Aberdeen, UK

Altair Astro GSO 10" f/8 Ritchey Chrétien CF OTA on EQ8 mount with homebrew 3D Balance and Pier
Moonfish ED80 APO & Celestron Omni XLT 120
QHY10 CCD & QHY5L-II Colour
9mm TS-OAG and Meade DSI-IIC

Offline lage

  • Newcomer
  • Posts: 22
Re: PCL Win32 System Exception
« Reply #4 on: 2017 March 30 17:09:19 »
I'd say it's clear what I was doing if you look at the attachment.
Nope. This is the first post.
I'm running w10 x64, so I find it odd with an error message indicating 32 bit windows.

Offline Niall Saunders

  • PTeam Member
  • PixInsight Jedi Knight
  • *****
  • Posts: 1456
  • We have cookies? Where ?
Re: PCL Win32 System Exception
« Reply #5 on: 2017 March 30 17:37:09 »
OK - so, how many frames were you integrating?

Can you integrate those frames using the standard ImageIntegration process (as opposed to the BatchPreprocessing script)?

I don't use the BatchPreporcessing script myself, for no other reason than I like to work my own way through the preprocessing stages, just to be sure nothing untoward happens as the the sequence progresses.

What happens if you tick the Calibration Only checkbox in the Integration section? Does the process run to completion and produce a full set of images ready for integration? Can you then integrate those images using the ImageIntegration process?

If the script does execute to completion (as described above), but ImageIntegration still fails, what error messages do you get (either on-screen, or in the ProcessConsole window)? If you examine the calibrated images that are failing the ImageIntegration step - are there any images that 'appear' to be different or unusual in any way?

By the way, do you get any report in the ProcessConsole window when you see the error messagethat you have posted?

Sorry about all the questions, but your extremely short posts and a lack of a detailed description means that the information needs to be sniffed out. It is extremely unlikely that your error messages, alone, will suggest a simple 'quick fix' (unless the author(s) of the script know of issues that can trigger this message).

Unfortunately I have spent almost forty years providing technical support (by HF radio (even using morse code), by phone, by fax and by email) - you have to try and imagine me trying to put myself in your chair, in front of your PC and then trying to replicate, analyse and resolve your isuue without ever actually being there!!!

I will try my best  :)
Cheers,
Niall Saunders
Clinterty Observatories
Aberdeen, UK

Altair Astro GSO 10" f/8 Ritchey Chrétien CF OTA on EQ8 mount with homebrew 3D Balance and Pier
Moonfish ED80 APO & Celestron Omni XLT 120
QHY10 CCD & QHY5L-II Colour
9mm TS-OAG and Meade DSI-IIC

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: PCL Win32 System Exception
« Reply #6 on: 2017 March 31 00:19:10 »
Looking at your console log I see many error messages like these:

*** Error: Invalid block position: attachment:8192:439084800 (line=7,column=123)
*** Error: The XSIF file contains no readable image. (line=78,column=7)


This error happens when an XISF file has been truncated. In other words, the data block where the image was stored when the file was created, at byte offset 8192 with length 439,084,800 bytes, is no longer available. You have many registered files that are not readable because they have been corrupted or damaged for some reason. One possibility is that you are running out of disk space. Another one is hardware errors.

Quote
I'm running w10 x64, so I find it odd with an error message indicating 32 bit windows.

On Windows, the term "Win32 error" is used to indicate errors reported by the operating system through its applications programming interface (API). It does not mean that you are running a 32-bit process or something like that. It is just technical jargon inherited from the good old days of Windows 3.1 + Win32s. Here is the complete list of Win32 error codes at MSDN:

https://msdn.microsoft.com/en-us/library/cc231199.aspx
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline Niall Saunders

  • PTeam Member
  • PixInsight Jedi Knight
  • *****
  • Posts: 1456
  • We have cookies? Where ?
Re: PCL Win32 System Exception
« Reply #7 on: 2017 March 31 04:06:47 »
Thanks Juan,

I hadn't spotted the extract of the ConsoleLog in the first post (to me, and with no descriptive text in the main post to go on, there were just two screen images to look at - hence the reason for having to ask all the questions!)

None the less, thanks for your valuable input.
Cheers,
Niall Saunders
Clinterty Observatories
Aberdeen, UK

Altair Astro GSO 10" f/8 Ritchey Chrétien CF OTA on EQ8 mount with homebrew 3D Balance and Pier
Moonfish ED80 APO & Celestron Omni XLT 120
QHY10 CCD & QHY5L-II Colour
9mm TS-OAG and Meade DSI-IIC

Offline lage

  • Newcomer
  • Posts: 22
Re: PCL Win32 System Exception
« Reply #8 on: 2017 March 31 07:04:41 »
Root cause was no disk space. This should be better error handled if you ask me. an error message and an option to choose another disk.

Offline msmythers

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1178
    • astrobin
Re: PCL Win32 System Exception
« Reply #9 on: 2017 March 31 08:09:12 »
I'm not trying to defend PI but from the System Requirements page  http://www.pixinsight.com/sysreq/index.html


Hard Disk Space

To maximize availability of RAM for critical tasks, the processing history management and masking systems implemented in PixInsight are based on temporary disk swap files. In addition, more space is required during file writing operations because of disk I/O security strategies (basically, when an existing file is rewritten a temporary copy of the original is kept during the whole disk write operation).

We really cannot speak of a minimum required free disk space, since this depends on the number and dimensions of the images that the user opens and modifies in the application. PixInsight is able to store and manipulate seven different sample formats transparently: 8, 16 and 32-bit integers, along with 32 and 64-bit real and complex floating point. 32-bit and 64-bit images require two and four times more disk storage space, respectively, than the native 16-bit format of a CCD camera. In addition, PixInsight can store an unlimited number of history states (unlimited undo/redo operations). This makes PixInsight Core a demanding application regarding free disk space requirements. For serious production work, we recommend a minimum of 50 to 200 GB of free hard disk space, depending on the average size of your images and the complexity of your processing workflows.



Stacking 300, RGB images that are 7392x4950 is serious work and requires a lot of free disc space.



Mike

Offline lage

  • Newcomer
  • Posts: 22
Re: PCL Win32 System Exception
« Reply #10 on: 2017 March 31 08:40:20 »
No excuse for not giving an error message if you run out of disk. Crappy coding.

Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4729
Re: PCL Win32 System Exception
« Reply #11 on: 2017 March 31 08:43:41 »
bye felicia

Offline Niall Saunders

  • PTeam Member
  • PixInsight Jedi Knight
  • *****
  • Posts: 1456
  • We have cookies? Where ?
Re: PCL Win32 System Exception
« Reply #12 on: 2017 March 31 08:44:35 »
Quote
Stacking 300, RGB images that are 7392x4950 is serious work and requires a lot of free disc space.

Almost 250Gb if my mental arithmetic is any good this afternoon!
Cheers,
Niall Saunders
Clinterty Observatories
Aberdeen, UK

Altair Astro GSO 10" f/8 Ritchey Chrétien CF OTA on EQ8 mount with homebrew 3D Balance and Pier
Moonfish ED80 APO & Celestron Omni XLT 120
QHY10 CCD & QHY5L-II Colour
9mm TS-OAG and Meade DSI-IIC

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: PCL Win32 System Exception
« Reply #13 on: 2017 March 31 11:20:51 »
Quote
No excuse for not giving an error message if you run out of disk. Crappy coding.

Oh well, I'll try to do better next time. Since you've purchased your license two weeks ago, I'll be glad to process a full refund if that's what you want.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline lage

  • Newcomer
  • Posts: 22
Re: PCL Win32 System Exception
« Reply #14 on: 2017 March 31 12:01:53 »
No, I want basic error handling. Is that asking too much?