ah, so making the assignment to the scalar variable is the difference, vs
an array variable. they are in different memory areas.
thanks I think that is a clear answer.
On Tue, May 29, 2018 at 7:08 PM, Ken Pettit wrote:
> Hi Steve,
>
> The line:
>
> 20
Only an fm drive can make a tppd disc. Mfm can't
Do It.
https://en.m.wikipedia.org/wiki/Modified_Frequency_Modulation
Translation...a standard 3.5 drive can't work. But the idea of a program
to make a boot disc is possible provided you have a good Tpdd.
On Tuesday, May 29, 2018, Kevin
Unless the pictures on eBay are wrong, mine is definitely a TPDD.
On May 29, 2018, at 7:01 PM, Brian White wrote:
If what you have is a TPDD-2 and not a TPDD, I can supply a copy for
TPDD-2. Send me an address off-list and I'll mail it tomorrow.
Conversely I would like a copy for TPDD myself
Hi Steve,
Or rather "... fails becuase *F* is pointing to the old location for
A$(0)".
Ken
On 5/29/18 4:08 PM, Ken Pettit wrote:
Hi Steve,
The line:
20 F=VARPTR(A$(0)):*K*=256*PEEK(F+2)+PEEK(F+1)
Doesn't work because you take the value of VARPTR(A$(0)) and assign it
to F. But then you
It might also be possible to use something like the SuperCard Pro or Kyroflux
to copy the disk. As I understand it both use a standard PC disk drive and
control it directly and do a flux level copy of any disk (i.e. read flux
density from disk write same flux density to same place on another
Hi Steve,
The line:
20 F=VARPTR(A$(0)):*K*=256*PEEK(F+2)+PEEK(F+1)
Doesn't work because you take the value of VARPTR(A$(0)) and assign it
to F. But then you assign the value of K. This creates a new scalar
variable, causing A$(0) to be moved. So then the
"256*PEEK(F+2)+PEEK(F+1)" fails
If what you have is a TPDD-2 and not a TPDD, I can supply a copy for
TPDD-2. Send me an address off-list and I'll mail it tomorrow.
Conversely I would like a copy for TPDD myself if anyone is willing to
either make me one, or trust me with mailing me theirs and I'll mail it
back after making a
Ken, when I first read your code I said "That wont work and k(0) will be
wrong."
however it seems to work.
I cannot explain why your code works and my original code did not. I never
modify the string content.
-
your line:
20 FOR
A little deeper googling is leading me to believe there is a special
floppy_sys file on the utility disk that nobody has figured out how to
recreate. I'll try it anyway when it arrives but If that ends up being the
case, then I wonder if there is anyone on the list who would be willing to
make my
Steve,
Are you are trying to pre-calculate the addresses of the strings to save
time or something?
One thing to note is that the address of the A$() or D$() array variable
will move around in RAM. However, as long as you don't modify the
strings *in* the array after they are first
Ah that's a good question, is like to know also.
On Tue, May 29, 2018 at 3:29 PM Kevin Becker wrote:
> I don’t mean with a PC. I should already be able to use the drive via
> TS-DOS so I’m assuming I can just copy floppy.co to my M102 using
> desklink and then save it to the TPDD. I’m just
I don’t mean with a PC. I should already be able to use the drive via
TS-DOS so I’m assuming I can just copy floppy.co to my M102 using desklink
and then save it to the TPDD. I’m just wondering if that is good enough or
if there is some special boot sector magic necessary.
On May 29, 2018, at
I don't believe you can create one with a PC floppy controller. I'd buy a
copy off of someone is I could. For now, I'm planning on using the python
library on Linux box connected to the drive to create the disk. I'd much
rather just have the floppy.
On Tue, May 29, 2018 at 2:31 PM Kevin Becker
I've been watching eBay on and off for a TPDD or TPDD2 complete with cable
at a reasonable price for what feels like forever. I finally pulled the
trigger on one today but doesn't include the utility diskette.
I already have a REX with TS-DOS and I know how to bootstrap TEENY if
necessary, but
I read something last night that gave me the impression the moving array
thing applies to BASIC generally, not just the M100.
On Tue, May 29, 2018 at 11:56 AM, John R. Hogerhuis
wrote:
>
> On Tue, May 29, 2018 at 9:25 AM Stephen Adolph
> wrote:
>
>> John, I wasn't able to declare variables in
On Tue, May 29, 2018 at 9:25 AM Stephen Adolph wrote:
> John, I wasn't able to declare variables in any meaningful way to solve
> this problem. Only assignment seemed to work. Do you know a trick for that?
> steve
>
No I think you’re probably right, storage attaches and variables move when
you
Every once in a while a spam message makes it through to the list from a
subscribed member. Very rare. It appears at first glance that it was not
the subscribers intention to send it.
I’ve set the moderate bit on the account for now so any further spam should
not make it to the list.
I won’t
John, I wasn't able to declare variables in any meaningful way to solve
this problem. Only assignment seemed to work. Do you know a trick for that?
steve
On Tue, May 29, 2018 at 12:21 PM, John R. Hogerhuis
wrote:
>
> On Tue, May 29, 2018 at 5:13 AM Jeffrey Birt
> wrote:
>
>> >>> Anytime a new
On Tue, May 29, 2018 at 5:13 AM Jeffrey Birt wrote:
> >>> Anytime a new scalar (i.e. non-array) variable is created, the
> addresses of the array variables must all change to make room for the new
> scalar variable.
>
>
>
> So BASIC copies all the arrays to a new memory address? That does not
On 5/29/18 5:13 AM, Jeffrey Birt wrote:
>>> Anytime a new scalar (i.e. non-array) variable is created, the
addresses of the array variables must all change to make room for the
new scalar variable.
So BASIC copies all the arrays to a new memory address? That does not
seem very efficient.
>>> Anytime a new scalar (i.e. non-array) variable is created, the addresses of
>>> the array variables must all change to make room for the new scalar
>>> variable.
So BASIC copies all the arrays to a new memory address? That does not seem very
efficient.
Jeff
From: M100 On
The manual mentions something to this effect. What is tricky is
understanding when it works and when it breaks.
As a rule, if every variable used in a program is assigned once before
using VARPTR then you are for sure safe.
I guess using VARPTR with array variables complicates things.
On Tue,
http://put.icestudioonline.com
Paul F
23 matches
Mail list logo
