Here's some follow up information regarding the use of port 2 vs. port 3 when archiving. This information explains the reason the backup objects show as different types by the 50G filer when reviewed (either type HPDIR on port 2 or type BCKUP on port 3).
This information is from John Meyers and originally posted on the comp.sys.hp48 user group....
What a "backup object" really is:
(this "geek speak" can be skipped without harm :)
The original HP48 RAM cards needed a way to name each object, and to know its length, so *any* object stored into a "port" (except a library, which already has a similar format) is first put inside a wrapper, which is called a "backup" object, not referring to "backing up my calculator," but rather to being anything stored in a RAM card.
However, whenever any object is _recalled_ from these places (or its info is reported by the Filer), the wrapper is automatically removed, and only the original object itself is seen,
which in the case of HOME is just an ordinary directory.
So when an archive is first made to a calculator port (:0: thru :2:) and then copied to SD or saved from Emu48, it is just a calculator directory, not enclosed within a "backup" object. When any directory is copied
to a real port (:0: thru :2:) it there becomes a "backup object" again, at least inside the port itself, in the eyes of the RESTORE command.
An SD card is not considered an actual "port," however, because it is an "external disk" that can also hold non-calc, foreign objects; thus "external" storage (:IO:xxxxx ARCHIVE and :3:xxxxx ARCHIVE)
are the only places that one can ever catch an object whose type actually says "backup," because STO and RCL otherwise transparently "wrap" and "unwrap" the actual inner objects,
as they enter and leave ports, without our ever noticing.
...thanks John Meyers for the explanation
This information is from John Meyers and originally posted on the comp.sys.hp48 user group....
What a "backup object" really is:
(this "geek speak" can be skipped without harm :)
The original HP48 RAM cards needed a way to name each object, and to know its length, so *any* object stored into a "port" (except a library, which already has a similar format) is first put inside a wrapper, which is called a "backup" object, not referring to "backing up my calculator," but rather to being anything stored in a RAM card.
However, whenever any object is _recalled_ from these places (or its info is reported by the Filer), the wrapper is automatically removed, and only the original object itself is seen,
which in the case of HOME is just an ordinary directory.
So when an archive is first made to a calculator port (:0: thru :2:) and then copied to SD or saved from Emu48, it is just a calculator directory, not enclosed within a "backup" object. When any directory is copied
to a real port (:0: thru :2:) it there becomes a "backup object" again, at least inside the port itself, in the eyes of the RESTORE command.
An SD card is not considered an actual "port," however, because it is an "external disk" that can also hold non-calc, foreign objects; thus "external" storage (:IO:xxxxx ARCHIVE and :3:xxxxx ARCHIVE)
are the only places that one can ever catch an object whose type actually says "backup," because STO and RCL otherwise transparently "wrap" and "unwrap" the actual inner objects,
as they enter and leave ports, without our ever noticing.
...thanks John Meyers for the explanation
--- In 50g@yahoogroups.com, "pin224466" <pin224466@...> wrote:
>
> with some other help, what I discovered is that the DIR object created on port 2 of the emulator CAN be used with RESTORE if you do one of the following....
>
> 1... if you transfer the dir object to the 50G on an SD card, all you need to do is use the FILER to copy or move the DIR object from the SD card to Port2. Now restore from port...:2:'filename.hp' ENTER RESTORE
>
> 2. if you use conn4x to transfer the dir object to the HOME directory, use the filer to either copy or move the object to port 2 and again restore from the port....:2:'filename' ENTER RESTORE
>
>
>
> --- In 50g@yahoogroups.com, "nate.beers" <natebeers@> wrote:
> >
> >
> > --- In 50g@yahoogroups.com, "pin224466" <pin224466@> wrote:
> >
> > >
> > > How do I archive the emulator and transfer it back to the 50G?
> > >
> >
> > If you use ARCHIVE to create a backup and store it in port 1 or 2, it
> > will be a DIR object . If you store th backup in port 3, it will be a
> > BCKUP object which can be used with the RESTORE command. The
> > directories can not. You can recall the driectory to the stack and use
> > Edit --> Save Object to save the directory to your pc and then transfer
> > that to you 50g . You would then have to save that DIR into a variable,
> > and then use the filer to move everything out of the newly created
> > directory to your home directory.
> >
> > If you install a null-modem emulator on your computer, you can connect
> > to emu48 and use the backup/restore function of Conn4x. Connect to your
> > 50g via USB using Conn4x and create a backup. Disconnect the 50g and
> > connect to Emu48 and restore the backup of your 50g. Or vice versa.
> >
> > See EMU48 Printing here <http://sense.net/%7Eegan/virtual82240b/> for
> > more info about installing a null-modem emulator.
> >
>