Mike Chaney's Tech Corner
July 06, 2020, 05:49:19 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Feb 2013: Qimage Ultimate Challenges... have fun and explore features!
 
   Home   Help Search Login Register  

Professional Photo Printing for Windows
Print with
Qimage and see what you've been missing!
Pages: [1] 2
  Print  
Author Topic: QU - occassional error message etc  (Read 14010 times)
PH Focal-Scape
Sr. Member
****
Posts: 262



View Profile WWW
« on: August 21, 2010, 07:49:36 AM »

Mike et al,

I'm running QU on Windows 7 64bit (actually as a virtual machine via VirtualBox on Mac OS x host).

1/ It performs well but, on start up, I occassionally get a "QImage" headed error message saying "A call to an OS Function failed". I click OK and QU proceeds to run fine.

Any idea what is causing it?

2/ Also occasionally get this when starting the image Editor:

http://pastoralsystems.co.nz/pshphotos/QUScreen.jpg

Seems to be a screen refresh problem? The white strip is a residual of the yellow bubble help displayed over the image thumbnail immediately prior to double-clicking the thumbnail to Edit Image.

3/ Loading of a large (eg 250MB) TIFF into the page editor sometimes takes a very long time compared to loading the image into the image editor. Although I expect it to take longer loading into the page editor, the extent of the difference is much more than with Q Studio.  


Thanks

Peter  

« Last Edit: August 21, 2010, 10:39:21 AM by pshrutpark » Logged

Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3195



View Profile WWW
« Reply #1 on: August 21, 2010, 09:10:01 AM »

Quote
Also occasionally get this when starting the image Editor:

http://pastoralsystems.co.nz/pshphotos/QUScreen.jpg

Seems to be a screen refresh problem?
I've seen this too on v110 and earlier, but not seen it yet on v111 (early days). I assumed it was something to do with my video card. I was about to check for driver updates.
I'm on XP and and old P4 machine
Terry
Logged
PH Focal-Scape
Sr. Member
****
Posts: 262



View Profile WWW
« Reply #2 on: August 21, 2010, 09:15:59 AM »

Thanks for the response Terry. As you will see I have listed 2 more "issues". Any comment on the others?
Logged

Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3195



View Profile WWW
« Reply #3 on: August 21, 2010, 09:25:26 AM »

Peter,
Quote
As you will see I have listed 2 more "issues". Any comment on the others?
No issues here wrt the other 2. In fact the image editor seems a little slower that the FPE but both depend on the edit filters present.
Terry
Logged
Fred A
Forum Superhero
*****
Posts: 5283



View Profile WWW Email
« Reply #4 on: August 21, 2010, 09:43:13 AM »

Quote
/ Loading of a large (eg 250MB) TIFF into the page editor sometimes takes a very long time compared to loading the image into the image editor. Although I expect it to take longer loading into the page editor, the extent of the difference is much more than with Q Studio.   

Peter, how are you set in the Full Page Editor?
Under Rulers, there's a selection box where you choose Thumbs/small images or Selected or ALL.
If you use Thumbs/ Small images, the FPE is lightning fast. If you are set for ALL or Selected, then you are asking for a High Resolution image, and it takes a while to load a large file.

Fred
Logged
PH Focal-Scape
Sr. Member
****
Posts: 262



View Profile WWW
« Reply #5 on: August 21, 2010, 09:54:15 AM »

Thanks Fred. I'll check those settings.

Peter
Logged

PH Focal-Scape
Sr. Member
****
Posts: 262



View Profile WWW
« Reply #6 on: August 22, 2010, 11:10:37 PM »

Any comment on the "A call to an OS Function failed" message Mike?

Peter
 
Logged

admin
Administrator
Forum Superhero
*****
Posts: 3074



View Profile Email
« Reply #7 on: August 23, 2010, 12:31:05 AM »

A couple things here:

(1) I'm estimating about a 90% chance that the screen draw problem is a video driver bug.  Could anyone having the problem please list the model number of your video board and also the driver version?

(2) On "A call to an OS function failed", sounds like it might be a Mac specific problem with Macs running Windows.

FWIW, neither of these have been reported outside of this thread/forum.

