Capturing and Recycling AppleWin Lo-Res and Double Lo-Res Screens - A Tutorial

[Bill Buckels]

Now available from the Following Link:

http://www.aztecmuseum.ca/AppleWin_LGR_DLGR_ScreenGrabs_2013.pdf

The document above describes how to capture and edit both Lo-Res and Double
Lo-Res Screen Captures from the AppleWin Apple IIe Emulator.

This completes a series of Tutorials on Capturing and Recycling AppleWin
Screen Captures for all 4 Standard Graphics modes of the Apple IIe.

The utilities discussed in these tutorials have undergone further testing
and refinement over the last day or so and the latest revisions will be
uploaded sometime tomorrow.

Updates will also simultaneously occur to both the AppleX Prodos 8 and the
Apple33 DOS 3.3 distrubutions of the Aztec C65 Apple IIe cross-compiler for
MS-DOS/Windows.

These updates provide the Aztec C65 developer with the expanded capabilities
of creating cross-compiled programs using a toolchain of utilities and
library routines targetted at all 4 graphics modes for "raw" ProDOS 8, the
Aztec C Shell for ProDOS 8, and DOS 3.3 which includes complete File I/O
capability, floating point capability from the comfort of your Windows
Machine or any place that MS-DOS runs in an MS-DOS emulator, including Linux
platforms like Ubuntu.

All the best, and have fun!

Bill Buckels

[TomCh]

Great document, Bill!

re. "always capture any screen to be converted using my utilities with 50% Scan lines *OFF*!"

Why is this?

NB. There is a bug in AppleWin when making a 280x192 screenshot (SHIFT+PrintScreen) in 50% Scan line mode. This is now fixed as of AppleWin 1.22.1.4 (an internal version only). I do plan to release a build publically soon which will include this fix.

Tom

[Bill Buckels]

"TomCh" <tomchar...@blueyonder.co.uk> wrote:
> re. "always capture any screen to be converted using my utilities with 50%
> Scan lines *OFF*!"

> Why is this?

Because I'm old and write restricted procedures, or because I can't hit a
moving target at my age? Take your pick!

I can't remember really, but it seems to me that somewhere along the line
when I tried this it didn't work and that was the end of that! If something
works I go with it and if works consistently then by dog it goes in the
document and we go to press! Where we find the time to do any of this is
still beyond me...

BTW something that STILL doesn't work is Microsoft Visual Studio Express 10.
I have not been ignoring AppleWin... but busy on other Aztec C stuff too.

1. I upgraded my Windows XP to SP3 because VS10 Express C++ complained when
I tried to do an install. This is my god machine for old stuff. My Windows 7
machines are clean. I was reluctant to change anything at all on this tower
because I newly upgraded all the hardware including drives and it screams
and works great, but I want to play with AppleWin. The SP3 upgrade is
idiotic and still takes forever too.

2. I have a complete licenced copy of VS8. It still works fine of course. As
does my VS 5 and everything else back to MSC 5.0 and prior. MinGW and Qt
work here too, and so does cygwin. So does BC++ various versions and Turbo C
1.0, Aztec C86, Mix Power C, etc.

Cross compilers written in the early 80's work! SO...

3. I get "exception has been thrown by the target of an invocation" with
VS10. I applied VS 10 SP1 without success and have .NET 4 and so-forth so
assume it is M$oft being sloppy... this is a common bug because I see it
everywhere on google. Does this cr*p work on XP is really my question. The
win 32 commandline works but looks old... or do you know about this?

I downloaded the complete ISO while I was at it, and now I am happy I didn't
bother to install all the other cr*p as well. I need a brandy just thinking
about it!

> NB. There is a bug in AppleWin when making a 280x192 screenshot
> (SHIFT+PrintScreen) in 50% Scan line mode. This is now fixed as of
> AppleWin 1.22.1.4 (an internal version only). I do plan to release a build
> publically soon which will include this fix.

This is very likely the reason that I tell the users of my utilities to turn
50% scanlines off. I have no love for that anyway. It looks nothing like the
RGB monitor on my real IIe.

As far as a public release... in the meantime, I am sure you can find lots
to keep you busy:) And anyone else that gets caught in the Web of
AppleWinDom... too hard to resist for me so if you have any insight on the
VS10 stuff bring it on!

But I am not into spending weeks trying to get junk written by pizza-faced
teenagers to run. If this is not junk it would work I think. With the number
of folks who have had this problem it appears to be abandonware!

You have proved me wrong in the not too distant past so perhaps you will
again... I hope:)

Regards,

Bill

[Bill Buckels]

"Bill Buckels" <bbuc...@mts.net> wrote:
> But I am not into spending weeks trying to get junk written by pizza-faced
> teenagers to run. If this is not junk it would work I think.

I do also want to remark that anyone running the Microsoft Intaller for VS
10 Express had best be prepared for the fact that that it replaces all file
assocations associated with working versions of Visual Studio...

If you compile CiderPress under VS6 for example you may be cleaning up
garbage written by careless children for a product that may not work...

Just thought I'd better make this clear... I am truly disgusted.

Bill

[Steve Nickolas]

On Tue, 23 Apr 2013, Bill Buckels wrote:

> 2. I have a complete licenced copy of VS8. It still works fine of course. As
> does my VS 5 and everything else back to MSC 5.0 and prior. MinGW and Qt
> work here too, and so does cygwin. So does BC++ various versions and Turbo C
> 1.0, Aztec C86, Mix Power C, etc.
>
> Cross compilers written in the early 80's work! SO...

Yeah, I'm biased toward using MinGW or OpenWatcom rather than VC here, and
still use Borland 3.1 on occasion.

-uso.