AppleWin 1.18.0 (beta)
TomCh
I've uploaded a beta of 1.18 here:
http://prdownload.berlios.de/applewin/AppleWin1.18.0.0.zip
This fixes some recently reported problems and also adds support for
compressed images. I'm tagging it as beta, because there were fairly
big changes to the backend code for the compression support.
Cheers,
Tom
1.18.0 - 17 Jan 2010 (beta)
---------------------------
Changes:
. Added disk/harddisk image r/w support for .gz/.zip (and .2mg) files.
- Multi-zip archives are read-only.
. Added disk/harddisk eject sub-menu to Disk Config tab.
. Removed .bin registration.
Fixes:
. [Bug #16632] Fix cmd-line -d1/d2 switches with relative path
. Fix speaker volume when booting with -d1 switch
. Fix debugger bugs:
- Crash when doing: help *
- [Bug #16651] Crash when doing: run <script-file>
. [Bug #16652] Fix "Harddisk images aren't persisted when in different
folders"
johnsonlam
> I've uploaded a beta of 1.18 here:http://prdownload.berlios.de/applewin/AppleWin1.18.0.0.zip
Thanks Tom.
Will AppleWin extract the image on %TEMP%?
Will you consider a configurable path? (so I can use RAMdisk instead
of physical disk)
Rgds,
Johnson.
A2Pro
> I've uploaded a beta of 1.18 here:http://prdownload.berlios.de/applewin/AppleWin1.18.0.0.zip
> This fixes some recently reported problems and also adds support for
> compressed images. I'm tagging it as beta, because there were fairly
> big changes to the backend code for the compression support.
> ---------------------------
> Changes:
> . Added disk/harddisk image r/w support for .gz/.zip (and .2mg) files.
> - Multi-zip archives are read-only.
> . Added disk/harddisk eject sub-menu to Disk Config tab.
> . Removed .bin registration.
I can't find the disk/harddisk eject sub-menu.
> Fixes:
> . [Bug #16632] Fix cmd-line -d1/d2 switches with relative path
> . Fix speaker volume when booting with -d1 switch
> . Fix debugger bugs:
> - Crash when doing: help *
> - [Bug #16651] Crash when doing: run <script-file>
> . [Bug #16652] Fix "Harddisk images aren't persisted when in different
> folders"
I can confirm that numbers 16651 and 16652 have been squashed.
Thanks!!! But doing: run <script-file> is still behaving a bit oddly,
at least with my directory structure. I have an "E" directory on
drive "D:" with subdirectories for various systems. The Apple ]
[ stuff is in a directory named "aII". AppleWin 1.18.0 is now in a
directory named "AW.new". So, the full pathname for AppleWin is "D:\E
\aII\AW.new\applewin.exe". There's a file in the same directory named
"h.txt". If I enter 'run h.txt' in the debugger I get "Couldn't load
filename: D:\E\aII\DOS3.3\h.txt". I do have a directory named
"DOS3.3", a subdirectory of "D:E\aII". If I move "h.txt" from "D:E\aII
\AW.new\h.txt" to "D:E\aII\DOS3.3\h.txt" then entering 'run h.txt' in
the debugger works as expected.
Willi
TomCh
Hi,
What are the reasons for these requests?
The .gz or .zip file is only uncompressed to RAM within the Win32
(AppleWin) process (never externally to the PC's filing-system).
Tom
TomCh
Thanks for confirming & giving this new repro case. I've raised a new
bug here:
https://developer.berlios.de/bugs/?func=detailbug&bug_id=16688&group_id=6117
Tom
johnsonlam
Hi Tom,
> The .gz or .zip file is only uncompressed to RAM within the Win32
> (AppleWin) process (never externally to the PC's filing-system).
Well done Tom!
I'm afraid the disk image will extract to hard disk (lots of program
do this!).
I've got another hard disk died a weeks ago.
Rgds,
Johnson.
A2Pro
Recently a change was made in the debugger that affects the way 'G
xxxx' works. Now, in addition, to execution halting at address xxxx,
address xxxx now appears in the list of breakpoints. I really liked
the way 'G xxxx' used to work because it was a great way to execute a
small block of code. Now, having to delete the breakpoint added to
the list of breakpoints makes 'G xxxx' more trouble to use then it's
worth, IMHO.
Willi
TomCh
>
> Tom
OK, I had a quick look at this...
AppleWin is using the last .dsk image path as the base for "h.txt".
So you must have last used a .dsk from the DOS3.3 folder.
If I change the base path of the script to be the same path as
applewin.exe, this will solve your problem. How does that sound?
Tom
TomCh
OK - I'll raise a bug to not put a BP in the list.
Tom
A2Pro
On Jan 22, 5:17 pm, Tom wrote:
> OK, I had a quick look at this...
> AppleWin is using the last .dsk image path as the base for "h.txt".
> So you must have last used a .dsk from the DOS3.3 folder.
I have directories named "CPM", "DOS33", "HFS"and "UCSD", all
subdirectories of "aII". Recently, I've been accessing CP/M and Mac
images. It's been ages since I worked with a DOS 3.3 image. AHA,
just opened a 'Command Prompt' window and issued 'dir|more'. This
gives an unsorted listing of all files and directories in "aII".
"DOS33" is the first subdirectory in the "aII" directory.
BTW, if I enter 'run "D:\E\aII\H.txt"' I get "Couldn't load
filename: D:\E\aII\DOS33\D:\E\aII\H.txt"
> If I change the base path of the script to be the same path as
> applewin.exe, this will solve your problem. How does that sound?
My problem was solved when you fixed 'RUN'. Accessing the first
subdirectory is a quirk I can live with.
Again, thanks for all your efforts!!! Am now using AppleWin for
ALL of my Apple ][ development. The cross-assembler I have for my
Amiga 3000 allows very fast assembly of 6502 code but my A3000 can no
longer match the ability of my XP system with its 20 inch monitor to
edit multiple source files at the same time.
Willi
TomCh
Ah, yes: the absolute path should be honoured regardless of whatever
the CWD is set to for path-less scripts. I missed that from your
original post. I'll get that added.
Great to hear that you are using AppleWin exclusively for your dev
work!
Cheers,
Tom
A2Pro
'symuser load "filename.sym' works as expected. 'symuser load
filename.sym' does nothing.
Attempting to run 1.18.0 in Windows '98 got me a message about
needing a newer version of Windows.
Willi
TomCh
Thanks - bug report raised.
AppleWin definitely doesn't work on Win95 due to a dependency on a
newer version of DirectX. Win98 is probably in the same camp. TBH, I
now only test on XP and above.
Tom
A2Pro
Entering 'SYMUSER CLEAR' in the debugger clears MAIN.
Need a HELP update, how to load and/or clear 'Basic', 'Assembly',
'User1', 'User2', 'Src1', 'Src2'???
Willi
D Finnigan
>
> I would jump back into my 6502 projects if the debugger window was
> seperate.
>
I must agree. Having the debugger in Virtual II helped me *immensely* to
figure out what wasn't working in Xinu and what to fix. Now if only I could
alter the registers....
--
Mac GUI Vault - A source for retro Apple II and Macintosh
computing.
http://macgui.com/vault/
Michael
Sorry for the delayed reponse. The general format is
<SYMBOL_TABLE> <COMMAND>
e.g.
SYMMAIN CLEAR // Main/ROM
SYMBASIC CLEAR // Basic
SYMASM CLEAR // Assembly
SYMUSER CLEAR // User 1
SYMUSER2 CLEAR // User 2
SYMSRC CLEAR // Src 1
SYMSRC2 CLEAR // Src 2
I see that in the 1.19 RC they aren't working properly :-( I'll get the nightly build updated with a patch soonish.
> Need a HELP update,
Can you let me know if these still need a External or Internal help update please?
HELP SYMBOLS, HELP SYMMAIN, etc.
Cheers
Michael, AppleWin Debugger Dev