Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

AppleWin 1.20.0

448 views
Skip to first unread message

TomCh

unread,
Feb 24, 2011, 5:28:26 PM2/24/11
to
Hi,

Michael has added support for accurate half-pixel rendering (in both
color & monochrome modes). Great perseverance in rev-engineering &
extending this 16 year old renderer, Michael!

The latest build is available here:
http://prdownload.berlios.de/applewin/AppleWin1.20.0.0.zip

FYI: See Sheldon's NTSC build (another thread on cea2) for a taste of
what we want to fully integrate into the AppleWin mainline.

Tom


History since 1.19.3:

Changes:
. Standard, Text Optimized and Monochrome video modes now support half-
pixel rendering accuracy!
. Colors tweaked to better match the real hardware.

Fixes:
. Fixed Mockingboard detection for Ultima III (ProDOS-8/harddisk
version).

Debugger
. See the Debugger_Changelog.txt for the various fixes and changes.

Misc:
. Updated acknowledgements. Cheers to Mike Harvey! (Nibble Magazine)

Rob

unread,
Feb 25, 2011, 8:13:14 AM2/25/11
to
Yah! Thanks guys.

rich12345

unread,
Feb 26, 2011, 2:12:19 PM2/26/11
to
On Feb 24, 2:28 pm, TomCh <tomcharleswo...@blueyonder.co.uk> wrote:
> Hi,

>
> The latest build is available here:http://prdownload.berlios.de

cool! its great you guys keep on updating this excellent emulator!

question:

is there a new "exit mouse input mode" key combination? control click
doesn't exit the mode any more.....

also, once in mouse input mode, the "crosshairs" on the border of
applewin are frozen, non responsive to mouse movements

TomCh

unread,
Feb 26, 2011, 6:37:22 PM2/26/11
to
On Feb 26, 7:12 pm, rich12345 <aiiad...@gmail.com> wrote:
> question:
>
> is there a new "exit mouse input mode" key combination?  control click
> doesn't exit the mode any more.....
>
> also, once in mouse input mode, the "crosshairs" on the border of
> applewin are frozen, non responsive to mouse movements

I can't reproduce either of these - both work fine on my WinXP machine
(I tested with Dazzle Draw).
I tried in both windowed & full-screen modes.

What's your configuration?

Tom

Bill Garber

unread,
Feb 26, 2011, 8:15:59 PM2/26/11
to

"TomCh" <tomchar...@blueyonder.co.uk> wrote in message news:cebb
fef1-f61e-4c1e-a...@u24g2000prn.googlegroups.com...

Tom and Rich,

I concur, the mouse feature works fine for me as well.

I am having issues with the NTSC version that Sheldon claims to be
"mystifying".

Bill G.

rich12345

unread,
Feb 26, 2011, 10:59:35 PM2/26/11
to
On Feb 26, 3:37 pm, TomCh <tomcharleswo...@blueyonder.co.uk> wrote:
> What's your configuration?
>
> Tom

windowed, just booted to my basic startup program selector...

previous version 1.15.0.1 works just fine.

Rich

rich12345

unread,
Feb 28, 2011, 9:23:01 PM2/28/11
to

Nobody else having this issue?

It's very strange. Previous versions of applewin the Joystick mouse
worked fine... I thought it may have been a registry issue

TomCh

unread,
Mar 1, 2011, 5:02:38 PM3/1/11
to

If you can email me the .dsk image, then I can try to reproduce here.

Tom

johnsonlam

unread,
Mar 2, 2011, 12:36:40 AM3/2/11
to
On Feb 24, 5:28 pm, TomCh <tomcharleswo...@blueyonder.co.uk> wrote:

Hi,

> Michael has added support for accurate half-pixel rendering (in both
> color & monochrome modes). Great perseverance in rev-engineering &
> extending this 16 year old renderer, Michael!

Thanks everyone! Wish all of you happy 'Appleing'.

rich12345

unread,
Mar 2, 2011, 10:46:23 AM3/2/11
to
On Mar 1, 2:02 pm, TomCh <tomcharleswo...@blueyonder.co.uk> wrote:
> If you can email me the .dsk image, then I can try to reproduce here.
>

I don't think that is going to help. It doesn't matter if I boot
into prodos, or turn on emulated machine without any disks...

IE, eject all disk. set HD to NONE. start applewin.exe:

clicking windows mouse pointer in applewin video output does this:
1)crosshairs show up... frozen, don't move when mouse moves
2)control/left click does not exit mouse input mode.

schmidtd

unread,
Mar 2, 2011, 11:22:25 AM3/2/11
to

Good testcase... seems to work fine here on Windows 7, with any
combination of "show crosshairs" or "restrict mouse to Apple window"
checkboxes, too.

What is your physical pointer device? Anything out of the ordinary?

Michael AppleWin Debugger Dev

unread,
Mar 2, 2011, 3:01:51 PM3/2/11
to
Thanks for the mention Tom. I actually had a lot of fun doing this -- as you can tell with all the various alternative display rendering modes in the DEBUG version of AppleWin. ;-)

