[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ADTPro 1.2.0 Released

David,
Thanks very much ... as you may see put a question last night about it on sourceforge forums !!
May I have not mention before, so, really good job with ADTPro, in my list of new technology/methods for ours beloved ancient machines your software is on the top of my list, helped me bring a ][+ to life and spark the flame on me to get a //GS. 

Tks and keep going with the grat job

Regards,

Leandro

David Schmidt escreveu:

On 1/14/2012 11:33 AM, David Schmidt wrote:

This release, contrary to its ".0" suffix, isn't revolutionary - I just
ran out of digits in the mod level counter before I came up with
anything extraordinary to release. This is a collection of bug fixes and
general useability improvements.

There's growing interest in 64-bit Windows, and the RXTX dll for that
platform wasn't working correctly - so I sourced a build from our
friends at cloudhopper (http://www.cloudhopper.com/opensource/rxtx/)
that has been beta tested by several folks.

http://adtpro.sourceforge.net

1.2.0 - January 14, 2012

Bug fixes:

* [Server] Integrate Cloudhopper's 64-bit Windows RXTX dll - fixes
2-way Windows 7 64-bit serial communications

* [Server] If a serial configuration isn't usable, it doesn't just
put up the dialog box saying you should change the configuration
- it brings up the change configuration dialog so you can
actually do it

* [Server] Be consistent when automatically adding file suffixes
(.dsk vs. .DSK)

* [Client] Don't lock out interrupts during program execution - it
hinders things like the GS Desk Accessory bringup

* [Client] Apple /// responds a little better to "disk switched"
notifications like those produced by the CFFA300 card

* [Client] Apple /// Ethernet screen layout was missing DHCP
configuration option


Thanks as always for your kind words of encouragement.
One additional feature I failed to mention - Leandro Polimeno requested a way to start a server in a particular mode automatically. That is in this version - invoking the start script (adtpro.sh, adtpro.bat) with the name of your communications mode of choice activates that configuration. I.e. 
'adtpro ethernet'
starts up the server with the Ethernet button "pushed." You just use the name of the button in your native language (as it appears on the button itself).