Studio 6..1 and Windows XP

[Reg Paling]

Hi Doug,

There is a note on the TL website at 
http://www.tigerlogic.com/tigerlogic/omnis/products/studio/sysreq.jsp 
which says Studio 6.1 requires Windows 7, Windows 2008 or above. Then it 
says it is "likely to run" on earlier versions, but it isn't tested.

It would be very handy to know exactly what features are not available 
on the earlier versions, and why.  If we had that information we could 
make informed recommendations to our customers.

Cheers,
Reg


On 31/03/2015 8:54 am, Doug Easterbrook wrote:
> hi Mischa:
>
> thats perfect -- its a technical reason that 32 bit Studio 6.1 can't run.    Although, a little google says that the issue is resolved in update1 of the visual runtime for 2012 -- which lets you compile for XP.
>
> http://stackoverflow.com/questions/13130713/how-to-compile-for-win-xp-with-visual-studio-2012
>
>
> thank you.
>
> we have a fair number of customers using 32 bit win 2003 R2 server (I know, not xp), but I suspect that will come to end of life as well even if all our other things still run on it.
>
> Doug Easterbrook
> Arts Management Systems Ltd.
> mailto:doug at artsman.com
> http://www.artsman.com
> Phone (403) 536-1205    Fax (403) 536-1210
>
>> On Mar 30, 2015, at 2:43 PM, Mischa <mischa at omnislab.com> wrote:
>>
>> Hi Doug,
>>
>> straight forward - no. Does not work. Omnis.exe needs the jump address
>> GetTickCount64 that is not provided in Kernel32.dll of XP (tried it with
>> 32bit version, of course).
>>
>> Hth
>> Mischa
>>
>> ---------------------------------------------------
>>   T H E   O M N I S   L /\ B     www.omnislab.com
>> ---------------------------------------------------
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: omnisdev-en [mailto:omnisdev-en-bounces at lists.omnis-dev.com] Im Auftrag
>> von Doug Easterbrook
>> Gesendet: Montag, 30. März 2015 18:49
>> An: OmnisDev List - English
>> Betreff: Re: Studio 6..1 and Windows XP
>>
>> hi Bas:
>>
>> it is a straight forward technical question -- 'can it be done'?
>>
>> Knowing the complete lay of the land regarding technical options is
>> important and I want to find out if its an arbitrary decision placed into
>> the installer, or a *real life* technical limitation.
>>
>>
>> I'm not interested in 'well you shouldn't because.... (insert your
>> technical, moral or philosophical reason why not)'.
>>
>>
>> I'd like my customers to move forward and I have forced progress on them in
>> some cases.    There are things we no longer support because our hand was
>> forced, but if:
>> - I do not have to force my hand
>> - it is not hurting my support team
>> - it is limited extra work on our behalf
>> - and the client expresses a desire
>>
>> then I'll keep compatibility with older operating systems or database
>> versions around unless I absolutely must have a feature that cannot be
>> backward supported at limited expense
>>
>> I prefer to keep my development tools at a defined level.   If studio 6.1
>> cuts me from XP support, using the register/calldll -- thats something to
>> know -- and I can make a decision.
>>
>> the very last thing I want to say to customers is...   sorry, I cannot help
>> you because I wont.    I'd prefer to say, you can continue on your path you
>> chose (i.e. XP),  but we recommend, as soon as you can, to put money into
>> your budget to buy a machine that only runs windows 10 and hate it....
>>
>>
>> sadly, both OSX (yes I love Mac) and Windows (hasn't been good customer
>> experiences) are migrating to overprotection.    Yosemite hasn't been the
>> best OS for running applications on.  I don't want to force customers to go
>> places that they don't want to go to.
>>
>>
>>
>> hence..   is it possible???  anybody tried it??
>>
>>
>> Doug Easterbrook
>> Arts Management Systems Ltd.
>> mailto:doug at artsman.com
>> http://www.artsman.com
>> Phone (403) 536-1205    Fax (403) 536-1210
>>
>>> On Mar 29, 2015, at 7:43 PM, Bastiaan Olij <bastiaan at basenlily.me> wrote:
>>>
>>> The big question I have is "why". XP is dead. It's leaking like a
>>> basketcase and leaving your business open to a myriad of risks. You
>>> never know what changes TL has made to move the product forward that
>>> will break parts of your code that you haven't found yet.
>>
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
>>
>>
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com

_____________________________________________________________
Manage your list subscriptions at http://lists.omnis-dev.com