Couple more "minor" (HA! SDL, 2x zoom, etc) video things TO DO and I can get back to the debugger ... this lack of command line editing is starting to "annoy" me. :)

Keep sending us your feedback everyone! Positive or Negative -- we are slowly continuing to implement features, wish lists, and make it one of the best emulators out of the box.

Cheers
Michael

rich12345

unread,
Mar 2, 2011, 3:40:22 PM3/2/11
to
On Mar 2, 8:22 am, schmidtd <schmi...@my-deja.com> wrote:
> What is your physical pointer device?  Anything out of the ordinary?

I go to:
http://download.berlios.de/applewin/AppleWin1.20.0.0.zip

open with winzip. extract to desktop/applewin

start application from: desktop/applewin/applewin.exe


ok click video output of apple: crosshairs lock and cant exit mouse
mode or see windows cursor

I just found it:

I disabled mouse interface. I can use mouse as the joystick,

(I forgot to mention that mouse emulation of joystick was enabled the
whole time)

cursor crosshairs move, I can control click to exit mode....

Mouse was selected as joystick input and mouse card was enabled at the
same time... I try to go back and enable mouse interface, then enable
mouse as joystick emulator, and it tells me it can't do it (like it
should, you can't have a total of 4 axis emulated by a 2 axis mouse!)
Must have something to do with the registry? keeping old settings?

Rich


rich12345

unread,
Mar 2, 2011, 3:45:02 PM3/2/11
to
On Mar 2, 12:01 pm, Michael AppleWin Debugger Dev

> Keep sending us your feedback everyone!  Positive or Negative -- we are slowly continuing to implement features, wish lists, and make it one of the best emulators out of the box.
>

applewin rocks!

requests: seperate window for debugger, with wider columns for source
more than 1 window for video output. window1=apple II selected video
mode. window2=any mode you choose (IE, have HGR1 on apple video
outputwindow . have HGR2 on the "extra" video output window.)

--option to Get Source files for debugger from HDV image used as apple
II hard disk.

comment: your choice of syntax for the debugger is ?interesting? :-)


Rich

rich12345

unread,
Mar 2, 2011, 6:36:28 PM3/2/11
to
On Mar 2, 12:01 pm, Michael AppleWin Debugger Dev
> Keep sending us your feedback everyone!  Positive or Negative -- we are slowly continuing to implement features, wish lists, and make it one of the best emulators out of the box.
>


feature wish: Slinky RAM card emulation

Michael AppleWin Debugger Dev

unread,
Mar 3, 2011, 2:25:30 PM3/3/11
to
> requests: seperate window for debugger
Feel free to keep "reminding" me ;-)

We really need to have a "window manager" -- I have slowly been putting in the framework to support this on the back end, as everything was hard-coded to just one (debugger) window. This has been a lot of work, and constantly getting pushed down in priority, but yes, thanks for keeping this on "my radar" so to speak.

I was hoping to have the SDL port done sooner, which is the second reason this feature request has been delayed.


>, with wider columns for source

Yeah, I'm starting to run into this myself.
a) The "tabs" in the dissembly while not hard-coded, are not user configurable
b) there is no way to disable the "info" CPU/REGS window on the right. If the user had the option to move that to a seperate window that would help.

I'm still looking for a clean way to support this, as we "need" to support the original mode. I put "need" in quotes, because I don't know all who is using the debugger. I like the "all-in-one" mode, as it is compact, but it definitely looses flexibility.

I'll have to talk to Tom is he feels it is OK to move the debugger to a seperate window permanently.


> more than 1 window for video output. window1=apple II selected video
mode. window2=any mode you choose

Yup, I need this functionality for my memory visualizer, so it is on the TO DO list.

> comment: your choice of syntax for the debugger is ?interesting? :-)

Could you clarify the context please? :-)

color syntax hilighting?
undocumented instructions?
debugger commands?
assembly opcodes? (I am planning on supporting all the assembler directives for Acme, Big Mac, DOS Tool Kit, Lisa, Merlin, MicroSparc, ORCA/M, Ted II, Well, and one other, with the user being able to specify what type they want to use for input/output. Preliminary support is already in the built-in assemblyer.)

A lot of things seem hard-coded to the user -- at the source level, some are, some aren't -- the biggest problem is that they are not exposed to the user to configure. We will have a proper options / config tab for the debugger -- its been a question of priority.

These are the things I'm tentatively working on next:
a) SDL port
b) Zoom x2 suppport
c) Debugger Command Line Editing and History

You would also like to see:
d) Seperate Debugger Windows

Am I right in assuming you would like to see (d) first priority? :-)

Thanks for the feedback Rich!

Michael AppleWin Debugger Dev

unread,
Mar 3, 2011, 2:27:56 PM3/3/11
to
> option to Get Source files for debugger from HDV image used as apple
II hard disk.

Rich, could you take some time to send me a repro instructions + images please?

I can see how this would save you a ton of time! I need the full environment to duplicate your usage case to make sure I implement this properly (and test to make sure it works. :)

Cheers,
Michael

Michael AppleWin Debugger Dev

unread,
Mar 3, 2011, 2:43:35 PM3/3/11
to
> requests: seperate window for debugger

