Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
another question about files
#11
Knowing you too have the manual reassures me. This gives us a safety net in case Glenn's manual is destroyed by some catastrophe. Big Grin
Antoni
Reply
#12
The manual that I have is MS Quickbasic 4.0. I found it more informative than 4.5, 5.0, etc. manuals that I had. I also have a GW-Basic manual which I seldom use anymore.
*****
Reply
#13
Man!!! Where do you get those manuals????

Error codes especially at compile time. ;*)

Re: Seek. How does it work? I mean I've used it extensively but I don't knoe the low-level stuff.

I would like to assume it does this:

INT21h...

Openfile

Mov cx, byte displacement
then
read sequentially until it hits the offset.

Pls. tell me if I'm wrong.

Glenn, Moneo?
y smiley is 24 bit.
[Image: anya2.jpg]

Genso's Junkyard:
http://rel.betterwebber.com/
Reply
#14
"reads sequentially until it hits the offset". What offset? SEEK just positions the file pointer, which is what determines where file I/O functions access the file at. (I would imagine that SEEK simply uses the DOS function of INT 21 that positions file pointers.)
ravelling Curmudgeon
(geocities sites require copying and pasting URLs.)
I liked spam better when it was something that came in a can.
Windows should be defenestrated.
Reply
#15
Manuals: Some I actually bought. Some I asked for when the company was throwing them out. This is pretty common. You may end up with an older manual, but it's better than none.

I don't understand what you mean about the error codes at compile time. If you mean looking up the error codes in the manual, well, I never have to resort to the manual for this. Usually the compiler error message is sufficient.

I honestly don't know the internals of how the SEEK works. If you're really interested, write a little prog that does SEEK, and look at the guts with DEBUG.
*****
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)