| AppleWin - change to minimum Windows version [message #387161] |
Wed, 18 September 2019 16:28  |
TomCh
Messages: 242
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
Just a note to say that currently AppleWin (1.29.x) is built with Visual Studio 2008, so should run on Windows 2000 (although I only ever test on Win7 & Win10).
In the coming months, we'll look to migrate to a newer Visual Studio, and at the same time switch to Windows XP as the minimum Windows version it should run on (but then I'll only test mainly on Win10 and occasionally on Win7).
btw. there was related discussion over on csa2, in "Ciderpress windows architecture 32 or 64?" (link: https://groups.google.com/d/msg/comp.sys.apple2/K1_3C9tKVOo/ D5b4MD7WAAAJ).
The (then legacy) 1.29.x versions will still be available at https://github.com/AppleWin/AppleWin, for anyone needing them for older OS's (but obviously won't continue to be maintained).
Tom
|
|
|
|
| Re: AppleWin - change to minimum Windows version [message #387164 is a reply to message #387161] |
Wed, 18 September 2019 21:34  |
|
|
Originally posted by: James Davis
On Wednesday, September 18, 2019 at 1:28:43 PM UTC-7, TomCh wrote:
> Just a note to say that currently AppleWin (1.29.x) is built with Visual Studio 2008, so should run on Windows 2000 (although I only ever test on Win7 & Win10).
>
> In the coming months, we'll look to migrate to a newer Visual Studio, and at the same time switch to Windows XP as the minimum Windows version it should run on (but then I'll only test mainly on Win10 and occasionally on Win7).
>
> btw. there was related discussion over on csa2, in "Ciderpress windows architecture 32 or 64?" (link: https://groups.google.com/d/msg/comp.sys.apple2/K1_3C9tKVOo/ D5b4MD7WAAAJ).
>
> The (then legacy) 1.29.x versions will still be available at https://github.com/AppleWin/AppleWin, for anyone needing them for older OS's (but obviously won't continue to be maintained).
>
> Tom
When you abandoned the 16-bit Windows (<= Win-98SE or maybe Win-ME) versions of AppleWin, you put a note to that effect in the last viable version that would run on those O.S.es. I hope you will do the same this next time.
Please keep testing for Windows 7 viability. I am too old to learn a new O.S. !!!
|
|
|
|
| Re: AppleWin - change to minimum Windows version [message #387166 is a reply to message #387164] |
Thu, 19 September 2019 16:15 |
|
|
Originally posted by: Bobbi Webber-Manners
On Wednesday, 18 September 2019 21:34:29 UTC-4, James Davis wrote:
> On Wednesday, September 18, 2019 at 1:28:43 PM UTC-7, TomCh wrote:
>> Just a note to say that currently AppleWin (1.29.x) is built with Visual Studio 2008, so should run on Windows 2000 (although I only ever test on Win7 & Win10).
>>
>> In the coming months, we'll look to migrate to a newer Visual Studio, and at the same time switch to Windows XP as the minimum Windows version it should run on (but then I'll only test mainly on Win10 and occasionally on Win7).
>>
>> btw. there was related discussion over on csa2, in "Ciderpress windows architecture 32 or 64?" (link: https://groups.google.com/d/msg/comp.sys.apple2/K1_3C9tKVOo/ D5b4MD7WAAAJ).
>>
>> The (then legacy) 1.29.x versions will still be available at https://github.com/AppleWin/AppleWin, for anyone needing them for older OS's (but obviously won't continue to be maintained).
>>
>> Tom
>
> When you abandoned the 16-bit Windows (<= Win-98SE or maybe Win-ME) versions of AppleWin, you put a note to that effect in the last viable version that would run on those O.S.es. I hope you will do the same this next time.
>
> Please keep testing for Windows 7 viability. I am too old to learn a new O.S. !!!
Even a new ProDOS?
|
|
|
|
| Re: AppleWin - change to minimum Windows version [message #387167 is a reply to message #387166] |
Thu, 19 September 2019 22:40 |
|
|
Originally posted by: James Davis
On Thursday, September 19, 2019 at 1:15:19 PM UTC-7, Bobbi Webber-Manners wrote:
> On Wednesday, 18 September 2019 21:34:29 UTC-4, James Davis wrote:
>> On Wednesday, September 18, 2019 at 1:28:43 PM UTC-7, TomCh wrote:
>>> Just a note to say that currently AppleWin (1.29.x) is built with Visual Studio 2008, so should run on Windows 2000 (although I only ever test on Win7 & Win10).
>>>
>>> In the coming months, we'll look to migrate to a newer Visual Studio, and at the same time switch to Windows XP as the minimum Windows version it should run on (but then I'll only test mainly on Win10 and occasionally on Win7).
>>>
>>> btw. there was related discussion over on csa2, in "Ciderpress windows architecture 32 or 64?" (link: https://groups.google.com/d/msg/comp.sys.apple2/K1_3C9tKVOo/ D5b4MD7WAAAJ).
>>>
>>> The (then legacy) 1.29.x versions will still be available at https://github.com/AppleWin/AppleWin, for anyone needing them for older OS's (but obviously won't continue to be maintained).
>>>
>>> Tom
>>
>> When you abandoned the 16-bit Windows (<= Win-98SE or maybe Win-ME) versions of AppleWin, you put a note to that effect in the last viable version that would run on those O.S.es. I hope you will do the same this next time.
>>
>> Please keep testing for Windows 7 viability. I am too old to learn a new O.S. !!!
>
> Even a new ProDOS?
Currently, I am using JB's latest safe version.
|
|
|
|
| Re: AppleWin - change to minimum Windows version [message #387169 is a reply to message #387167] |
Thu, 19 September 2019 23:36 |
|
|
Originally posted by: Bobbi Webber-Manners
On Thursday, 19 September 2019 22:40:38 UTC-4, James Davis wrote:
> On Thursday, September 19, 2019 at 1:15:19 PM UTC-7, Bobbi Webber-Manners wrote:
>> On Wednesday, 18 September 2019 21:34:29 UTC-4, James Davis wrote:
>>> On Wednesday, September 18, 2019 at 1:28:43 PM UTC-7, TomCh wrote:
>>>> Just a note to say that currently AppleWin (1.29.x) is built with Visual Studio 2008, so should run on Windows 2000 (although I only ever test on Win7 & Win10).
>>>>
>>>> In the coming months, we'll look to migrate to a newer Visual Studio, and at the same time switch to Windows XP as the minimum Windows version it should run on (but then I'll only test mainly on Win10 and occasionally on Win7).
>>>>
>>>> btw. there was related discussion over on csa2, in "Ciderpress windows architecture 32 or 64?" (link: https://groups.google.com/d/msg/comp.sys.apple2/K1_3C9tKVOo/ D5b4MD7WAAAJ).
>>>>
>>>> The (then legacy) 1.29.x versions will still be available at https://github.com/AppleWin/AppleWin, for anyone needing them for older OS's (but obviously won't continue to be maintained).
>>>>
>>>> Tom
>>>
>>> When you abandoned the 16-bit Windows (<= Win-98SE or maybe Win-ME) versions of AppleWin, you put a note to that effect in the last viable version that would run on those O.S.es. I hope you will do the same this next time.
>>>
>>> Please keep testing for Windows 7 viability. I am too old to learn a new O.S. !!!
>>
>> Even a new ProDOS?
>
> Currently, I am using JB's latest safe version.
I have been alpha testing the new one (2.5.0) and I don't know how we ever managed without "PREFIX .."
|
|
|
|
| Re: AppleWin - change to minimum Windows version [message #387244 is a reply to message #387169] |
Sat, 21 September 2019 16:46 |
Michael J. Mahon
Messages: 1767
Registered: October 2012
Karma: 0
|
Senior Member |
|
|
Bobbi Webber-Manners <bobbi.manners@gmail.com> wrote:
> On Thursday, 19 September 2019 22:40:38 UTC-4, James Davis wrote:
>> On Thursday, September 19, 2019 at 1:15:19 PM UTC-7, Bobbi Webber-Manners wrote:
>>> On Wednesday, 18 September 2019 21:34:29 UTC-4, James Davis wrote:
>>>> On Wednesday, September 18, 2019 at 1:28:43 PM UTC-7, TomCh wrote:
>>>> > Just a note to say that currently AppleWin (1.29.x) is built with
>>>> > Visual Studio 2008, so should run on Windows 2000 (although I only
>>>> > ever test on Win7 & Win10).
>>>> >
>>>> > In the coming months, we'll look to migrate to a newer Visual Studio,
>>>> > and at the same time switch to Windows XP as the minimum Windows
>>>> > version it should run on (but then I'll only test mainly on Win10 and
>>>> > occasionally on Win7).
>>>> >
>>>> > btw. there was related discussion over on csa2, in "Ciderpress
>>>> > windows architecture 32 or 64?" (link:
>>>> > https://groups.google.com/d/msg/comp.sys.apple2/K1_3C9tKVOo/ D5b4MD7WAAAJ).
>>>> >
>>>> > The (then legacy) 1.29.x versions will still be available at
>>>> > https://github.com/AppleWin/AppleWin, for anyone needing them for
>>>> > older OS's (but obviously won't continue to be maintained).
>>>> >
>>>> > Tom
>>>>
>>>> When you abandoned the 16-bit Windows (<= Win-98SE or maybe Win-ME)
>>>> versions of AppleWin, you put a note to that effect in the last viable
>>>> version that would run on those O.S.es. I hope you will do the same this next time.
>>>>
>>>> Please keep testing for Windows 7 viability. I am too old to learn a new O.S. !!!
>>>
>>> Even a new ProDOS?
>>
>> Currently, I am using JB's latest safe version.
>
> I have been alpha testing the new one (2.5.0) and I don't know how we
> ever managed without "PREFIX .."
>
I always loaded the “cd” ProCmd to get this functionality. Nice to have it
built-in. ;-)
--
-michael - NadaNet 3.1 and AppleCrate II: http://michaeljmahon.com
|
|
|
|
| Re: AppleWin - change to minimum Windows version [message #387253 is a reply to message #387244] |
Sat, 21 September 2019 20:28 |
|
|
Originally posted by: Bobbi Webber-Manners
On Saturday, 21 September 2019 16:46:56 UTC-4, Michael J. Mahon wrote:
> Bobbi Webber-Manners wrote:
>> On Thursday, 19 September 2019 22:40:38 UTC-4, James Davis wrote:
>>> On Thursday, September 19, 2019 at 1:15:19 PM UTC-7, Bobbi Webber-Manners wrote:
>>>> On Wednesday, 18 September 2019 21:34:29 UTC-4, James Davis wrote:
>>>> > On Wednesday, September 18, 2019 at 1:28:43 PM UTC-7, TomCh wrote:
>>>> >> Just a note to say that currently AppleWin (1.29.x) is built with
>>>> >> Visual Studio 2008, so should run on Windows 2000 (although I only
>>>> >> ever test on Win7 & Win10).
>>>> >>
>>>> >> In the coming months, we'll look to migrate to a newer Visual Studio,
>>>> >> and at the same time switch to Windows XP as the minimum Windows
>>>> >> version it should run on (but then I'll only test mainly on Win10 and
>>>> >> occasionally on Win7).
>>>> >>
>>>> >> btw. there was related discussion over on csa2, in "Ciderpress
>>>> >> windows architecture 32 or 64?" (link:
>>>> >> https://groups.google.com/d/msg/comp.sys.apple2/K1_3C9tKVOo/ D5b4MD7WAAAJ).
>>>> >>
>>>> >> The (then legacy) 1.29.x versions will still be available at
>>>> >> https://github.com/AppleWin/AppleWin, for anyone needing them for
>>>> >> older OS's (but obviously won't continue to be maintained).
>>>> >>
>>>> >> Tom
>>>> >
>>>> > When you abandoned the 16-bit Windows (<= Win-98SE or maybe Win-ME)
>>>> > versions of AppleWin, you put a note to that effect in the last viable
>>>> > version that would run on those O.S.es. I hope you will do the same this next time.
>>>> >
>>>> > Please keep testing for Windows 7 viability. I am too old to learn a new O.S. !!!
>>>>
>>>> Even a new ProDOS?
>>>
>>> Currently, I am using JB's latest safe version.
>>
>> I have been alpha testing the new one (2.5.0) and I don't know how we
>> ever managed without "PREFIX .."
>>
>
> I always loaded the “cd” ProCmd to get this functionality.. Nice to have it
> built-in. ;-)
>
> --
> -michael - NadaNet 3.1 and AppleCrate II: http://michaeljmahon.com
Yes the ProCMDs are pretty handy. 2.5.0 has ONLINE built-in too.
The other one I find handy is PATH, but it is probably better to have these as loadable extras like ProCMD rather than builtins. RAM is scarce!
|
|
|
|
|
|
Members
Search
Help
Register
Login
Home
