Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
You are not logged in - nap
CSDb User Forums


Forums > C64 Coding > Disc command weirdness
2016-03-28 15:37
oziphantom

Registered: Oct 2014
Posts: 478
Disc command weirdness

So
open 2,8,2,"#2"
open 15,8,15,"U1 2 0 2 0"

works
open 2,8,2
print#2,"#2"
open 15,8,15,"U1 2 0 2 0"

doesn't
open 2,8,2,"#2"
open 15,8,15
print#15,"U1 2 0 2 0"

does

And the asm version of the BASIC operates the same as above.
Some quirk I'm missing to send the #2 over print/ffd2 is there something else I need to do ?
2016-03-28 16:38
Flavioweb

Registered: Nov 2011
Posts: 442
My guess:
PRINT# adds a new line after the command, OPEN don't?
What happen with "PRINT#2,"#2";"?
2016-03-28 19:38
soci

Registered: Sep 2003
Posts: 472
Buffers need to be _opened_ so that they get a channel assigned. You can't just open a channel and send stuff to it like "#2" and expect that now this buffer will be assigned to it.

If you open the buffer properly (as in the first variant) then you can use the channel to transfer data to/from it.

Don't confuse it with the command channel's behaviour, that's special.
2016-03-29 08:21
oziphantom

Registered: Oct 2014
Posts: 478
Ah ok so sending data post open is not the same as sending the filename during open. Thanks for clearing that up.

I guess once the channel is open, and it is used to pull data into the drives memory, it doesn't matter that the computer "forgets* the channel. I can just send more "U1 2 0 X X" to the drive, to make it pump more sectors into its memory?
2016-03-29 19:17
lA-sTYLe

Registered: Sep 2003
Posts: 63
I've been testing nearly the same with cmd drives but always needed to close the command channel beforet sending another command.

which reminds me a question

does there exist a burstloader that speeds up loading single sectors of a track for cmd drives, except using the Standart DOS commands?
2016-03-30 04:20
oziphantom

Registered: Oct 2014
Posts: 478
with a 1571 you don't need to close the Command Channel, you do need to do a JSR FFCC which is CLRLIN, just flushes stuff, and if you are sending via FFD2 you need to put a $0D carriage return on the end of the string.

Does the CMD support the U0 Burst commands? "U0"0,Track,Sector,num sectors,next sector Burst Command could do what you want. note that the params should be in binary not petascii like the other drive commands, not sure if you will be able to use a normal DOS load command to get the data though.
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
t0m3000/ibex-crew
Slimex
sailor/Triad
Asphodel
Freeze/Blazon
Mason/Unicess
pastbytes
master_hacker
Malmix/Fatzone
algorithm
Guests online: 317
Top Demos
1 Next Level  (9.8)
2 Mojo  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 No Bounds  (9.6)
6 Comaland 100%  (9.6)
7 Uncensored  (9.6)
8 The Ghost  (9.6)
9 Wonderland XIV  (9.6)
10 Bromance  (9.6)
Top onefile Demos
1 Party Elk 2  (9.7)
2 Cubic Dream  (9.6)
3 Copper Booze  (9.5)
4 Rainbow Connection  (9.5)
5 TRSAC, Gabber & Pebe..  (9.5)
6 Onscreen 5k  (9.5)
7 Dawnfall V1.1  (9.5)
8 Quadrants  (9.5)
9 Daah, Those Acid Pil..  (9.5)
10 Birth of a Flower  (9.5)
Top Groups
1 Booze Design  (9.3)
2 Nostalgia  (9.3)
3 Oxyron  (9.3)
4 Censor Design  (9.3)
5 Crest  (9.3)
Top Fullscreen Graphicians
1 Carrion  (9.8)
2 Joe  (9.8)
3 Duce  (9.8)
4 Mirage  (9.7)
5 Facet  (9.7)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.039 sec.