Start.SBP
8 messages in this thread
Have you done any research on the problem I noted here with the START.SBP
problem some weeks ago? To recap, the START.SBP program which is supposed
to be executed automatically is not executed if the SUPERBASE.INI file is
present in the S: directory. Bill Roberts in Ellettsville In. via Whap!
This problem has been corrected in the Beta 1.2 version. NOTE: this is
still in beta-test.
Regards, Whap!penned…
Pat @Oxxi (310) 427-1227
Glad to hear that the Start.SBP problem will be corrected. Will 1.2 be a
patch available here, or will it require an order by mail?
Bill Roberts in Ellettsville In. via Whap!
Most likely it will need to be ordered from here and shipped through the
mail. By the way, in the process of testing the Start.sbp file for the
Runtime Module, I noticed that when I launched the regular SBpro4, it also
started using the Start.sbp. That's the standard 1.01 version on my Tech
Support machine — the Start.sbp file was in the same directory. Moving it
to a different directory was all it took to keep it from being used in the
launch. Any chance the Start file is just in the wrong place?
Regards, Whap!penned…
Pat @Oxxi (310) 427-1227
>> Any chance the start file is just in the wrong place?
I am not sure about the actions you are describing, or about your question.
But here is an experiment I am running while typing this message. From a
started shell started from DirectoryOpus, I did a cd to the directory
data:medical. In that directory is a data base of medical bills, and a
program called start.sbp. I loaded SB4 (with the command
prod:superbasepro4/sbpro4). SB started and waited for me to enter a
command. When I asked to open a file, I was in the directory specified by
S:superbase.ini (data:). I entered a go command for a program (in case the
start.sbp program had loaded, but not run. I got the open program
requester. I selected start.sbp in the directory data:medical. I got the
screen setup that should have come up automatically at startup. (Note:
Data: and Prod: are assigns to various directories on my hard disk)
Incidently, I just did a status, and it shows conclip, arq (the requester
program), and wwwwtimer (from Who, What, When, Where) running. My startup
sequence does not start any jobs running, except DirectoryOpus, which is
currently running in the background. I also am running DisDF, to quiet my
floppies.
I have 512 K of chip memory and 2.5 meg of ram, and a 105 meg Quantum in a
Trumpcard 500.
Bill Roberts in Ellettsville In. via Whap!
Yay, Bill!
That's the kind of assessment tech support people _love_ to see — a
complete rundown of the environment in which the problem occured. Okay,
now it's over to me.
What I suggest you try as a test is copying the start.sbp file into the
same directory with the Superbase program. (It should specify complete
paths for any files to be opened.) Launch the program by cd'ing to the
directory in which Superbase resides, then giving the execution command.
The start.sbp operations should work, if my experience is any indication.
Then copy the start.sbp file to the data: "root" directory (outside the
medical directory), and launch the program as you indicated doing in your
message. This may also work, though I haven't tried it — again, any files
opened by the start.sbp operation should be completely specified with path
and filename.
I'll be interested in a report about what happens.
Regards, Whap!penned…
Pat @Oxxi (310) 427-1227
I ran the test that you suggested, plus a few more. First, I tried the
start.sbp file in the same directory as the sb4 program. You said that the
program started for you. Mine didn't. Then I moved the program to my
DATA: directory, where I set sb4 start directory. The start.sbp program
did start.
I also tried a second experiment to see if a local Superbase.ini file would
overwrite a global one. I made a backup to S:Superbase.ini (always a wise
move when dinking with important files). I then changed my start directory
to data:medical and moved the .ini file to data:medical. I did a cd to
data:medical, and started sb4. (I have no S:superbase.ini, but do have
data:medical/Superbase.ini. There is a sb4 program data:medical/start.sbp.
) I now start sb4. The start program runs, but the settings are the
default settings (British pounds for money, dates are default settings,
etc.). That is, the local Superbase.ini file is ignored.
One last experiment: I removed the file name from the start directory. The
program did start.
Conclusion: If a directory is listed in the start option, the start.sbp
program must be in that directory. If no directory is listed, the current
directory is used. The documentation says only the the current directory
is used. Given a vote, I would say that the program should check the local
directory. If there is a start.sbp, run it. Otherwise, go to the start
directory.
Thanx for your assistance.
Bill Roberts in Ellettsville In. via Whap!
Thanks for your assessment — I agree, the local directory should be
checked. I'll pass on the suggestion to Mike.
Regards, Whap!penned…
Pat @Oxxi (310) 427-1227