CO files only have a fixed location to run from. You're not trying to run
it, just transfer it from a saved RAM image.
CO files as files in the file system move around as files are created,
deleted, change in size. Just like BA files and DO files.
Now "trigger files" are a horse of a different co
Maybe because of CO files' fixed memory locations and the fact that I
changed the amount of RAM in the machine?
On Sun, Mar 8, 2020, 15:10 John R. Hogerhuis wrote:
> I wonder why CO files didn't copy. There are three kinds of files, DO, CO
> and BA. Unless Steve says otherwise I'd think the copy
Phones... I didn't stroke out.
-- John.
On Sun, Mar 8, 2020, 12:09 PM John R. Hogerhuis wrote:
> I wonder why CO files didn't copy. There are three kinds of files, DO, CO
> and BA. Unless Steve says otherwise I'd think the copy feature should work
> with all three. Maybe a bug.
>
>
> -- Just h
I wonder why CO files didn't copy. There are three kinds of files, DO, CO
and BA. Unless Steve says otherwise I'd think the copy feature should work
with all three. Maybe a bug.
-- Just hj.
>
No, it's not on my PC. I was able to load the files out of the 24K RAM
image onto the T102, and then make a new 32K RAM image on the REX
containing the files I care about.
I was going to re-load .CO programs like HTERM from my PC, since those
didn't copy out of the RAM image successfully.
On Sat,
Does it? I guess I must have done that then ;)
On Saturday, March 7, 2020, Josh Malone wrote:
> Well, you could always load it into virtual t and use it. But the REXMGR
> file copy function works fine for extracting files from RAM images
> regardless of the size.
>
> On Sat, Mar 7, 2020, 2:20 P
Well, you could always load it into virtual t and use it. But the REXMGR
file copy function works fine for extracting files from RAM images
regardless of the size.
On Sat, Mar 7, 2020, 2:20 PM Stephen Adolph wrote:
> now that a 24k ram image is out of REX and onto your pc, what are you
> going t
now that a 24k ram image is out of REX and onto your pc, what are you going
to do now?
REX can't read a 24K ram image into a 32k Machine. Unless I am losing my
memory, which could be true.
On Sat, Mar 7, 2020 at 1:58 PM Alex ... wrote:
> So all I cared about really is the .DO and .BA files, whi
So all I cared about really is the .DO and .BA files, which REXMGR copied
out of the backup just fine. Thanks Josh! Not sure why I didn't think to
try that...
I tried to copy a .CO file out and it didn't work, but that's not really a
surprise. I can reload that one from my PC.
On Sat, Mar 7, 2020
I actually don't think there is a way for REX to figure that out.
I would save off the files you want while the computer has its original
memory config.
Then upgrade the ram, and reload in it.
..Steve
On Sat, Mar 7, 2020 at 6:08 AM Josh Malone wrote:
> You can copy individual files out of a RAM
You can copy individual files out of a RAM image using REXMGR. I think it's
the "file" function. They get copied into working RAM.
On Fri, Mar 6, 2020, 11:05 PM Alex ... wrote:
> Hey M100 list,
> I've had a T102 with a REX for a few years and I finally got around to
> stuffing another 8k RAM chi
Can you export the backups using TSDOS, load them into Virtual T, and then
pull the individual files back in?
I realize that's a lot of work
Tom Wilson
wilso...@gmail.com
(619)940-6311
K6ABZ
On Fri, Mar 6, 2020 at 8:05 PM Alex ... wrote:
> Hey M100 list,
> I've had a T102 with a REX fo
Hey M100 list,
I've had a T102 with a REX for a few years and I finally got around to
stuffing another 8k RAM chip into it to get 32K. That's great and all, but
now I can't restore any of my REX backups because the RAM size doesn't
match.
Is there any way to trick this thing into restoring the bac
13 matches
Mail list logo
