[Coco] VCC 1.17

[Joef6809]

You've hit a debug message that (I thought) should never happen.
It happens when DirectDraw successfully locks the secondary draw buffer but 
doesn't get a pointer back. As far as I knew untill now , that was 
imposible.
what should happen is either the lock should fail or you get back a real 
pointer to memory. I've got a couple of Vista machines I can test this on 
and should have it fixed in the next release assuming I can reproduce it. I 
have a feeling MS changed the API a little in vista so I have to handle this 
condition now. Thats for letting me know.


>From Hell's heart I STore Accumulator B at thee!

----- Original Message ----- 
From: "Roger Taylor" <operator at coco3.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, February 24, 2008 3:21 PM
Subject: [Coco] VCC 1.17


> To the author of VCC...  I'm using 1.17 and have noticed that sometimes 
> the emulator will abort with what appears to be an exception error box. 
> The error I'm getting is "Returning Null!!" and the VCC window goes black, 
> with no return.
>
> Here are some things that have set this error off: closing the laptop and 
> reopening, or if Window Vista dims the screen for an admin "Click 
> Continue" dialog.  After this, VCC is down.
>
> This is not critical to me right now since I'm just using VCC to help test 
> some games I'm developing in the Rainbow IDE.  When the IDE builds my .bin 
> I have another explorer window open to "\Files" where I can click on the 
> binary and launch it (nice feature, btw).
>
> If someone is using VCC to work around DOS or OS-9 and they have important 
> stuff they don't want to lose, don't put your computer to sleep, close the 
> laptop, or do any admin-prompted functions.
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco