Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pcserver2!ddsw1!dattier From: dattier@ddsw1.MCS.COM (David W. Tamkin) Newsgroups: comp.sys.cbm Subject: Re: Reading SEQ files Message-ID: <1991Mar03.070459.27936@ddsw1.MCS.COM> Date: 3 Mar 91 07:04:59 GMT References: <13324@hubcap.clemson.edu> <1991Feb27.213545.18354@nntp-server.caltech.edu> <9678.27cd0f47@cc.newcastle.edu.au> Organization: Contributor Account at ddsw1, Wheeling, Illinois Lines: 31 c9037544@cc.newcastle.edu.au (David Williams) wrote in <9678.27cd0f47@cc.newcastle.edu.au>: | > The problem is, SEQ files can't be loaded like PRG files can. | Actually, it is possible. When using the SAVE and LOAD commands, just | inserting a ,s before the end quote in the filename will specify a SEQ file | rather than a PRG file. A USR file can be specified by using ,u. This could | be used a small way of protecting your programs from others, perhaps. That can be done as long as the file contains program data. If the purpose is to read the contents of a sequential file as text, loading "file,s" will get it into memory but won't be a good way to read it! (You can then examine memory with a machine language monitor but the formatting won't be very good, and you can come up with some screen code vs. character code and even ASCII vs. PETSCII problems, depending on the format of the stores file and the way the MLM displays memory locations.) And if you try to load it and list it, every PETSCII capital in the file will get expanded into whatever BASIC keyword uses that value as its token. What David Williams brought up can be done, but I don't think it's useful for the original poster's intentions. (I've responded in this thread to two other people who share my first name, and their last initials are my first two initials. Curious.) David Tamkin Box 7002 Des Plaines IL 60018-7002 708 518 6769 312 693 0591 dattier@ddsw1.mcs.com MCI Mail: 426-1818 CIS: 73720,1570 GEnie: D.W.TAMKIN "Parker Lewis Can't Lose" mailing list: write flamingo-request@ddsw1.mcs.com