Marcel,
Please, carry on! There are always people who lack appreciation for what
you're trying to do.
As the changes are more than cosmetic, I do think you should change the
name to TK3 or something. People have a long history and set of
expectations from TK2. Your changes are very worthwhile.
Am 31.03.2017 um 17:13 schrieb Marcel Kilgus:
> Peter Graf wrote:
>>> It's fairly easy to built new versions, so nobody is stopping anybody
>>> to make different releases. I do this for my own amusement, mostly.
>> If mostly for your amusement, one more reason to give your stuff a
>> different
Peter Graf wrote:
>> It's fairly easy to built new versions, so nobody is stopping anybody
>> to make different releases. I do this for my own amusement, mostly.
> If mostly for your amusement, one more reason to give your stuff a
> different name. Not the traditional TK2 ROM, where major QL
Yes networking is QLs every day work.
> Am 31.03.2017 um 16:55 schrieb Peter Graf :
>
> Marcel Kilgus wrote:
>> pg...@q40.de wrote:
>>> The network code is an essential of the ROM version. If removed, I
>>> would not call the result TK2 ROM anymore.
>>
>> Well, I do ;-)
>> [Snip]
Marcel Kilgus wrote:
> pg...@q40.de wrote:
>> The network code is an essential of the ROM version. If removed, I
>> would not call the result TK2 ROM anymore.
>
> Well, I do ;-)
> [Snip]
>
> It's fairly easy to built new versions, so nobody is stopping anybody
> to make different releases. I do
Thanks for the feedback. Are there people badly missing the network
code in the new TK2, i.e. is this still a thing?
Very.
That's why I didn't try the new TK2. I use networking often.
On the other hand, I have Minerva ROM, and trying to avoid using of
mdv_'s at all, so I don't need the
I would rather chain-load some other, non-critical commands from disk than
refraining from the network server and client in ROM.
But just my 2 cents. No worries.
Tobias
> Am 31.03.2017 um 14:03 schrieb Marcel Kilgus :
>
> pg...@q40.de wrote:
>>> Thanks for the
pg...@q40.de wrote:
>> Thanks for the feedback. Are there people badly missing the network
>> code in the new TK2, i.e. is this still a thing?
>
> Depends on ROM or RAM.
>
> The network code is an essential of the ROM version. If removed, I
> would not call the result TK2 ROM anymore.
Well, I do
On 31/03/2017 12:22, pg...@q40.de wrote:
On 31 Mar 2017 at 12:12, Marcel Kilgus wrote:
Fabrizio Diversi wrote:
if someone is wondering, Tk2 2.31 is perfectly working also in Mist (at
least as far as I can see:-))
Thanks for the feedback. Are there people badly missing the network
code in the
On 31 Mar 2017 at 12:12, Marcel Kilgus wrote:
> Fabrizio Diversi wrote:
> > if someone is wondering, Tk2 2.31 is perfectly working also in Mist (at
> > least as far as I can see:-))
>
> Thanks for the feedback. Are there people badly missing the network
> code in the new TK2, i.e. is this still
Here.
The one single reason why I would not use your new TK2 over the traditional one.
My QLs and QXLs are all networked, one of them is diskless and thus depends on
the network.
Otherwise: very good job bringing TK2 and SMSQ/E to the same code base!
Tobias
> Am 31.03.2017 um 12:12 schrieb
Fabrizio Diversi wrote:
> if someone is wondering, Tk2 2.31 is perfectly working also in Mist (at
> least as far as I can see:-))
Thanks for the feedback. Are there people badly missing the network
code in the new TK2, i.e. is this still a thing?
Cheers, Marcel
Ciao,
if someone is wondering, Tk2 2.31 is perfectly working also in Mist (at
least as far as I can see:-))
Fabrizio
On 27/03/2017 00:31, Marcel Kilgus wrote:
I just uploaded a version with the fix for the CDEC$ bug. Also I
noticed that the sources were not complete, this is fixed, too,
I just uploaded a version with the fix for the CDEC$ bug. Also I
noticed that the sources were not complete, this is fixed, too, along
with including Jan's conditional assembly trick to get both versions
without altering the source code.
https://www.kilgus.net/2017/03/19/toolkit-ii-the-sequel/
14 matches
Mail list logo