This is topic Editing Autoexec.bat file with MS-DOS in forum Film-Yak at Film-Tech Forum ARCHIVE.
To visit this topic, use this URL:
https://ft-forum.com/ft/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic;f=8;t=001458
Posted by Paul G. Thompson (Member # 655) on 11-17-2002, 12:05 PM:
First, the Prelude...So far, I have lost some hair trying to get a MS-DOS 6.22 based computer to boot up and load a program automatically, and I have not been successful. I tried a bunch of command lines I thought would work, and on each boot-up attempt, the computer hurled an insult at me, or locked me out of the autoexec.bat file unless I edited through the DOS directory. The computer has no programs in it with the exception of DOS and the program I am trying to load at boot-up. The program I speak of is a DOS-based program, and it works perfectly when I load it manually.
Immediately after MS-DOS 6.22 is installed (no memmaker initiated), the Autoexec.bat file looks like this:
@ECHO OFF
C:\DOS\SMARTDRIV.EXE /X
PROMPT $p$g
PATH C:\DOS
SET TEMP: C:\DOS
Secondly, the program I want to load on bootup is called SETUPVRC which is the name of the directory. In this directory, there is a bat and a cfg file called KBRC.bat and KBRC.cfg
I want to insert a line in the Autoexec.bat file to load this program because this program is used to take transmitter parameter readings, log the file, and print it out on a printer. If there is a power outage, the computer will come back only on DOS prompt when the power is back on line and the program has to be initiated manually. Obviously, this is not satisfactory.
Third:
My question is, what is the command line I should insert in the Autoexec.bat file, and where should I insert it? 
The Operations manual for the software says it can be done, but there is no suggestion as to what or where the command line sequence is supposed to be. 
I contacted Gentner Electronics, and was told they signed over the software to another company. I called that company and they appear to have "Banker's Hours."
I sent them an email, and I suspect I won't get a reply fast enough to suit my needs.
Thanks for the suggestions, gentlemen. If you have a suggestion, please clue me in. Don't be concerned if your suggestion might fail. No matter how bad it lunches the program, I can get it running in less that 10 minutes. I have a spare computer to experiment with.
Posted by Daryl C. W. O'Shea (Member # 1303) on 11-17-2002, 12:16 PM:
I don't believe that's the command for smartdrive, if I remeber right it's smartdrv.exe (8 characters).
try this:
Posted by David Stambaugh (Member # 1102) on 11-17-2002, 12:21 PM:
"locked me out of the autoexec.bat file unless I edited through the DOS directory". What exactly do you mean? Are you using the DOS "edit" utility to edit the autoexec.bat file? I can't imagine why it wouldn't work unless there is some piece of the edit utility missing. If I remember correctly, for edit to run you should have 6 related files in the DOS directory:edit.com
edit.hlp
edit.pif
qbasic.exe
qbasic.hlp
qbasic.ini
I would suggest modifying the PATH command to:
PATH=C:\DOS;C:\SETUPVRC
As for the command you want to insert at the end of the autoexec.bat file to run the application, it's probably
c:\setupvrc\kbrc.bat
Only you might have to use a "call" in the command line, like:
call c:\setupvrc\kbrc.bat
Or as Daryl suggested, change the default directory first, then run the batch file:
cd c:\setupvrc
kbrc.bat
Hope this helps at least some. 
Posted by Daryl C. W. O'Shea (Member # 1303) on 11-17-2002, 12:31 PM:
You only have to use call if you want to return to the calling batch file. Since kbrc.bat is the last thing to be run you don't need to call it. Using call would actually tie up a bit of extra memory unnecessarily (although very little).
You should also change to the directory (using: cd\setupvrc) before calling the programs batch file incase it just assumes it is starting from its directory. If it doesn't make sure it is in its directory first it won't be able to find its resource files as it will use c:\ as it's working directory.
Those are indeed the six files required for edit.com.
If you don't have them you can still create batch files by typing this:
Posted by Paul G. Thompson (Member # 655) on 11-17-2002, 03:17 PM:
Daryl, that was a typo on my part for the Smartdrv.exe 
OK, I'll try your suggestions when I get home to my experimental computer. Right now, I have a more serious problem. The RFPA's in the driver cabnet burned up the plate load choke. No parts to fix it. 
Just happens I have a vacuum tube 10KW Collins that was made in 1964, and the RFPA's in the driver cabnet happens to be a pair of 4-400's in parallel running at Class "C" Bias. If I get a chance, I'll post a picture of it (or what's left of it) later. I suspect a "bottle" shorted out and blew the choke before it could blow itself off line, or I lost the bias.
As far as being "Locked out" of the MS-DOS editor, I had to log into the DOS directory and type "Edit c:\ autoexec.bat" in order to get back into it.
I'll post the results on the autoexec.bat file as soon as I try it.
Thanks, guys. Much appreciated.
Posted by Paul G. Thompson (Member # 655) on 11-18-2002, 01:58 AM:
Daryl, your command line worked.
I then went back to the kbrc.bat file, and added "+a" (without the quotation marks, naturally) which bypasses the the password and sets the program into "Activate Terminal Mode."
Now, if I put the right answers in when I orginally ran "Install", the damn thing should work. I'll know tomorrow for sure when I make the test run in the real world.
Thanks alot.
to you at Sho West.
While orginally trying to get it to boot up automatically, I felt like I was getting
by the computer and the damn program.
(I just had to try one of Brad's new Graemlins...)
Posted by Daryl C. W. O'Shea (Member # 1303) on 11-18-2002, 02:01 AM:
I've been getting
by multiple computers all night long (and that 24HR period between the two nights).

Now if only Showest wasn't right at the end of the semester (if I'm not mistaken).
Posted by Paul G. Thompson (Member # 655) on 11-18-2002, 02:16 AM:
David, I am not sure why I was locked out. I think I didn't load DOS because of a typo when I was screwing around in there. Once I got that line right, I was no longer locked out. It happened twice when I was trying to "call", and when I was adding it to the Path C: line.
Posted by Mike Blakesley (Member # 26) on 11-18-2002, 01:05 PM:
Who ever said DOS was dead??
Posted by Daryl C. W. O'Shea (Member # 1303) on 11-18-2002, 07:12 PM:
I like DOS.
D.O'Shea
Posted by Paul G. Thompson (Member # 655) on 11-18-2002, 07:50 PM:
Daryl, it worked in real life, too....except for one insignificant detail. That being, if I let it load with the +a in the KBRc.bat string, the stupid modem does not know how mant times it is supposed to let the phone ring before it picks up.
The kbrc.bat file looks like this:
setupvrc KBRC.CFG -1 /2400 +a +h +fwhite +bblack +tblack "at"
The number of rings the modem want to hear before it picks up is set in a menu "activate Terminal mode" in the modem commands dialog. When the number of rings are selected, then is supposedly set.
I will send you a zip file of the program which includes the operations.doc - the entire program is very small.
The people who handle the program never responded to a phone call or an email. If you looked things over and make some suggestions, I will be very greatful.
Posted by Daryl C. W. O'Shea (Member # 1303) on 11-18-2002, 08:01 PM:
No problem, it's probably something in the modem init string. AT commands... what are those again?
BTW, how many times do you want it to ring?
Posted by Paul G. Thompson (Member # 655) on 11-18-2002, 08:18 PM:
Daryl, if I understand it correctly, "at" is all that is needed. But obviously, that is not correct. That's why I included the operations manual in the zip file.
We only want it to ring once before the modem picks up.
Thank you
Posted by Jack Ondracek (Member # 1466) on 11-18-2002, 08:54 PM:
That Gentner's a pretty decent remote control, Paul. I used it here when I had part of one of the local stations.
Posted by Paul G. Thompson (Member # 655) on 11-19-2002, 02:09 AM:
Jack, indeed they are! They have a limited vocabulary, though.
Daryl, I didn't get a chance to try the modem string you recommended, as the other transmitter blew a capacitor. I was off the air for a couple of hours before I got one running again. I still have the Collins out of service. It blew a coil because of lost RFPA bias supply.
But, I'll give your recommendation a try tomorrow...I am sure it will work. I'll let you know via email how it turned out. Again, thatn you - your expertise so far has proved to be invaluable,as Brad knows with the update of FT, and from what I know of your astonishingly rapid replys that seem to work!
Now it is time to
Jeeze, what a day! Had a sound system
in one of our theatres, too.
When it rains, it pours!!
Posted by Daryl C. W. O'Shea (Member # 1303) on 11-19-2002, 02:34 AM:
I'm sure that the modem will answer, whether or not the program notices the modem answers is anybody's guess.
Sounds like you're just having all the fun.
At least I can just ignore Brad's emails.
Stupid, stupid
cookies... why can't you just behave!
Posted by Daryl C. W. O'Shea (Member # 1303) on 12-31-2002, 06:57 PM:
Try this init string Paul, I've tested it with my good ol' analog phone line and it works on my laptop.