www.virtualacorn.co.uk/forum

For support and advice on VirtualAcorn products
Forums now closed. This is an HTML only record of the content.
HTML version of Forum generated Thursday 24th May 2018

All times are UTC [ DST ]




Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: "Failed to create primary surface (0x8876024e" on a Vista no
PostPosted: Wed Jul 01, 2009 2:18 pm 
Offline

Joined: Fri Jun 26, 2009 6:30 am
Posts: 20
Hi,

on my Vista notebook (Vista Home Premium, SP2) there are two things...

-run Uniprint.exe AFTER VirtualRPC,

-minimise VirtualRPC to the task bar and leave it there for something like ten minutes,


...which invariably lead to the above error message.

Afterwards the window containing VRPC is empty - i.e. it shows whatever was behind it at the moment I tried to go back to VRPC after doing one of the two things above.

I've so far not found any way to get VRPC working again short of quitting from Windows and re-running VRPC.

Is this an effect singular to my machine, or is this a more widespread problem with Vista?


Kind Regards,

Jochen

_________________
From Cologne on the banks of the Rhine - 2000 years old but still young at heart. ;-)


Last edited by Marabu_Too on Wed Jul 01, 2009 2:36 pm, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: "Failed to create primary surface (0x8876024e" on a Vista no
PostPosted: Wed Jul 01, 2009 2:35 pm 
Offline

Joined: Fri Jun 26, 2009 6:30 am
Posts: 20
Ooops,

my eye sight must be failing; I only just noticed that there is a very similar thread further down the page; maybe Aaron should move my first message there?

Regards,

Jochen


Top
 Profile  
 
 Post subject: Re: "Failed to create primary surface (0x8876024e" on a Vista no
PostPosted: Thu Jul 02, 2009 11:26 am 
Offline
Site Admin

Joined: Wed Oct 23, 2002 12:16 pm
Posts: 958
There are several posibilities. Firstly make sure that UAC is disabled.

The error indicates that for some reason VirtualRPC couldn't grab the screen buffer it needs to display the RISC OS output. This could be caused by:

A problem with the graphics drivers on this machine
A fault with DirectX
Something else messing up the DirectX workspace pointers.

It's not (as far as I am aware) a general problem.


Top
 Profile  
 
 
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

   
Forums originally Powered by phpBB © 2007 phpBB Group. Contents © 3QD Developments Ltd 2018 version no. 1.07