Rich, assuming the debugger full-screen colors were fixed :-), do you ever want to / need to use the full-screen debugger?

Assuming you used the full-screen debugger: If the debugger supported seperate windows, how would you like the full-screen debugger to function please?

Cheers,
Michael

rich12345

unread,
Mar 3, 2011, 4:41:04 PM3/3/11
to
On Mar 3, 11:27 am, Michael AppleWin Debugger Dev

<michael.pohore...@gmail.com> wrote:
> > option to Get Source files for debugger from HDV image used as apple
>
> II hard disk.
>
> Rich, could you take some time to send me a repro instructions + images please?
>


you could make it all configurable (and should)...

have user specify: slot, drive, subdirectory/sub/sub/file.txt
(through a file browser that works with HDV images)

so for me:

S7/D1/Merlin/SRC/MAPPERXP2SRC.TXT

then the debugger opens the HDV image, goes to the specified file, and
uses it for debugger source

Rich

rich12345

unread,
Mar 3, 2011, 4:42:28 PM3/3/11
to
On Mar 3, 11:43 am, Michael AppleWin Debugger Dev

>
> Assuming you used the full-screen debugger: If the debugger supported seperate windows, how would you like the full-screen debugger to function please?
>

I would like it to function just as it does... seperate window so I
can watch HGR screen while debugging (and stepping through) some
things.

rich12345

unread,
Mar 3, 2011, 4:45:06 PM3/3/11
to
On Mar 3, 11:25 am, Michael AppleWin Debugger Dev

<michael.pohore...@gmail.com> wrote:
> You would also like to see:
> d) Seperate Debugger Windows
>
> Am I right in assuming you would like to see (d) first priority? :-)
>
> Thanks for the feedback Rich!

:-) If I had a simultaneous view of what's going on in the apple
(video output and cpu activity) then I would be more likely
to code some more fun apple II things :-)

rich12345

unread,
Mar 4, 2011, 12:30:41 PM3/4/11
to

Michael AppleWin Debugger Dev wrote:
> Rich, assuming the debugger full-screen colors were fixed :-), do you ever want to / need to use the full-screen debugger?
>
> Assuming you used the full-screen debugger: If the debugger supported seperate windows, how would you like the full-screen debugger to function please?

i just figured out what you mean by full screen debugger.... my
opinion: full screen is for playing games. once they are debugged in
windowed mode.. so id leave the FS debugger as is

rich12345

unread,
Mar 4, 2011, 1:38:38 PM3/4/11
to
On Mar 3, 11:25 am, Michael AppleWin Debugger Dev
<michael.pohore...@gmail.com> wrote:
> d) Seperate Debugger Windows
>
> Am I right in assuming you would like to see (d) first priority? :-)
>

http://rich12345.tripod.com/debugger.JPG....

wider columns for source not shown

seperate windows for Watches? Registers?

WATCH command for labels in source (then in watch window, put LABEL =
$XX)
16bit watches in watch window ( LABEL = $XXXX)

:-)

MotoFox

unread,
Sep 23, 2011, 9:49:33 AM9/23/11
to
Works great, Tom! Thanks!

Even on the dinky old Tecra...... ;o)

--
MotoFox
Originator of the word "enubulous"

I just tell everybody to run Linux, myself.

The "users are idiots and are confused by functionality" approach of
Apple is a disease. If you design your OS for idiots, only idiots will
use it. I don't use a Macintosh, because in striving to be so simple,
they simply can't do what I need them to do.

Please, just tell everybody to go to Linux.

pedigo...@yahoo.com

unread,
Mar 20, 2017, 5:50:15 PM3/20/17
to
would it be possible for you to update the control scheme to allow WASD or arrow keys with either the space bar or enter as action? the current controls are awful and in archons case, the mouse doesn't work properly

Michael AppleWin Debugger Dev

unread,
Mar 21, 2017, 2:59:53 PM3/21/17
to
On Monday, March 20, 2017 at 2:50:15 PM UTC-7, pedigo...@yahoo.com wrote:
> would it be possible for you to update the control scheme to allow WASD or arrow keys with either the space bar or enter as action? the current controls are awful and in archons case, the mouse doesn't work properly

I've added Feature Request #396 for this.

https://github.com/AppleWin/AppleWin/issues/396

yews...@gmail.com

unread,
Mar 21, 2017, 9:04:47 PM3/21/17
to
On Thursday, March 3, 2011 at 7:45:02 AM UTC+11, rich12345 wrote:

> more than 1 window for video output. window1=apple II selected video
> mode. window2=any mode you choose (IE, have HGR1 on apple video
> outputwindow . have HGR2 on the "extra" video output window.)

Just out of curiosity, would you mind providing a use-case for that? Would these windows be sharing the same Apple II instance, or would they be two separate instances?

Thanks!

spedi...@gmail.com

unread,
Jan 9, 2020, 4:46:03 PM1/9/20
to
same window, I guess.

spedi...@gmail.com

unread,
Jan 9, 2020, 4:47:08 PM1/9/20
to
in other words, when I try to use the number pad, it fails to work and if I use cursors I get some form of warning, then they also fail to work
0 new messages