Regards,
Mike
Logged
Box Brownie
Newbie
*
Posts: 48


View Profile
« Reply #8 on: August 23, 2010, 01:10:51 AM »

Hi Mike

I am also seeing the odd apparent redraw glitch ~ my card is an nVidia GeForce 6200 using driver version 6.14.10.9371

For the record I look forward to your thoughts & insight I 'talk' about here http://ddisoftware.com/tech/qimage-ultimate/tts-initial-impressions/

TIA

Smiley
Logged
PH Focal-Scape
Sr. Member
****
Posts: 262



View Profile WWW
« Reply #9 on: August 23, 2010, 02:36:16 AM »

A couple things here:

(1) I'm estimating about a 90% chance that the screen draw problem is a video driver bug.  Could anyone having the problem please list the model number of your video board and also the driver version?

(2) On "A call to an OS function failed", sounds like it might be a Mac specific problem with Macs running Windows.

FWIW, neither of these have been reported outside of this thread/forum.

Regards,
Mike

Thanks Mike.

Yes, I could be related to the video driver (virtualisation with VirtualBox). My Mac has a NVIDIA GeForce GT 330M video card.

The message box relating to the error is titled QImage, therefore I assumed that it was a specific QImage message rather than comming from the OS.

I briefly tested the same images on my Windows XP Pro PC and found that I don't get the problem.

Peter
Logged

Terry-M
The Honourable Metric Mann
Forum Superhero
*****
Posts: 3195



View Profile WWW
« Reply #10 on: August 23, 2010, 07:12:56 AM »

Quote
Could anyone having the problem please list the model number of your video board and also the driver version?
I've not had the problem since updating to v111 but my video card is an NVidea 8400GT with the latest driver 258.96
Terry
Logged
admin
Administrator
Forum Superhero
*****
Posts: 3074



View Profile Email
« Reply #11 on: August 23, 2010, 01:05:22 PM »

The message box relating to the error is titled QImage, therefore I assumed that it was a specific QImage message rather than comming from the OS.

The error is titled Qimage just because the error happened while running "qimage.exe".  The error message indicates that one of the standard Windows API calls crashed.  By definition, that means that the OS either failed when that OS function was called or it crashed inside the OS function.  What that really indicates is that the error occurred inside OS code, not Qimage code.  Of course, that doesn't completely rule out Qimage as the cause (it could have passed "gibberish" to the OS) but usually it is more an indication that something isn't "healthy" with the OS.

Mike
Logged
jeffjessee
Jr. Member
**
Posts: 76


.


View Profile Email
« Reply #12 on: August 23, 2010, 01:36:56 PM »

Mike, I have the redraw problem (message from first screen shows up on batch screen and full page editor.) I have an ATI Radeon X600XT, and driver 6.14.10.6483, which is the latest I can find.

Incidentally, I have found the message doesn't transfer if I move the cursor to the folder window after double-clicking and before the batch window opens.

Jeff Jessee
Logged
PH Focal-Scape
Sr. Member
****
Posts: 262



View Profile WWW
« Reply #13 on: August 23, 2010, 10:05:59 PM »

Regarding the QU problems I have mentioned above.

I turned 3D Graphics off (now just using 2D) and so far the various problems haven't reoccurred.

It may be worth other users who are experiencing problems to try similar and see if it resolves the problem on normal machines (ie not as is mine, a virtual machine hosted by OS X). This may help identify the source.

Incidently, prior to turning the 3D off, the initial large yellow start up QU icon would display normally and then redisplay without transparency (ie white around the yellow circle in shape of square). Additionally, within QU, the scrolling of the image thumbnails and selecting of an image was a little erratic.

Again this could be a virtualisation problem, but maybe not since other users have similar symptoms.

Mike I have MS Visual Studio installed and that has installed some sort of continually running debugger which reports problems in programmes. The error message may be generated by that.

Peter
 

         
Logged

admin
Administrator
Forum Superhero
*****
Posts: 3074



View Profile Email
« Reply #14 on: August 24, 2010, 01:40:59 PM »

For anyone having the screen draw/refresh problem, please give 112 a try.  I changed the way Qimage draws the windows and I believe it will gel better with certain video cards.

Regards,
Mike
Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!