>Or, if POSE would hunt in the current directory when it found the
>specified path to be invalid.
If Poser can't find the ROM file, it falls back and looks in both the same
directory as the .psf file and the same directory as the Poser executable
for a ROM file with the same name as the required one. From the Release
notes:
* On the Mac, session files contain references to their associated
ROM files via aliases. On Windows, the references are stored as
full pathnames. This is old news. What's new is that if either of
these mechanisms fails to find the ROM file, Poser now looks first
in the same directory as the session file for a ROM file with the
same name, and if that fails looks in Poser's own directory for a
ROM file with the same name.
Your suggestion of acception both a -psf and a -rom switch on the command
line is an interesting one; I'll look into it.
-- Keith Rollin
-- Palm OS Emulator engineer
[EMAIL PROTECTED] on 05/28/99 09:07:48 AM
Please respond to [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (Keith Rollin/HQ/3Com)
Subject: Re: Quick Emulator Question
Nathan --
Assuming that you are referring to the Windows version, POSE (including the
latest 21b28) remembers the location of the ROM as an absolute file
location,
i.e., drive letter and complete path. Moving your files doesn't update the
entry in the .psf file. If you set up the directory on the demo machine to
be
the same as the source machine you copied from, then everything looks the
same
to POSE and it'll run.
If yo can't, for example, your POSE directory is on drive D: and the demo
machine doesn't have a drive D:, you can always recreate the environment
by
moving the files mentioned and everything else loaded into the psf ( .prcs,
.pdbs )
An alternative would be if the command line options added in 21b28 would
accept
both a -psf and a -rom entry and use the specified rom instead of the one
from
the psf file, but I couldn't get it to work when I tried before sending
this
message. Or, if POSE would hunt in the current directory when it found the
specified path to be invalid. But since neither of these are in place, the
first two (same directory structure, or transfer and rebuild) are your
options.
Hope this helps.
-- John Kinast
Nathan Gold <[EMAIL PROTECTED]> on 05/28/99 10:11:31 AM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: (bcc: John Kinast/IGT)
Subject: Quick Emulator Question
Hello!
I have been very successful at loading the PalmOS emulator with my
application and it runs beautifully! However, I am trying to get it
running
on someone else's machine and I am stuck. Every time I try to run it on
another machine, the emulator tells me that the rom I am using is not there
(and it is)!
The files I have transferred are emulator.exe, emulator_profile.exe,
PalmIII.rom, and the palmts.psf file.
I am trying to get a demo up by this afternoon. Any help would be greatly
appreciated.
Nathan
