Okay, I know that (unfortunately) there is no fseek() available with cc65 on the c64 platform. So how do I implement random access files then? Is there a way to do it the old "REL file" way utilizing cbm_open / cbm_read / cbm_write ?! Any help will be apprecitated!!

_________________
LOAD ":*",8,1
READY.
RUN

i dont think REL files are supported, you could do it with direct t/s access ...

(and you really should ask this on the cc65 mailinglist =P)

_________________
http://hitmen.c02.at/html/tools_rr.html

hmm, that's the one method I tried to avoid so far ...



hmm... I guess those gurus have more important things to do than answer stupid newbie questions . But that's probably the only choice I have then ...

_________________
LOAD ":*",8,1
READY.
RUN

Is there a fseek equivalent in CBM DOS for non-REL files?

nope. REL files dont really allow fseek either

_________________
http://hitmen.c02.at/html/tools_rr.html

REL files let you read any record, which is close enough - you can just read and discard a few bytes to move to the proper position.

A little custom drive code would do the trick though. What are you working on?

Well, I'm working on a generic routine to take data in a struct e.g. an address record like this:

record_no: 1
name: tom
surname: thompson
phone: 1234

and write it to a file. the next record wil be appended to the existing file. If I want to change a single record, I just want to access and manipulate this particular record and not load the whole data (all records) into ram. with fseek this is not too complicated, but it gets complicated without it, me thinks ...

I'm just surprised that there is fread() and fwrite() but no ftell() and fseek() - for whatever reasons that is ...

_________________
LOAD ":*",8,1
READY.
RUN

the simple reason for fseek & friends not existent is that the cbm dos simply offers no way to alter the "file pointer" if you can speak of such a thing. i had a similar problem lately when writing some std libs for Power-C, and i could implement fseek(offs, SEEK_CUR) but that's all there is to do: skipping bytes. Everything else is simply not available (without going beyond DOS level) - for your application the normal way would be to read the whole file once, then do all modifications in RAM and at last write the whole stuff back to file - or: use REL files: they are predestined for your purpose and let you access each single record, but handling REL files is not quite easy, at least i never really dealed with'em, so i can't tell you more.

i made a whacked up half working fseek once.... basically skip bytes when seeking forward, and close/reopen/skip when seeking backwards. very ugly

_________________
http://hitmen.c02.at/html/tools_rr.html

@lodger: well in that case I think REL is your only friend in the C= realm

Yes, as RaveGuru says REL is the way to go. It's basically a simple database format, where you can read and edit any record at will.

Hmm... looks like I'll have to go back to BASIC after more than 16 years and check out REL file handling (using the examples in the 1541 drive manual) then. And I'll have to do it in (cc65) C afterwards.

Regarding my current project: I've written some code that makes up a small, simple and very lightweight "text adventure creator" (very, very simple!). It's far from being finished and currently all room and object data is stored in memory and then - after editing all data is done - written back to disk using cbm_write (just as hannez suggested). Unfortunately this takes a lot of time. If I split "editor" and "game engine" into two separate parts, this may be a useful workaround (until I know how to do the REL file stuff).

Anyway, thanks for helping me out here!

_________________
LOAD ":*",8,1
READY.
RUN

I would suggest working with a memory expansion for the editor. cc65 comes with drivers for the popular ones. After editing is done you can write down a packed file to disk. Doing read-only random access is, perhaps not easy, but at least a solved problem (i.e. IFFL loaders).