**************************************************************************** QNX 4.24 OS Upgrade Note Sept. 10/97 **************************************************************************** /updates/qnx42/Released/qnx424diskset.tar.F - This archive contains a set of images suitable to make a set of 1.44M QNX 424 install disks. (1 boot disk, 4 install disks) Instructions for making QNX 424 install disks --------------------------------------------- 1) Download the archive, and check the cksum. 2) install the archive using the following command: /etc/install -u qnx424diskset.tar.F Note: The files will be unpacked into your current dir. You should see the following files: ./Readme ./boot_disk ./disk1 ./disk2 ./disk3 ./disk4 The "Readme" is this file, the others are images of the install disks. 3) Format 5 floppy disks, 4 with the default options (ie. fdformat /dev/fd0 ) for disk1 through disk4, and one for the boot disk 'fdformat -k0 -z2 /dev/fd0' 4) Copy the images to the formatted floppies... cp boot_disk /dev/fd0 cp disk1 /dev/fd0 cp disk2 /dev/fd0 etc. You should now have a set of QNX 424 install disks, which you have of course labeled already :-) These disks can be used to install QNX 424 on new (empty) systems, or to update a previously installed system (ie. 4.22). These disks are not licensed so if you are installing to a new system you will need to use your original QNX 4.2x OS disk 1. Installing the QNX 4.24 OS --------------------------- To install your QNX 4.24 upgrade, you can either do a complete installation "from scratch" or simply update your existing QNX system, depending on which version you're upgrading from: Existing version : Installation method : -------------------- ----------------------- QNX 4.0x Full install required QNX 4.1x Full install recommended QNX 4.2x Update install recommended --------------------------------------------------------------- If your standard distribution files reside on more than one partition or physical disk, or on a partition other than type 77 you'll need to use additional options to the install program. After you've booted from floppy, enter "use install" to see addtional options and examples. ---------------------------------------------------------------- Installing QNX 4.24 from scratch --------------------------------- 1. Backup any files from your existing system that you may wish to restore after this upgrade. WARNING : This "from scratch" procedure will completely erase the contents of your hard disk! You should back up any files you want to keep and then re-install them after this procedure. Note that you will have to re-install any existing software packages (e.g. Watcom) as well. 2. Read the release notes (See below). 3. Insert the boot disk in the floppy drive and reboot the computer. You should see the QNX logo, a welcome message. and a shell prompt(#). 4. At the shell prompt, type : install 5. Follow the instructions on your screen to set up your hard disk so it will boot the QNX OS. 6. Once the installation is complete, you should remove any floppy disks and reboot your computer from hard disk. The QNX OS should now be up and running. At this point, you'll need to login as root in order to begin setting your environment. Update Installation method -------------------------- 1. Back up your hard disk. 2. Read the release notes (See below). 3. Insert the QNX 4.24 boot disk in the floppy drive and boot your machine from floppy. 4. At the shell prompt type : install -u 5. Follow the instructions on your screen. The install program's -u option will install all the files to your hard disk without "diniting" the disk. Note that install -u won't overwrite any of the following configuration files, but will instead add a .424 extension when writing these default files to your disk: /etc/default/login.424 /etc/default/passwd.424 /etc/default/profile.424 /etc/default/su.424 /etc/config/netboot.424 /etc/config/netmap.424 /etc/config/lpsrvr.424 /etc/config/pcmcia.cards.424 /etc/config/pcmcia.cfg.424 /etc/config/qtalk.424 /etc/config/sysinit.floppy.424 /etc/config/sysinit.424 /etc/group.424 /etc/issue.424 /etc/motd.424 /etc/passwd.424 /etc/profile.424 /etc/shadow.424 /etc/syslog.conf.424 /etc/termcap.424 /usr/lib/mailx.rc.424 6. The install program will have built the following files : File Description -------- -------------- /boot/build/hard..424 buildfile, where is the logical node number /boot/images/hard. boot image corresponding to the buildfile. /etc/config/sysinit..424 example sysinit file Examine the buildfile to determine if the boot image is suitable for you machine. If it is copy the boot image to /.boot. If the buildfile isn't suitable, modify the build file to suit your machine, rebuild your boot image, and copy it /.boot. Examine the example sysinit file and use it as a template for your existing sysinit. file. 7. Boot your machine from hard disk. QNX 4.24 Release Notes (taken from /etc/readme/qnx424) ------------------------------------------------------ ; This file is divided into four sections: ; ; 1) Problems. Explaining issues that may cause problems. ; 2) Enhancements. Explaining new features. ; 3) Upgrading Notes when upgrading from a previous version of QNX. ; 4) Errata. Corrections to printed docs. ; ; ; Conference/Update System ; ------------------------ ; ; QNX Software System's Interactive Conferencing System ; (QUICS) is available to QNX users. QUICS allows users to ; download QNX product software updates and QNX freeware; it ; also provides a conferencing system and technical support ; forum. (In order to access software updates of QNX products, ; you'll need the serial number found on the back of your ; original disks.) ; ; To connect to QUICS, use the qtalk utility and dial ; 1-613-591-0934. QUICS is also accessible from the Internet ; for telnet and ftp access at quics.qnx.com and ftp.qnx.com, ; respectively. ; ; NOTE: The shipped version of the file /etc/config/qtalk contains ; an entry for QUICS. Simply type: ; ; qtalk quics ; ;***************************************************************************** SECTION I: Problems ;***************************************************************************** ; NOTE: Some topics are covered in more detail in individual technotes. Technotes are shipped in the directory /etc/readme/technotes. As more become available, they will be posted for download on the update system. Note that "vedit" has its own release notes in /etc/readme. Install Program --------------- The install program uses the utility "disktrap" to detect your hard disk. If for some reason this utility doesn't work with your machine (some laptops will lock-up during this sequence), you may need to skip this auto-detect portion of the install program. To skip the auto-detect (disktrap) : 1) Reboot with the boot floppy. 2) Start the install program with the "-d" option. This will tell the install program to skip the auto-detect sequence because a 3rd-party disk driver is being installed. 3) When the install program prompts with, "Please insert the '3rd party driver disk' in the floppy drive." "Press Enter when ready." leave the boot disk in the drive, and press enter. (The boot disk is the 'QNX driver disk') 4) You will be presented with a list of drivers that were found on the disk. Choose the proper one for your machine. 5) Continue normally through the install program. (The install program will prompt for the 3rd-party disk once more; leave the boot disk in the drive, and press enter.) If you are having trouble with an initial installation of QNX to a SCSI controller: - Clear the partition table 1) Reboot with the boot floppy. 2) Start the appropriate driver for your hard disk. (Or run the install program up to the point where it starts the driver for you; then press Esc to exit the install program) 3) Type "fdisk /dev/hd0", and delete all of the partition entries. - If the drive is < 1Gb 1) Make sure the BIOS >1Gb option is DISABLED 2) Reboot and try to install again If it fails again 1) Clear the partition table (see above) 2) Reboot and install using: install -p "fsys -h64,32" OR if the drive is >1Gb 1) Make sure the BIOS >1Gb option is ENABLED 2) Reboot and try to install again If it fails again 1) Clear the partition table (see above) 2) Reboot and install using: install -p "fsys -h255,63" If you are updating (install -u) an existing QNX machine with a SCSI controller: 1) Record the heads and sectors the system is currently using by executing the command "fdisk /dev/hd0 info" 2) When the install program displays the heads/sectors, verify they are the same, if not reboot and override with "install -up"fsys -h{heads},{sectors}" where {heads} and {sectors} are the old values. NOTE: The SCSI drivers now support extended translations. If your drive is > 1Gb and you did not use the >1G option, then you have >1024 cylinders and probably have a separate bootable partition. This extra partition is unnecessary with the new drivers, because they will now work with the >1G option. If you change to using the >1G option, you MUST backup the disk, reinstall as listed above, and restore your files. Installing on a hard-drive with more than 1024 cylinders -------------------------------------------------------- The BIOS is used to load the boot image. For this reason, the boot image _must_ reside below the 1024th cylinder. The recommended procedure to ensure the location of the boot image on a _large_ hard-drive, is to make a small (2Meg) _bootable_ partition on the first part of the disk. This bootable partition would be, for example, of type 78, while the main QNX partition would remain type 77. After constructing a boot image (see the buildqnx utility), copy the image to the bootable partition. The image, by default, will mount the main QNX partition when booted. NOTE: The install program is designed for moderately sized disks. The following procedure explains how to circumvent the default install program for _large_ disks. Using the install program Boot from the boot floppy and run install with the '-q' option (query mode). In this mode the install program will present you with a (yn!) prompt before executing each command. In Step 1, Creating a QNX Hard Disk Partition, choose to edit the partition table with the fdisk command. Create a small (2Meg) type 78 partition on the first part of the disk, making sure that it is entirely below the 1024th cylinder. Create the main QNX partition, default type 77, to install to. Make the small partition bootable; then save and quit the fdisk program. Choose 'y' (execute the command) for all commands up until the part of Step 4, Making QNX Boot From Hard Disk, that copies the boot image to /.boot. (The command will be "cp -t images/hard. /.boot") Choose '!' to escape to a shell prompt. CAUTION: The dinit command below will remove all existing files from the named partition. Be sure to name the small bootable partition and not your main QNX partition, or else you will need to install QNX again. Type in: dinit -h /dev/hd0t78 dcheck -m /dev/hd0t78 mount /dev/hd0t78 /bootable cp -t /boot/images/hard. /bootable/.boot exit When you have returned to the install program, by typing exit or pressing Ctrl-D, you will be prompted once again if you wish to copy the boot image to /.boot. Type 'n'. The very next command presented to you will be in the form of: fdisk /dev/hd0 [LOADER] BOOT [QNX|t] Choose '!' to escape to a shell prompt. Type in the same command specifying your bootable partition: (In this example, type 78) fdisk /dev/hd0 [LOADER] BOOT t78 exit When you have returned to the install program (by typing exit or pressing Ctrl-D), you'll be prompted once again if you wish to execute the same command. Type 'n'. Choose 'y' at all remaining (yn!) prompts to finish the install. (If you wish, when the install has completed, execute 'fdisk /dev/hd0' and ensure that your small partition is indeed marked bootable) Installing 3rd-Party Products ------------------------------- Previous versions of the OS had files that shipped in "/bin32/". This directory not longer exists with QNX 4.24, but some 3rd-party products will install files to this directory. If you install a 3rd-party product, move any files installed to this directory to "/bin", and remove the directory. Online Documentation -------------------- Our HTML-based online documentation is designed to be read by our Photon Helpviewer. If you try to use a generic HTML browser, you won't see the table of contents for any book. Also, your browser may not be able to render tables properly (our documentation includes many tables). We've posted a text mode help viewer (tmhv) in /usr/free/utils on QUICS for those who don't have Photon. This will let you view the online docs (but not the images, tables, etc.). int10 ----- The version of "int10" shipped with 4.23 (or later) must be used with the 4.24 Proc. If it gets backdated during the installation of Photon 1.00 or any other packages, then you can selectively install "int10" from the 4.24 install disks. (See 'use /etc/install' for details) Network Analysis ---------------- When a significant event happens in the Net process or a Net.* driver, the event is logged in an internal buffer maintained by Net. A utility called 'netinfo' displays the contents of this buffer. By default, the same event is also logged as a trace entry. As the Net process and Net.* drivers can generate a large number of events, the trace buffer can be filled very quickly. It is at the discretion of system operators as to how they wish to use these tools to analyze the network. A number of options are available: 1. Only use 'netinfo' and don't log any network events in the trace buffer. To do this, start your 'Net' process with the -T option. Then, there will be no trace entries for Net; you would use 'netinfo' to display network events. 2. Save network events in the trace log, but don't display them with traceinfo. To do this, use the -M option on traceinfo. e.g. traceinfo -M !4 3. Display details of all network events. There is a new file provided with this release that describes in detail the network events. This file is /etc/config/traceinfo.net To use it, have traceinfo read in the traceinfo.net file: e.g. traceinfo -e /etc/config/traceinfo.net Details on all the current network events will be displayed. Another way to read in the traceinfo.net file is to use the #include command. In /etc/config/traceinfo, you could insert the line: #include /etc/config/traceinfo.net (put this command at the end of the file so that the entries in /etc/config/traceinfo.net will override the default net entries in /etc/config/traceinfo) Be careful when using this. The time taken to load in all the network event descriptions and sort them can be long (several seconds). It may be easiest to have a new shell command that only specifies the traceinfo.net file when you want to analyze the network. e.g. alias traceinfo_net='traceinfo -e /etc/config/traceinfo.net' Socket/Socklet -------------- Versions of the TCP/IP server (Socket or Socklet) prior to 4.22B (as reported in the VERSION column output from "sin version") must have their stack increased to work correctly with QNX 4.24. The stack can be increased by executing the following command as root: size -s4k /bin/Socket /bin/Socklet Resource Managers ----------------- There's a limit (not enforced) of no more than 150 prefix unit numbers per resource manager. IDE Drives ---------------- The following chart details the supported features for the Fsys.eide, Fsys.ata, Fsys.ide, and Fsys.vpm50 hard-disk drivers. Where: LBA stands for Logical Block Addressing. PIO stands for Programmed IO. Supported Feature Fsys.eide Fsys.ata Fsys.ide Fsys.vpm50 CD-ROM yes no no no Multiple interfaces yes no no no Removable drives (SYQUEST) yes no no no LBA yes yes no yes Enhanced PIO modes yes yes no yes Multi-block per interrupt yes yes yes* yes Uses BIOS for drive geometry yes yes yes no! * If drive supports it. ! Uses geometry returned by drive. Exceptions: 1. If the user specifies parameters to the driver, they override the default. 2. If the drive geometry info is read from the BIOS, and both the cmos and bios data area(s) show no drives, then the geometry will be read from the drive and a warning printed. 3. If the drive does not support LBA or if LBA is disabled, the drive is 'programmed' with the geometry parameters. Boot Image Limits ----------------- The boot image is limited to 512k. See buildqnx in the Utilities Reference for required system services. Booting from floppy -------------------- If you are making a boot floppy that will need to use pipes, make sure you run the pipe manager (Pipe). Using pipes without the pipe manager when the floppy is mounted as "/" will result in corruption of the pipe data. Extended Memory --------------- There is an outstanding problem detecting memory above 16M on Compaq machines because of their non-standard interface. You can add the extra memory to your system by using the "-M" option to "boot" in your build file or by using the ramtrap utility. Login procedure --------------- On login /etc/profile is run for every user. This file should be owned by root. On some systems it becomes a fairly elaborate shell script giving extra security or accounting features, e.g. only certain users can come in via modem ports, etc. On others it just does any all-user environment setup you want. $HOME/.profile is run after /etc/profile. Each user has his/her own .profile and on most systems he/she owns the file. Sometimes administrators retain ownership for tighter control. Both files should be writable only by their owners for security reasons. There is a file called /etc/default/profile. This is a "standard" file which gets copied to $HOME/.profile by the passwd utility that creates new user accounts. (See Utilities Reference - N to Z, p.898, sh) Dev.ditto --------- This console driver can be run on a machine that does not have a video card. The machine can then be accessed and 'ditto'ed from other machines on the network. The script, /etc/make_links, creates a link to Dev.ansi ln -fs /bin/Dev.ansi /bin/Dev.ditto When the driver is invoked as Dev.ditto, it will not touch the local hardware, if it exists. Dosfsys and Windows 95 Long Filenames ------------------------------------- As noted in the QNX 4.24 documentation set, the Microsoft Windows 95 release has added support for long filenames that are not limited to the traditional DOS "cccccccc.xxx" filename convention. Dosfsys can handle existing Windows 95 files with "long" filenames when the "-L" option is specified, but Dosfsys does not support creating files with long filenames -- the file must already exist. For every Windows 95 long filename created, Windows 95 also creates a "short" name to maintain backwards compatibility with DOS. If you delete or rename a file with a "long filename" through Dosfsys (or through DOS or a pre-Windows 95 application), the file will get deleted but the "long filename" will become detached from its "short name". This is easily corrected using Windows 95 SCANDISK utility. Full Windows 95 filename support (e.g. long filename creation, full deletion of long filenames, etc) is not currently scheduled. co -------- co -T does not work. A fixed version will posted on QUICS when it becomes available. Dev.ansi -------- When hardware scrolling is enabled, some machines may hang on a console switch. Dev.ansi has been changed to disable hardware scrolling by default and a "-h" option is now provided that enables hardware scrolling. Fsys.aha -------- This driver is no longer being shipped. Fsys.ps2e --------- This driver is no longer being shipped. Fsys.ps2m --------- This driver is no longer being shipped. Fsys.ps2s --------- This driver is no longer being shipped. Fsys.wd ---------- This driver is no longer being shipped. ksh --------------- sin > /dev/con8 > /dev/con8 When the command finishes and control returns to the shell, the shell's output is still redirected to /dev/con8. When piping between a remotely executing process and a local process, if you terminate the local process, the remote process will not always terminate. For example: //1 cat /etc/readme/qnx | less The remote 'cat' will require a ^C to terminate if 'less' is exited from before the remote 'cat' has finished. Mouse, mousetrap ---------------- The new version of "/bin/Mouse" shipped with this release has been modified to work on top of Input (new input manager). "/bin/mousetrap" is now a link to inputtrap. inputtrap detects input devices and starts Input with the appropriate parameters. "inputtrap" will behave in very similar fashion as mousetrap when called with argv[0] == "mousetrap". The mousetrap options "-P" and "-mp" have been deprecated; if your sysinit makes reference to these options, you will get a "Invalid option('')" error. To correct this, simply remove these options from the mousetrap command line. Input/inputtrap --------------- If you're not running Dev.ser and have a PnP Mouse connected to your system, then you must create a "/etc/config/trap/input." config file. This file should contain the arguments inputtrap will pass to Input. When an input.node file exists, inputtrap doesn't probe for input devices - it simply invokes Input with the arguments you specify in the file. If you don't include this file, then your system may hang when inputtrap starts Input. Creating an input.node file --------------------------- To reduce the likelihood of typing errors, you may query inputtrap and redirect the output to an initial input. file, which you may then edit: touch /etc/config/trap/input.node inputtrap query > /etc/config/trap/input.node where "node" is the logical node number assigned to the computer. The input. file doesn't have a line-oriented structure, but you may find it convenient to list each protocol module (along with its options and arguments) on a separate line. Since the result resembles a simple script, you may think of each hardware module as an "executable." After you remove the protocol modules you won't need, the contents of your input.node file might look like this: kbd fd -d/dev/kbd msoft fd -d/dev/ser1 To determine which protocol modules to select for your hardware, type "use Input" for a complete description of the modules and their options and arguments. netmap --------------- There's an in-memory image of the netmappings in the data space of Net on each node. When you type netmap, you are NOT looking at the /etc/config/netmap file, but rather you are asking Net for its in-memory contents. (/etc/config/netmap should be owned by root with file permission mode bits set to 644; see the chmod utility) When you use netmap to change a mapping, you are changing ONLY the contents of Net's memory. The contents of Net's data space can be changed only by root (with the netmap utility). Any user may read the information by using the netmap utility -- i.e. any user may execute the following: netmap [-n node] to display the network node mapping table of the specified node (the default is the node that netmap is executed on). Proc32 --------------- A variety of reboot methods is needed to ensure that all machines will be able to reboot successfully. The "-b" option to Proc32 has been changed to accept an optional digit that can be used to select different reboot methods. If your machine has trouble rebooting with the default method, then include the "-b num" in your build file. (See the Proc32 docs in the Utilities Reference for a complete description of the reboot methods when using the "-b" option.) Graphics --------------- To run programs that call Watcom Graphics library functions, you must start the 'int10' utility. See the int10 docs in the Utilities Reference for details. QNX Windows ----------- With the release of QNX 4.23 (or later), QNX is defaulting to 32-bit executables for all the OS components, including the Dev suite. Unfortunately, Dev.win is still 16-bit and requires a 16-bit Dev to run. An update for QNX Windows is available on QUICS that allows Dev.win to talk to a 16-bit Dev while co-existing with the default Dev32 suite. Included in the update is a new Dev.win that will properly handle the -N option to talk to a Dev that isn't registered as /dev. This new Dev.win, which needs to be 16-bit, can talk to a 16-bit Dev co-existing with the 32-bit Dev suite, which is the default in the 4.24 OS. Once you have the update installed, you can run the 16-bit Dev and Dev.win and still have 32-bit Dev suite running like so: /bin16/Dev -N /D16 & /windows/apps/Wterm/Dev.win -N /D16/win -n10 -r & Rundos ------ Rundos doesn't work with the QNX 4.23A (or later) 32-bit Process Manager. SMBfsys ------- RCS doesn't work on top of SMBfsys tic --- tic doesn't handle commented booleans or numerics. ; ;***************************************************************************** SECTION II: Enhancements ;***************************************************************************** ; For a summary of enhancements, changes, etc., see the file: /etc/readme/qnx423Atoqnx424.changes ;***************************************************************************** SECTION III: Upgrading ;***************************************************************************** ; Notes : Upgrading from a previous version of QNX ------------------------------------------------ Configuration Files ------------------- If you're upgrading from QNX 4.x to 4.24, you'll use the '-u' option to the automatic install program. When you use this option, the system configuration files will not be overwritten; instead, the new files will be installed as .424. You should examine the following files and compare them to your existing files to ensure they're suitable for this release: /etc/default/login.424 /etc/default/passwd.424 /etc/default/profile.424 /etc/default/su.424 /etc/config/netboot.424 /etc/config/netmap.424 /etc/config/lpsrvr.424 /etc/config/pcmcia.cards.424 /etc/config/pcmcia.cfg.424 /etc/config/qtalk.424 /etc/config/sysinit.floppy.424 /etc/config/sysinit.424 /etc/group.424 /etc/issue.424 /etc/motd.424 /etc/passwd.424 /etc/profile.424 /etc/shadow.424 /etc/syslog.conf.424 /etc/termcap.424 /usr/lib/mailx.rc.424 Note: The file "/etc/issue" is printed when login is invoked without any arguments. The default file contains a message : Welcome to QNX 4.24 Copyright (c) QNX Software Systems Ltd. 1982,1997 If you don't update this file, then you'll still see the older 4.?? version message. You should also examine the /etc/config/sysinit..424 file that was built for you and use it as a template to modify your existing sysinit file. The file /boot/build/hard.. 424 should also be examined to see if it is suitable for your system. If it is, then cp /boot/images/hard..424 /.boot If it's not suitable, use it as a template to modify your hard-disk buildfile, and then build a new operating system image using the new managers. You should then copy this image to /.boot. Please Note: You must rebuild and copy a new image to /.boot before you reboot. Files that may not get installed during an update ------------------------------------------------- The following files will be installed only if they are newer than the ones currently installed on your system : /bin/Input /bin/Mouse /etc/config/pnpmouse /bin/inputtrap /usr/bin/int10 Removing "/bin32" ----------------- Since most executables shipped with QNX 4.23 (or later) are 32-bit, QNX has decided to deprecate "/bin32" and ship everything in "/bin". This means that "/bin32" will no longer exist on freshly installed systems. Before unpacking all the files from the install disks, the install program will get rid of your "/bin32" directory. All files currently in the directory will be moved to "/bin". NOTE: Some files and links shipped with previous versions of QNX may simply be removed. A symbolic link will be created from "/bin32" to "/bin" to preserve any references to this directory. NOTE: This may cause problems for some 3rd-party products if they are installed after 4.24 (e.g. Watcom wsql). You may need to actually create the bin32 directory before installing a 3rd-party product. Then after the install, move anything that was installed there to /bin and replace the /bin32 dir with a symlink. After your system has been updated you should remove "/bin32" from the $PATH of all of your users. The "/etc/profile" shipped with QNX 4.24 no longer adds "/bin32" to $PATH. Build files ----------- Every attempt has been made to make QNX 4.22 build files compatible with QNX 4.23A (or later), but there are a few areas that could cause trouble: - heap sizes. The recommended heap size for all modules is now '1'. If you have '0' specified as the heap size for any module in 4.22, this meant 'grab as much heap as you can' -- in 4.24 this is bad, as it causes the boot image to be too big. NOTE: The absolute maximum size for boot images is 524288 (512K), i.e. in your build file change : sys/Proc32 to sys/Proc32 $ 0 Proc32 -l 1 $ 1 Proc32 -l 1 - Options. Some obsolete options specified to Proc32, Fsys etc. may cause problems. We've tried to handle them all, but if you have problems booting, try removing some of the more obscure options and get a simple system booting first. - sys/boot 'sys/boot' is a new process (shipped with qnx 4.23A or later) that does some initialization and then jumps into Proc32. This module will be automatically included in your image by buildqnx, but if you need to supply options to 'boot', the module must be included in your build file. If 'sys/boot' does appear in your build file, it must be first. - Slib32 and Slib16 Slib32 must come before Slib16 in your build file. New default make ---------------- QNX 4.23 (or later) ships with a new version of make (gnu make). After your system has been updated, /bin/make will be a symbolic link to /bin/gmake. Some of your existing makefiles may not be compatible with the new version of make. For this reason, your old version of make will be saved as /bin/qmake. vedit 3.22 ---------- All files for the new version of vedit are shipped under /usr/lib/vedit3. This leaves all the files from your original version of vedit intact. Note to Users Upgrading from QNX 4.22 (or earlier): ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Because of the changes included in the new vedit, all of your customized config files are no longer compatible. Before starting the new vedit, you should: 1. Delete any ".veditrc", ".vedit.cfg",".vedit.key" files in the user's HOME directories. 2. Configure VEDIT 3.22 as desired and in the same way as before. ;***************************************************************************** SECTION IV: Errata ;***************************************************************************** ;