home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Hot Shareware 35
/
hot35.iso
/
ficheros
/
NUTI
/
4NT301.ZIP
/
_4INST.BTM
(
.txt
)
next >
Wrap
4DOS Compressed Batch-To-Memory File
|
1998-02-02
|
22KB
|
958 lines
@*echo off
*setlocal
*unalias *
setdos /g.,
on errormsg goto on_error
on break goto on_break
goto start
text > nul
_4INST.BTM -- 4DOS, 4OS2, and 4NT Self-Install
Copyright 1998, JP Software Inc., All Rights Reserved.
Author: Tom Rawson Last Revision: January 29, 1998
This file is used to install a downloaded copy of 4DOS, 4OS2, or 4NT.
It performs basic installation functions once, then renames itself so it
will not be run automatically a second time.
DO NOT MODIFY THIS FILE UNLESS INSTRUCTED TO DO SO BY OUR SUPPORT STAFF.
We cannot provide support for the installation process if you have
modified the installation batch file!
The primary functions provided by this file are:
* Check that required files appear to have been extracted OK,
and perform other similar tests for proper version, operating
system, etc.
* Locate the previous copy of the product, if any.
* If there was a previous copy:
- Copy over the old .INI and 4START files.
- Update the old .INI file for the new path, and (in 4DOS) remove
the old HelpPath directive and replace it with InstallPath.
- Allow branding of the new version if appropriate.
* For 4DOS:
- Update CONFIG.SYS so the SHELL= line points to the new version
- Update AUTOEXEC.BAT to include KEYSTACK (except in Win95).
- If running in OS/2, start an OS/2 .CMD file to create a desktop
folder for 4DOS.
- If running in Win95, create a shortcut for 4DOS, and add registry
extensions.
* For 4OS2:
- Call a REXX script to update CONFIG.SYS (updates OS2_SHELL, COMSPEC,
BOOKSHELF, DPATH, and LIBPATH).
- Call a REXX script to create a desktop object for 4OS2.
* For 4NT:
- If running in NT 4.0+, create a shortcut for 4NT, and add registry
entries.
endtext
:start
if %_dos eq DOS if %_4ver ge 6.0 goto verok
if %_dos eq OS2 if %_4ver ge 3.0 goto verok
iff %_dos eq WIN95C .or. %_dos eq WIN98C then
set _dos=NT
cls
text
4NT is not designed to run under Windows 95, and we do not recommend
installing it there. For a native Windows 95 version of our command
line tools use 4DOS, our DOS command processor with full Windows 95
and long filename support.
(This is a one-time message which will not be repeated.)
endtext
set qq=Y
goto exit_noretry
endiff
if %_4ver ge 3.0 goto verok
endiff
cls
text
This automated installation batch file is for use under 4DOS 6.0 or
above, 4OS2 3.0 or above, or 4NT 3.0 or above. It will not work for
other products, or earlier versions.
endtext
pause
goto done
:verok
setdos /c%=^
setdos /p%=&
setdos /e%=
cls
if "%_jprr" eq "Y" goto pathok
echo.
echo.
echo Welcome to 4%_dos!
echo.
echo This installation procedure is run automatically the first time
echo you start a new downloaded or trial copy of 4%_dos. It is written
echo entirely in the 4%_dos batch language.
echo.
echo If you are new to 4%_dos, this procedure will install 4%_dos on your
echo system. No system files will be modified without your permission.
echo.
echo If you already have a previous version of 4%_dos installed, this
echo procedure will copy the settings (4%_dos.INI and 4START) and
echo registration information (if available) from the previous version,
echo and -- after requesting your permission -- will update the
echo appropriate configuration files.
echo.
echo If you have already installed this new version of 4%_dos, or prefer to
echo perform the installation manually as described in the 4%_dos.TXT file, you
echo can exit now, and this installation program will not be run again.
echo.
inkey /k"yn" Proceed with installation (Y/N)? %%yn
if "%yn" ne "Y" goto exit_noretry
iff %_dos eq DOS then
if %@len["%@full[%0]"] lt 150 goto pathok
echo.
echo The 4DOS directory name is too long for automated installation.
goto fatalerr
endiff
:pathok
cdd "%@path["%@full[%0]"]" || (echo Cannot switch to the product directory! %+ goto fatalerr)
iff not exist 4%_dos.%@if[%_dos eq DOS,com,exe] then
cls
echo.
echo The 4%_dos automated installation batch file is not in the
echo directory where the product files are stored. Please put all
echo the new 4%_dos files in the same directory and try again.
goto done
endiff
iff %_dos eq DOS .and. (%_env lt 512 .or. %_alias lt 256) then
iff "%_jprr" eq "Y" then
exit 16
else
text
=========================================================================
The free environment or alias space is not adequate for automated
installation. The installation software will start a temporary copy of
4DOS with larger environment and alias space, and try again.
endtext
pause
set _jprr=Y
.\4dos.com //envfree=768 //alias=%@eval[%_alias + 384] /c "%@full[%0]" %&
unset /q _jprr
iff %? eq 16 then
text
=========================================================================
The free environment or alias space is still inadequate for automated
installation.
endtext
goto fatalerr
else
goto done
endiff
endiff
endiff
alias fatalerr `(echo %& %+ goto fatalerr)`
alias wait `echo. %+ pause Press any key to continue ...`
alias yesno `echo. %+ inkey /k"yn" %2& (Y/N)? %%%1`
alias retry `(beep %+ iff "%2&" ne "" then %+ echo. %+ echo %2& %+ endiff %+ goto %1)`
alias insthelp `pushd %+ .\insthelp.exe %& %+ set result=%? %+ popd`
alias callrexx `pushd %+ call %& %+ set result=%? %+ popd`
alias instinf `pushd %+ %instinf %& %+ popd`
alias sep `echo. %+ echo %@repeat[%1,72] %+ echo.`
alias clear `cls %+ echo. %+ echo.`
set reltype=%4
set product=4%_dos
set cd=%_cwds
if %product eq 4DOS .or. %product eq 4OS2 set cd=%@upper[%cd]
set instinf=rem
iff %product eq 4DOS then
iff %_win ge 40 then
set cd=%@sfn["%cd"]
set instinf=rundll.exe
if "%windir" ne "" .and. exist "%windir\rundll.exe" set instinf=%windir\rundll.exe
set instinf=%instinf setupx.dll,InstallHinfSection DefaultInstall 132
endiff
elseiff %product eq 4NT .and. %_dosver ge 4.00 then
set instinf=%SystemRoot\System32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132
endiff
set majordate=6405
set newbdate=6405
switch %product
case 4DOS
set reqfiles=4DOS.COM OPTION.EXE 4HELP.EXE 4DOS.HLP INSTHELP.EXE
set exefile=4DOS.COM
set batext=BTM BAT
set opsys=DOS
if %_win ge 40 set opsys=Windows 95
case 4OS2
set reqfiles=4OS2.EXE JPOS2DLL.DLL KEYSTACK.EXE OPTION2.EXE 4OS2.INF 4OS2H.MSG JPOS2INS.CMD
set exefile=4OS2.EXE
set batext=BTM CMD
set opsys=OS/2
option //execwait=Yes
case 4NT
set reqfiles=4NT.EXE 4NT.HLP 4NT.CNT SHRALIAS.EXE INSTHELP.EXE
set exefile=4NT.EXE
set batext=BTM CMD BAT
set opsys=Windows NT
option //execwait=Yes
endswitch
for %f in (%reqfiles) if not exist %f (set errname=%f %+ goto missing_file)
goto filesok
:missing_file
sep =
echo The %errname file is missing. This file is required to install %product.
echo Please check that all downloaded files were placed in the same directory.
goto nonfatalerr
:filesok
clear
echo This procedure installs %product version %_4ver.
yesno pver Are you currently using an earlier version of %product on your system
if "%pver" ne "Y" goto noprev
:getpdir
sep -
echo Please enter the directory where your previous
input version of %product is installed: %%prevdir
set prevdir="%prevdir"
iff %product eq 4DOS .and. %_win ge 40 then
set prevdir=%@sfn[%prevdir]
endiff
set slashdir=prevdir
gosub addslash
if not isdir %prevdir retry getpdir That is not a valid directory
iff not exist %[prevdir]%exefile then
echo This directory does not appear to contain a previous version of
echo %product. Please try again.
retry getpdir
endiff
set prevdate=%@date[%@filedate[%[prevdir]%exefile]]
set majorupg=%@if[%prevdate lt %majordate,Y,N]
set newbrand=%@if[%prevdate ge %newbdate,Y,N]
unset prevdate
clear
echo Your current %product.INI, 4START, and 4EXIT files (if any) will now be
echo copied from the previous %product directory. If these files already
echo exist in the new %product directory you will be prompted for whether to
echo replace the file in the new directory with the file from the old
echo directory.
echo.
yesno yn Copy the %product.INI, 4START, and 4EXIT files
iff "%yn" eq "Y" then
:: Copy the files
if exist %[prevdir]%[product].ini copy %[prevdir]%[product].ini .\
for %f in (4START 4EXIT) for %e in (%batext) if exist %[prevdir]%f.%e copy %[prevdir]%f.%e .\
:: Update paths in INI file
iff exist %product.INI then
sep -
echo Paths in the new copy of %product.INI will now be updated to point to your
echo new %product directory. The old .INI file will be saved as %product.JPS.
echo If you do not allow this update, you must perform it manually, or %product
echo may not work properly.
iff %product eq 4DOS then
echo.
echo During the update process any old HelpPath directive will be removed from
echo 4DOS.INI (this directive is now obsolete), and an InstallPath directive
echo will be added.
endiff
yesno yn Update %product.INI
set jptemp=%@filename["%@unique[.]"]
iff "%yn" eq "Y" then
iff %product eq 4OS2 then
callrexx jpos2ins.cmd "4OS2" "%cd" "UpdateINI" "4OS2.INI" "%jptemp"
else
insthelp IniFile /d"%cd" /o"%product.INI" /t"%jptemp"
endiff
iff %result eq 0 then
copy %product.INI %product.JPS > nul
copy %jptemp %product.INI > nul
else
sep -
echo Paths in %product.INI could not be updated due to the above error. Be sure
echo to manually update any settings in %product.INI which point to the %product
echo directory. If you do not, %product may not work properly.
endiff
wait
endiff
del /q %jptemp > nul
endiff
else
sep -
echo You chose not to copy existing startup files from your previous %product
echo directory. You may want to copy these files manually at a later time,
echo and update them for the new version.
wait
endiff
clear
if "%reltype" eq "P" goto trialver
echo The next part of the installation process varies depending on whether
echo you own a purchased or "registered" version of %product, as opposed to a
echo trial or "shareware" version.
yesno yn Are you upgrading from a previously purchased copy of %product
if "%yn" ne "Y" goto trialver
iff %newbrand eq Y then
:: Previous version is 6.0 / 3.0 or later
iff %majorupg eq Y then
:: Major update, order is probably required
sep -
echo The installation software has determined that you are installing a
echo major update to %product (as opposed to a minor or maintenance update).
echo.
echo Normally such updates must be purchased; please contact JP Software
echo or your dealer for details. If you order an upgrade you can use the
echo trial version while you wait for your upgrade to arrive.
echo.
echo If you believe you are eligible for a free registered copy of this
echo version even though it is a major update (for example, because you
echo purchased a special offer which included the next version), you can try
echo to "brand" %product with your name and serial number manually; for
echo instructions see the README.TXT file. If branding fails with the
echo message "Contact JP Software or your dealer for an upgrade" then you
echo must purchase the upgrade.
goto branddone
endiff
:: Minor update
iff %product eq 4DOS then
:: Minor update to 4DOS, try to brand it
sep -
echo The installation software has determined that you are installing a
echo minor or maintenance update to 4DOS. This portion of the installation
echo process will assist you in "branding" this update with your name and
echo serial number.
iff exist %[prevdir]br4dos.exe then
yesno yn Brand the new version of 4DOS with your name and serial number
iff "%yn" eq "y" then
copy /u %[prevdir]br4dos.exe
do forever
.\br4dos.exe
if %? eq 0 leave
echo.
yesno yn Branding failed ... try again
if "%yn" ne "Y" leave
enddo
endiff
else
:: Oops, missing brand program.
wait
sep -
echo You cannot brand 4DOS now, because the BR4DOS program from the previous
echo version is not available in your old 4DOS directory.
echo.
echo The installation process will continue with the downloaded trial version.
echo To brand this version at a later time, see the README.TXT file.
endiff
else
:: Minor update to 4OS2 / 4NT
:: If 4OS2, copy JPCONFIG.INI
if (%product eq 4OS2 .and. exist %[prevdir]jpconfig.ini) copy /u %[prevdir]jpconfig.ini .\ > nul
sep -
echo The installation software has determined that you are installing a
echo minor or maintenance update to %product. The "branding" (name and
echo serial number) information should already be stored on your system,
echo and will be transferred automatically to the new version.
echo.
echo If the information does not transfer properly, or you need to
echo reinstall your branding information for any other reason, see the
echo manual branding instructions in the README.TXT file.
echo.
endiff
else
:: Updating from 5.5 / 2.5 or earlier
sep -
iff %product eq 4DOS then
text
This portion of the installation process will assist you in "branding"
4DOS with your name and serial number. Branding the program converts it
from a trial (shareware) copy to one registered to you.
You are only eligible to brand this upgrade if your FIRST purchase of
4DOS was a version 5.5 or later diskette, and you are upgrading to
version 6.0. If your original purchase was for version 5.0 or earlier,
or you obtained 4DOS on our CD Suite, in most cases you must purchase
the version 6.0 upgrade (once you order the upgrade you can continue to
use this trial version until your order arrives). For more information
on upgrades see PRODUCTS.TXT and UPGFORM.TXT.
Branding also requires the brand program and brand information (name,
serial number, and validation code) from 4DOS 5.5 or later. If you are
eligible for the upgrade at no charge but have lost your brand
information, contact JP Software to obtain a replacement (there is a
small charge for this service).
endtext
iff exist %[prevdir]brand.exe then
yesno yn Brand the new version of 4DOS with your name and serial number
iff "%yn" eq "y" then
copy /u %[prevdir]brand.exe
do forever
.\brand.exe
if %? eq 0 leave
echo.
yesno yn Branding failed ... try again
if "%yn" ne "Y" leave
enddo
endiff
else
wait
sep -
text
You cannot brand 4DOS now because the BRAND program from the previous
version is not available in your old 4DOS directory.
The installation process will continue with the downloaded trial
version. To brand this version at a later time, see the instructions
in the README.TXT file.
endtext
endiff
else
echo This portion of the installation process provides information on
echo "branding" the new version of %product with your name and serial number.
echo.
echo This section is informational only; you cannot actually brand %product now
echo because it is in use (to run this installation batch file), and
echo %opsys does not allow running programs to be modified. For manual
echo branding instructions see the README.TXT file.
echo.
echo You will only be eligible to brand this upgrade if your FIRST purchase
echo of %product was a version 2.5 or later diskette, and you are upgrading
echo to version 3.0. If your original purchase was for version 2.0 or
echo earlier, or you obtained %product on our CD Suite, in most cases you
echo must purchase the version 3.0 upgrade (once you order the upgrade you
echo can continue to use this trial version until your order arrives). For
echo more information on upgrades see PRODUCTS.TXT and UPGFORM.TXT.
echo.
echo Branding will also require the brand program and brand information
echo (name, serial number, and validation code) from %product 2.5 or later.
echo If you are eligible for the upgrade at no charge but have lost your
echo brand information, contact JP Software to obtain a replacement (there is
echo a small charge for this service).
endiff
endiff
:branddone
wait
goto doconfig
:noprev
iff %product eq 4DOS then
echo [4DOS] >! 4DOS.INI
echo InstallPath = %cd >>! 4DOS.INI
endiff
:trialver
sep -
iff "%reltype" eq "P" then
:: Pre-release
echo You may use this pre-release version of %product until the date stated
echo in the signon message when the program starts, or in the README.TXT or
echo other similar file which came with the pre-release.
echo.
echo After that time you must upgrade to or purchase the final release under
echo our standard license terms. This pre-release version may be difficult
echo to use or cease to operate properly after the date shown in the signon
echo message or documentation.
echo.
echo See the license agreement in the file LICENSE.TXT for complete details.
else
:: Shareware
echo You may use this new trial version of %product for up to 21 days while
echo evaluating it. After that time you must purchase %product if you continue
echo to use it. See our license agreement in the file LICENSE.TXT for
echo complete details.
endiff
wait
:doconfig
if %product eq 4NT goto configdone
set csname=%_boot:\CONFIG.SYS
set csbak=%_boot:\CONFIG.JPS
set csmod=N
clear
echo The installation process updates CONFIG.SYS to load your new copy of
echo %product as the default %opsys command processor. You have three choices:
echo.
echo - Update the system CONFIG.SYS file. This is the recommended method
echo and will fully install %product on your system. Your previous
echo CONFIG.SYS file will be saved as CONFIG.JPS.
echo.
echo - Make a copy of CONFIG.SYS in the %product directory and update that
echo copy, instead of the "real" CONFIG.SYS file. This allows you to
echo review the changes before implementing them. If there is already a
echo copy of CONFIG.SYS in the %product directory it will be renamed CONFIG.JPS.
echo.
echo - Skip the CONFIG.SYS update. In this case you will have to update
echo CONFIG.SYS manually (see the %product.TXT file for details).
echo.
echo Enter: Y to update %csname
echo C to update a copy of CONFIG.SYS in the %product directory
echo N to skip the CONFIG.SYS changes
echo.
inkey /k"YNC" Your choice: %%csopt
switch %csopt
case Y
set jptemp=%@filename["%@unique[.]"]
iff %product eq 4OS2 then
callrexx jpos2ins.cmd "4OS2" "%cd" "UpdatePaths" "%csname" "%jptemp" "" "%[cd]%exefile"
else
insthelp Config /d"%cd" /o"%csname" /t"%jptemp"
endiff
iff %result eq 0 then
copy %csname %csbak > nul
copy %jptemp %csname > nul
set csmod=Y
sep -
echo CONFIG.SYS has been updated. The next time you reboot your system, your
echo new copy of %product will be used as the %opsys command processor.
else
sep -
echo CONFIG.SYS could not be updated due to the above error. You must update
echo it manually (see the %product.TXT file for details).
endiff
del /q %jptemp > nul
case C
echo.
if exist .\config.sys (move .\CONFIG.SYS .\CONFIG.JPS > nul)
iff %product eq 4OS2 then
callrexx jpos2ins.cmd "4OS2" "%cd" "UpdatePaths" "%csname" "%[cd]CONFIG.SYS" "" "%[cd]%exefile"
else
insthelp Config /d"%cd" /o"%csname" /t"%[cd]CONFIG.SYS"
endiff
iff %result eq 0 then
sep -
echo The copy of CONFIG.SYS has been updated. You can review this file, then
echo make changes to the real CONFIG.SYS file manually when you are ready to
echo start using your new copy of %product as the %opsys command processor.
else
sep -
echo The copy of CONFIG.SYS could not be updated due to the above error. You
echo must update CONFIG.SYS manually (see the %product.TXT file for details).
endiff
case N
sep -
echo CONFIG.SYS will not be updated. You can update it manually when you are
echo ready to start using your new copy of %product as the default %opsys
echo command processor (see the %product.TXT file for details).
endswitch
wait
:configdone
if %product ne 4DOS .or. %_win ge 40 goto autoexecdone
set aename=%_boot:\AUTOEXEC.BAT
set aebak=%_boot:\AUTOEXEC.JPS
clear
text
The installation process updates AUTOEXEC.BAT to load the KSTACK.COM
program, a small memory-resident program used by the 4DOS KEYSTACK
command to pass keystrokes to DOS applications. You have three choices:
- Update the system AUTOEXEC.BAT file. This is the recommended
method and will fully install 4DOS on your system. Your previous
AUTOEXEC.BAT file will be saved as AUTOEXEC.JPS.
- Make a copy of AUTOEXEC.BAT in the 4DOS directory and update that
copy, instead of the "real" AUTOEXEC.BAT file. This allows you to
review the changes before implementing them. If there is already a
copy of AUTOEXEC.BAT in the 4DOS directory it will be renamed to
AUTOEXEC.JPS.
- Skip the AUTOEXEC.BAT update. In this case you will have to update
AUTOEXEC.BAT manually to install KSTACK.COM (see the 4DOS.TXT file
for details).
endtext
echo Enter: Y to update %aename
echo C to update a copy of AUTOEXEC.BAT in the 4DOS directory
echo N to skip the AUTOEXEC.BAT changes
echo.
inkey /k"YNC" Your choice: %%aeopt
switch %aeopt
case Y
set jptemp=%@filename["%@unique[.]"]
insthelp AutoExec /d"%cd" /o"%aename" /t"%jptemp"
iff %result eq 0 then
copy %aename %aebak > nul
copy %jptemp %aename > nul
set aemod=Y
echo AUTOEXEC.BAT has been updated.
else
sep -
text
AUTOEXEC.BAT could not be updated due to the above error. You must
update it manually (see the 4DOS.TXT file for details).
endtext
endiff
del /q %jptemp > nul
case C
if exist .\AUTOEXEC.BAT (move .\AUTOEXEC.BAT .\AUTOEXEC.JPS > nul)
insthelp AutoExec /d"%cd" /o"%aename" /t"%[cd]AUTOEXEC.BAT"
iff %result eq 0 then
sep -
text
The copy of AUTOEXEC.BAT has been updated. You can review this file,
then make changes to the real AUTOEXEC.BAT file manually when you are
ready.
endtext
else
sep -
text
The copy of AUTOEXEC.BAT could not be updated due to the above error.
You must update AUTOEXEC.BAT manually (see the 4DOS.TXT file for
details).
endtext
endiff
case N
sep -
text
AUTOEXEC.BAT will not be updated. You can update it manually when you
are ready (see the 4DOS.TXT file for details).
endtext
endswitch
wait
:autoexecdone
switch %product
case 4DOS
iff %_dosver ge 20.0 .and. exist jpos2ins.cmd then
clear
text
If you wish, the installation software can create an OS/2 desktop folder
for 4DOS, including objects to start 4DOS itself, and the 4DOS help.
endtext
yesno yn Create an OS/2 desktop folder for 4DOS
iff "%yn" == "Y" then
start /fg /c jpos2ins.cmd "4DOS" "%cd" "CreateFolder"
sep -
text
You should see the folder creation window open and execute on the
screen. Creating a folder is a separate process, and the installation
software cannot determine when the process is finished, or whether it
worked correctly. When you return to this screen you can continue, and
complete the installation.
If there are any errors in creating the folder or it does not appear on
your desktop, you can create 4DOS desktop objects manually as described
in the 4DOS.TXT file, in the section on using 4DOS under OS/2.
endtext
wait
endiff
endiff
iff %_win ge 40 then
iff exist jpsoft.inf then
clear
text
The installation software can create a JP Software program group for
4DOS, accessible through the Windows 95 Start menu. The group will
include shortcuts to start 4DOS itself, and the 4DOS help. The same
process creates a desktop shortcut for 4DOS (easily deleted if you
prefer to use only the Start menu).
The JP Software group and related desktop shortcuts will also be made
removable using Windows 95's Uninstall facility (available from the
Control Panel's Add / Remove Programs item).
If you choose not to create these items now, you can create shortcuts
manually as described in the 4DOS.TXT file, in the chapter on installing
4DOS.
endtext
yesno yn Create a Windows 95 program group and desktop shortcut for 4DOS
iff "%yn" == "Y" then
instinf %[cd]jpsoft.inf
sep -
text
The process to create the 4DOS group and shortcuts has been started, and
should be complete in a few seconds (this is a separate process, and the
installation software cannot determine when it is finished).
Installation will now continue. If there are any errors in creating the
group or shortcuts, or they do not appear on your Start menu or desktop,
you can create 4DOS shortcuts manually as described in the 4DOS.TXT
file, in the section on using 4DOS under Windows 95.
endtext
wait
endiff
endiff
iff exist jp4dos.inf then
clear
text
The installation software can install optional registry extensions for
4DOS. The registry extensions customize a few Windows 95 functions to
best take advantage of features provided by 4DOS. Specifically, they:
- Create a new "4DOS Prompt here" entry in the context menu of drives
and directories, to launch 4DOS in that drive or directory.
- Extend Windows' definition of a "batch file" to include BTM files.
- Provide an additional "open" option in the context menu of all
batch files (.BAT, .CMD, and .BTM), to run the file with 4DOS.
These registry extensions can be removed using Windows 95's Uninstall
facility (available from the Control Panel under Add / Remove Programs).
If you choose not to install the registry extensions now, you can do so
later as described in 4DOS.TXT, in the 4DOS installation chapter.
endtext
yesno yn Install 4DOS registry extensions
iff "%yn" == "Y" then
instinf %[cd]jp4dos.inf
sep -
text
The process to install the 4DOS registry extensions has been started, and
should be complete in a few seconds (this is a separate process, and the
installation software cannot determine when it is finished).
You can continue now, and complete the installation.
endtext
wait
endiff
endiff
endiff
case 4OS2
clear
text
If you wish, the installation software can create an OS/2 desktop folder
for 4OS2, including objects to start 4OS2 itself, and the 4OS2 help.
You can also create these objects manually as described in the 4OS2.TXT
file, in the chapter on installing 4OS2.
endtext
yesno yn Create an OS/2 desktop folder for 4OS2
iff "%yn" == "Y" then
callrexx jpos2ins.cmd "4OS2" "%cd" "CreateFolder"
wait
endiff
case 4NT
clear
:: Registry stuff only works in NT 4.0
iff %_dosver ge 4.00 then
iff exist jpsoft.inf then
clear
text
The installation software can create a JP Software program group for
4NT, accessible through the Windows NT Start menu. The group will
include shortcuts to start 4NT itself, and the 4NT help. The same
process creates a desktop shortcut for 4NT (easily deleted if you
prefer to use only the Start menu).
The JP Software group and related desktop shortcuts will also be made
removable using Windows NT's Uninstall facility (available from the
Control Panel's Add / Remove Programs item).
If you choose not to create these items now, you can create shortcuts
manually as described in the 4NT.TXT file, in the chapter on installing
4NT.
endtext
yesno yn Create a Windows NT program group and desktop shortcut for 4NT
iff "%yn" == "Y" then
instinf %[cd]jpsoft.inf
echo.
echo The program group and shortcuts have been created.
wait
endiff
endiff
iff exist jp4nt.inf then
clear
text
The installation software can install optional registry extensions for
4NT. The registry extensions customize a few Windows NT functions to
best take advantage of features provided by 4NT. Specifically, they:
- Create a new "4NT Prompt here" entry in the context menu of drives
and directories, to launch 4NT in that drive or directory.
- Extend Windows' definition of a "batch file" to include BTM files,
including the ability to double-click on a BTM file to execute it.
- Provide an additional "open" option in the context menu of all
batch files (.BAT, .CMD, and .BTM), to run the file with 4NT.
These registry extensions can be removed using Windows NT's Uninstall
facility (available from the Control Panel under Add / Remove Programs).
If you choose not to install the registry extensions now, you can do so
later as described in the 4NT.TXT file, in the 4NT installation chapter.
endtext
yesno yn Install 4NT registry extensions
iff "%yn" == "Y" then
instinf %[cd]jp4nt.inf
echo.
echo The registry extensions have been installed.
wait
endiff
endiff
endiff
endswitch
clear
switch %product
case 4DOS .or. 4OS2
iff %csmod eq Y then
echo %product installation is complete. The next time you reboot your system,
echo %product will be used as the default %opsys command processor.
else
echo %product installation is complete. You chose not to update the system
echo CONFIG.SYS file during the installation process. When you are ready,
echo update CONFIG.SYS as described in the %product.TXT file, then reboot.
endiff
iff %product eq 4DOS .and. %_win eq 40 then
echo.
echo To start 4DOS from the Windows 95 desktop, use the shortcut or group
echo created during the installation process. If you did not allow the
echo installation software to create a shortcut you can do so manually;
echo instructions are in the 4DOS.TXT file, in the chapter on 4DOS
echo installation.
endiff
case 4NT
echo 4NT installation is complete. To start 4NT, use the shortcut or group
echo created during the installation process. If you did not allow the
echo installation software to create a shortcut you can do so manually;
echo instructions are in the 4NT.TXT file, in the chapter on 4NT
echo installation.
endswitch
goto exit_noretry
:on_error
:nonfatalerr
on errormsg
on break
echo.
echo.
echo *** The installation stopped due to the above error. The installation
echo program will restart the next time you start 4%_dos.
echo.
goto done
:on_break
on errormsg
on break
echo.
echo.
echo *** Installation interrupted. The installation program will restart
echo the next time you start 4%_dos.
echo.
goto done
:fatalerr
on errormsg
on break
echo.
echo.
echo *** Installation stopped due to the above error.
echo.
echo You will have to complete the installation manually. For
echo instructions see the chapter on 4%_dos installation in the
echo 4%_dos.TXT file.
echo.
:exit_noretry
on errormsg
on break
set bname="%@full[%0]"
move %bname "%@path[%bname]\%@name[%bname].btx" >& nul
:done
on errormsg
on break
if "%_jprr" eq "Y" (endlocal %+ quit)
echo.
iff "%qq" eq "Y" then
pause Press any key to exit ...
exit
else
pause Press any key to exit to the 4%_dos prompt ...
endiff
endlocal
quit
:addslash
iff "%@right[1,%[%slashdir]]" eq "%=q" then
if "%@instr[%@eval[%@len[%[%slashdir]]-2],1,%[%slashdir]]" ne "\" set %slashdir="%@instr[1,%@eval[%@len[%[%slashdir]]-2],%[%slashdir]]\"
else
if "%@right[1,%[%slashdir]]" ne "\" set %slashdir=%[%slashdir]\
endiff
return