I'm using WASP (Windows AppleSoft Programmer), and when I'm ready
to
send my finished program to AppleWin (my Apple //e emulator),
AppleWin
does not boot the Apple //e, but simply stares at me as if to say,
"What?"

Then, when my Apple //e in AppleWin is on, and I try to send the
program to AppleWin, WASP returns an error, saying, "No Emulator
Running!" even when I know full well that AppleWin is active.

What's the deal here?

Brandon Taylor

DMn2004... at (no spam) gmail.com> wrote in message

news:7f2390d6-e408-488d-b26e-7078baeb06f2 at (no spam) z28g2000vbl.googlegroups.com...

I'm using WASP (Windows AppleSoft Programmer), and when I'm ready
to
send my finished program to AppleWin (my Apple //e emulator),
AppleWin
does not boot the Apple //e, but simply stares at me as if to say,
"What?"

WASP never booted an image in AppleWin by itself.  You must start
AppleWin *and* boot an image (to an Applesoft prompt) before you can
send a program to it.  You can set up WASP to automatically start
AppleWin everytime WASP starts but you still have to boot an image.
(see the Help menu for how to do this).



Then, when my Apple //e in AppleWin is on, and I try to send the
program to AppleWin, WASP returns an error, saying, "No Emulator
Running!" even when I know full well that AppleWin is active.

What's the deal here?

Brandon Taylor

AppleWin 1.16.1 changed it's name. By that I mean it's process name
under Windows.  When you boot an image in AppleWin you will see (on
the title bar) a dash and the video mode appended to the name.  For
instance "Enhanced Apple //e Emulator - TV".  You can also look for
an emulator's name by using the "List Programs Running" function in
the tools menu.

WASP didn't know ahead of time they were going to change the name so
it's still looking for the old name.  Until I get the new names
added to the default list you can fix it yourself by editing the
WASP.ini file.  Look for a section something like this:

[Emulators]
Number=6
Name[1]=Enhanced Apple //e Emulator
Name[2]=Apple //e Emulator
Name[3]=Apple ][ Emulator
Name[4]=Apple ][+ Emulator
Name[5]=Pravets 82 Emulator
Name[6]=Pravets 8A Emulator

Change Number=6 to Number=7
and then add:

Name[7]=Enhanced Apple //e Emulator - TV
Save the WASP.ini file.

This assumes you are using the TV video mode. If you are using a
different video mode than TV then the name is going to be different.
You can add as many names as you want using this method.

Hope this helps,

Charlie

That's got it. Boy, WASP seems pretty stupid right about now.

DMn2004... at (no spam) gmail.com> wrote in message

news:7f2390d6-e408-488d-b26e-7078baeb06f2 at (no spam) z28g2000vbl.googlegroups.com...

I'm using WASP (Windows AppleSoft Programmer), and when I'm
ready
to
send my finished program to AppleWin (my Apple //e emulator),
AppleWin
does not boot the Apple //e, but simply stares at me as if to
say,
"What?"

WASP never booted an image in AppleWin by itself. You must start
AppleWin *and* boot an image (to an Applesoft prompt) before you
can
send a program to it. You can set up WASP to automatically start
AppleWin everytime WASP starts but you still have to boot an
image.
(see the Help menu for how to do this).



Then, when my Apple //e in AppleWin is on, and I try to send the
program to AppleWin, WASP returns an error, saying, "No Emulator
Running!" even when I know full well that AppleWin is active.

What's the deal here?

Brandon Taylor

AppleWin 1.16.1 changed it's name. By that I mean it's process
name
under Windows. When you boot an image in AppleWin you will see (on
the title bar) a dash and the video mode appended to the name. For
instance "Enhanced Apple //e Emulator - TV". You can also look for
an emulator's name by using the "List Programs Running" function
in
the tools menu.

WASP didn't know ahead of time they were going to change the name
so
it's still looking for the old name. Until I get the new names
added to the default list you can fix it yourself by editing the
WASP.ini file. Look for a section something like this:

[Emulators]
Number=6
Name[1]=Enhanced Apple //e Emulator
Name[2]=Apple //e Emulator
Name[3]=Apple ][ Emulator
Name[4]=Apple ][+ Emulator
Name[5]=Pravets 82 Emulator
Name[6]=Pravets 8A Emulator

Change Number=6 to Number=7
and then add:

Name[7]=Enhanced Apple //e Emulator - TV
Save the WASP.ini file.

This assumes you are using the TV video mode. If you are using a
different video mode than TV then the name is going to be
different.
You can add as many names as you want using this method.

Hope this helps,

Charlie
--------------------------------------------------------------

"DMn2004404" <DMn2004... at (no spam) gmail.com> wrote in message

news:a51bad70-ce82-47e1-a5eb-00a0e902e873 at (no spam) k30g2000yqf.googlegroups.com...
On Aug 7, 2:18 pm, "Charlie" <charlieD... at (no spam) verEYEzon.net> wrote:

DMn2004... at (no spam) gmail.com> wrote in message

news:7f2390d6-e408-488d-b26e-7078baeb06f2 at (no spam) z28g2000vbl.googlegroups.com....

I'm using WASP (Windows AppleSoft Programmer), and when I'm
ready
to
send my finished program to AppleWin (my Apple //e emulator),
AppleWin
does not boot the Apple //e, but simply stares at me as if to
say,
"What?"

WASP never booted an image in AppleWin by itself. You must start
AppleWin *and* boot an image (to an Applesoft prompt) before you
can
send a program to it. You can set up WASP to automatically start
AppleWin everytime WASP starts but you still have to boot an
image.
(see the Help menu for how to do this).

Then, when my Apple //e in AppleWin is on, and I try to send the
program to AppleWin, WASP returns an error, saying, "No Emulator
Running!" even when I know full well that AppleWin is active.

What's the deal here?

Brandon Taylor

AppleWin 1.16.1 changed it's name. By that I mean it's process
name
under Windows. When you boot an image in AppleWin you will see (on
the title bar) a dash and the video mode appended to the name. For
instance "Enhanced Apple //e Emulator - TV". You can also look for
an emulator's name by using the "List Programs Running" function
in
the tools menu.

WASP didn't know ahead of time they were going to change the name
so
it's still looking for the old name. Until I get the new names
added to the default list you can fix it yourself by editing the
WASP.ini file. Look for a section something like this:

[Emulators]
Number=6
Name[1]=Enhanced Apple //e Emulator
Name[2]=Apple //e Emulator
Name[3]=Apple ][ Emulator
Name[4]=Apple ][+ Emulator
Name[5]=Pravets 82 Emulator
Name[6]=Pravets 8A Emulator

Change Number=6 to Number=7
and then add:

Name[7]=Enhanced Apple //e Emulator - TV
Save the WASP.ini file.

This assumes you are using the TV video mode. If you are using a
different video mode than TV then the name is going to be
different.
You can add as many names as you want using this method.

Hope this helps,

Charlie

--------------------------------------------------------------
That's got it.  Boy, WASP seems pretty stupid right about now.

Thanks.

Brandon
--------------------------------------------------------------

I have fixed the name problem by having WASP truncate the process
name to the same length as the name from the WASP.ini file.  That
way "Enhanced Apple //e Emulator" would be equivalent to "Enhanced
Apple //e Emulator - TV" for the purpose of the test.  It will be in
the next release which has been delayed because of a bug in the Open
file dialog when running under Windows 7.
Incidentally, if you are wondering why WASP can't just send the
Applesoft program to AppleWin even if it doesn't detect it running,
it's because AppleWin has to have the keyboard focus to receive the
simulated keystrokes that start the transfer.  I don't know of any
way for WASP to set the keyboard focus without knowing the name of
the that process.  If you or anyone does know of another way I'd
like to hear about it.

Charlie

"DMn2004404" <DMn2004... at (no spam) gmail.com> wrote in message

news:a51bad70-ce82-47e1-a5eb-00a0e902e873 at (no spam) k30g2000yqf.googlegroups.com...
On Aug 7, 2:18 pm, "Charlie" <charlieD... at (no spam) verEYEzon.net> wrote:

DMn2004... at (no spam) gmail.com> wrote in message

news:7f2390d6-e408-488d-b26e-7078baeb06f2 at (no spam) z28g2000vbl.googlegroups.com...

I'm using WASP (Windows AppleSoft Programmer), and when I'm
ready
to
send my finished program to AppleWin (my Apple //e emulator),
AppleWin
does not boot the Apple //e, but simply stares at me as if to
say,
"What?"

WASP never booted an image in AppleWin by itself. You must start
AppleWin *and* boot an image (to an Applesoft prompt) before you
can
send a program to it. You can set up WASP to automatically start
AppleWin everytime WASP starts but you still have to boot an
image.
(see the Help menu for how to do this).

Then, when my Apple //e in AppleWin is on, and I try to send
the
program to AppleWin, WASP returns an error, saying, "No
Emulator
Running!" even when I know full well that AppleWin is active.

What's the deal here?

Brandon Taylor

AppleWin 1.16.1 changed it's name. By that I mean it's process
name
under Windows. When you boot an image in AppleWin you will see
(on
the title bar) a dash and the video mode appended to the name.
For
instance "Enhanced Apple //e Emulator - TV". You can also look
for
an emulator's name by using the "List Programs Running" function
in
the tools menu.

WASP didn't know ahead of time they were going to change the
name
so
it's still looking for the old name. Until I get the new names
added to the default list you can fix it yourself by editing the
WASP.ini file. Look for a section something like this:

[Emulators]
Number=6
Name[1]=Enhanced Apple //e Emulator
Name[2]=Apple //e Emulator
Name[3]=Apple ][ Emulator
Name[4]=Apple ][+ Emulator
Name[5]=Pravets 82 Emulator
Name[6]=Pravets 8A Emulator

Change Number=6 to Number=7
and then add:

Name[7]=Enhanced Apple //e Emulator - TV
Save the WASP.ini file.

This assumes you are using the TV video mode. If you are using a
different video mode than TV then the name is going to be
different.
You can add as many names as you want using this method.

Hope this helps,

Charlie

--------------------------------------------------------------
That's got it. Boy, WASP seems pretty stupid right about now.

Thanks.

Brandon
--------------------------------------------------------------

I have fixed the name problem by having WASP truncate the process
name to the same length as the name from the WASP.ini file. That
way "Enhanced Apple //e Emulator" would be equivalent to "Enhanced
Apple //e Emulator - TV" for the purpose of the test. It will be
in
the next release which has been delayed because of a bug in the
Open
file dialog when running under Windows 7.
Incidentally, if you are wondering why WASP can't just send the
Applesoft program to AppleWin even if it doesn't detect it
running,
it's because AppleWin has to have the keyboard focus to receive
the
simulated keystrokes that start the transfer. I don't know of any
way for WASP to set the keyboard focus without knowing the name of
the that process. If you or anyone does know of another way I'd
like to hear about it.

Charlie

I don't know of any
way for WASP to set the keyboard focus without knowing the name of
the that process. If you or anyone does know of another way I'd
like to hear about it.

I don't know about that,

but I have discovered another WASP anomaly: When I double click a disk
image file in the Open file dialog, the "APPLE ][" section of the dialog is
supposed to show me a list of files that are inside that disk image...

but instead WASP opens the disk image file as if it were a text file, and I
get gibberish.

Among the gibberish is undoubtedly some human-readable data, but the
displayed output is generally useless. What's the issue here?

"DMnDMr" <DMn2004404 at (no spam) gmail.com> wrote:

Charlie wrote:

I don't know of any
way for WASP to set the keyboard focus without knowing the name
of
the that process. If you or anyone does know of another way I'd
like to hear about it.

I don't know about that,

Well, he might try GetModuleFileName after enumerating the open
Windows on
the desktop... I'm sorry Charlie but if my answer doesn't make
sense it is
because I am terribly distracted with real-life. Here's a link
that may
prove useful:

http://msdn.microsoft.com/en-us/library/ms683198(VS.85).aspx

"Bill Buckels" <bbuck... at (no spam) mts.net> wrote in message

news:gF9hm.148552$ZN.108959 at (no spam) newsfe23.iad...





"DMnDMr" <DMn2004... at (no spam) gmail.com> wrote:

Charlie wrote:

I don't know of any
way for WASP to set the keyboard focus without knowing the name
of
the that process. If you or anyone does know of another way I'd
like to hear about it.

I don't know about that,

Well, he might try GetModuleFileName after enumerating the open
Windows on
the desktop... I'm sorry Charlie but if my answer doesn't make
sense it is
because I am terribly distracted with real-life. Here's a link
that may
prove useful:

http://msdn.microsoft.com/en-us/library/ms683198(VS.85).aspx

Thanks for the suggestion Bill.  Unfortunately, after enumerating
open Windows, which WASP does, it has to determine which of the
Windows is AppleWin before it can do anything else.  It needs to do
this so it can obtain a handle.  Windows API calls usually need a
handle to identify the window.  For instance "SetFocus(handle)".
There are usually quite a few other (often invisible) Windows
running to search through looking for AppleWin.  You can see this
when you click on the "List Programs Running" function in WASP's
Tool menu.  Each line you see is a name of a process (Window) that
is running.  WASP compares each name to a list of known names from
the WASP.ini file until it finds a match.  If no match is found WASP
pops up a message saying "No Emulator Running!" (I suppose it should
say "No Supported Emulator Running!").  Version 1.14.2.0 of AppleWin
used, I believe, six different names.  One for each of the different
emulators (Apple //e, Apple II, Apple II+, etc.).  The idea was that
if new names were added (or another emulator adopted the same way of
pasting text) a WASP user could use the "List Running programs"
function to find the new name and edit the WASP.ini file and never
have to worry about it again (or at least until another new name was
added).  AppleWin 1.16.1.0 did add a new name, "Pravets 8M" and my
plan would have worked well with that but AppleWin also introduced
the addition of the video mode and the 50% scanlines into the name,
making I believe, 112 new name combinations.  Clearly not good for
WASP.  Ahh, "The best laid plans...".
As I mentioned in a previous post, my next release will have WASP
just comparing the seven names to the truncated AppleWin names.  It
seems to work.

Anyway, even though GetModuleFileName won't help me, your suggestion
did get me to wondering if maybe there is a better way to obtain
AppleWin's handle.  I will definitely look into that.

As for the other problem the original poster has, I can think of two
things that could cause what he is seeing.
1. The image he is opening is not a supported disk image type.
2. A bug in WASP that causes it to 'think' the disk image is just an
ordinary PC file.  Without any other information I will take a hard
look at the code but not being able to replicate the problem makes
it very hard to debug.

In any case I am considering using Michael J. Mahon's wastebasket
for my Open File dialog.  Re-writing the dialog as a completely new
control instead of trying to adapt Microsoft's standard control.
This has a lot to do with problems I'm seeing with WASP in Windows
7.

Charlie

As for the other problem the original poster has, I can think of
two
things that could cause what he is seeing.
1. The image he is opening is not a supported disk image type.
2. A bug in WASP that causes it to 'think' the disk image is just
an
ordinary PC file. Without any other information I will take a hard
look at the code but not being able to replicate the problem makes
it very hard to debug.

-------------------------------------------------------
Let me show you how to duplicate the problem I'm having:

------------------------------------------------------