QNX Technical Articles
QNX 4 Product Suite June 2008 Release Notes
Date of this edition: June 09, 2008
![]() |
For the most up-to-date version of these notes, go to our website, www.qnx.com, log into your myQNX account, and then go to the Download area. |
Contents...
- What's new in this product suite?
- Security updates
- Troubleshooting: safe mode
- Video support
- Known issues
- Where to find release notes for specific products
- Online documentation
- Technical support
What's new in this product suite?
This archive includes:
- an ISO of the QNX 4 Product Suite June 2008
- a copy of the license agreement
- installation and release notes
This edition of the product suite has the same content as the July 2003 Product Suite CD, except for the following:
- Fsys.atapi block driver — this driver adds support for
the latest IDE/SATA chipsets in legacy and native modes (see below).
For information about this driver's options, type use Fsys.atapi.
- dinit, fdisk utilities — these utilities support booting on large drives.
![]() |
If your QNX 4 computer has a SATA drive, modify the BIOS so that the controller uses IDE legacy/compatibility mode. (Ref# 56067) |
The Fsys.atapi driver supports the following IDE, EIDE and SATA chipsets:
| Manfacturer | Chip | Vendor ID | Device ID | Revision | Xfer Mode |
|---|---|---|---|---|---|
| ACER Labs | M5229 | 0x10b9 | 0x5229 | 0x19-0xc1 | UDMA 2 |
| ACER Labs | M5229 | 0x10b9 | 0x5229 | 0xc2-0xc3 | UDMA 4 |
| ACER Labs | M5229 | 0x10b9 | 0x5229 | 0xc4 | UDMA 5 |
| ACER Labs | M5287 | 0x10b9 | 0x5287 | — | SATA |
| ACER Labs | M5289 | 0x10b9 | 0x5289 | — | SATA |
| AMD | 8111 | 0x1022 | 0x7469 | — | UDMA 5 |
| AMD | PCB-756 | 0x1022 | 0x7409 | — | UDMA 4 (untested) |
| AMD | PCB-766 | 0x1022 | 0x7411 | — | UDMA 5 (untested) |
| AMD | PCB-768 | 0x1022 | 0x7441 | — | UDMA 5 |
| ATI | IXP-200 | 0x1002 | 0x4349 | — | UDMA 5 |
| ATI | IXP-300 | 0x1002 | 0x4369 | — | UDMA 5 |
| ATI | IXP-400 | 0x1002 | 0x4376 | — | UDMA 5 |
| ATI | IXP-600 | 0x1002 | 0x438c | — | UDMA 5 |
| ATI | SB-400 | 0x1002 | 0x4379 | — | SATA |
| ATI | SB-600 | 0x1002 | 0x4380 | — | SATA |
| HighPoint Tech | HPT-366 | 0x1103 | 0x0004 | 0x01 | UDMA 4 (untested) |
| HighPoint Tech | HPT-370 | 0x1103 | 0x0004 | 0x03+ | UDMA 5 |
| HighPoint Tech | HPT-372 | 0x1103 | 0x0005 | — | UDMA 6 |
| HighPoint Tech | HPT-374 | 0x1103 | 0x0008 | — | UDMA 6 |
| Intel | 6300ESB | 0x8086 | 0x2680 | — | SATA |
| Intel | 6300ESB | 0x8086 | 0x269e | — | UDMA 5 |
| Intel | 82371AB | 0x8086 | 0x7111 | — | UDMA 2 |
| Intel | 82371FB | 0x8086 | 0x1230 | — | BIOS |
| Intel | 82371SB | 0x8086 | 0x7010 | — | MDMA 2 |
| Intel | 82443MX | 0x8086 | 0x7199 | — | UDMA 2 |
| Intel | 82801AA | 0x8086 | 0x2411 | — | UDMA 4 |
| Intel | 82801AB | 0x8086 | 0x2421 | — | UDMA 4 |
| Intel | 82801BA | 0x8086 | 0x244B | — | UDMA 5 |
| Intel | 82801BAM | 0x8086 | 0x244A | — | UDMA 5 |
| Intel | 82801CA | 0x8086 | 0x248B | — | UDMA 5 |
| Intel | 82801CAM | 0x8086 | 0x248A | — | UDMA 5 |
| Intel | 82801DB | 0x8086 | 0x24CB | — | UDMA 5 |
| Intel | 82801DBM | 0x8086 | 0x24CA | — | UDMA 5 |
| Intel | 82801EB | 0x8086 | 0x24D1 | — | SATA |
| Intel | 82801EB | 0x8086 | 0x24DB | — | UDMA 5 |
| Intel | 82801ER | 0x8086 | 0x24DF | — | SATA |
| Intel | 82801ESB | 0x8086 | 0x25A2 | — | UDMA 5 |
| Intel | 82801ESB | 0x8086 | 0x25a3 | — | SATA |
| Intel | 82801FB | 0x8086 | 0x2651 | — | SATA |
| Intel | 82801FB | 0x8086 | 0x266F | — | UDMA 5 |
| Intel | 82801FBM | 0x8086 | 0x2653 | — | SATA |
| Intel | 82801FR | 0x8086 | 0x2652 | — | SATA |
| Intel | 82801GB | 0x8086 | 0x27c0 | — | SATA |
| Intel | 82801GB | 0x8086 | 0x27c4 | — | SATA |
| Intel | 82801GB | 0x8086 | 0x27df | — | UDMA 5 |
| Intel | 82801HB | 0x8086 | 0x2820 | — | SATA |
| Intel | 82801HBM | 0x8086 | 0x2825 | — | SATA |
| Intel | 82801IB | 0x8086 | 0x2920 | — | SATA |
| JMicron | JMB361 | 0x197b | 0x2361 | — | SATA |
| JMicron | JMB363 | 0x197b | 0x2363 | — | SATA |
| JMicron | JMB366 | 0x197b | 0x2366 | — | SATA |
| PCI IDE | Any | — | — | — | BIOS |
| PCMCIA | Any | — | — | — | PIO 0 |
| Promise | PDC-20262 | 0x105a | 0x4d38 | — | UDMA 4 |
| Promise | PDC-20265 | 0x105a | 0x0d30 | — | UDMA 5 |
| Promise | PDC-20267 | 0x105a | 0x4d30 | — | UDMA 4 |
| Promise | PDC-20269 | 0x105a | 0x4d69 | — | UDMA 5 |
| ServerWorks | CSB5 | 0x1166 | 0x0212 | — | UDMA 4 (untested) |
| ServerWorks | CSB5 | 0x1166 | 0x0212 | 0x92+ | UDMA 5 |
| ServerWorks | OSB4 | 0x1166 | 0x0211 | — | UDMA 2 |
| SiS | SiS-180 | 0x1039 | 0x0180 | — | SATA |
| SiS | SiS-181 | 0x1039 | 0x0181 | — | SATA |
| SiS | SiS-5513 | 0x1039 | 0x5513 | 0xd0 | UDMA 2/4 |
| SiS | SiS-5517 | 0x1039 | 0x5517 | — | UDMA 6 |
| SiS | SiS-5518 | 0x1039 | 0x5518 | — | UDMA 6 |
| VIA Tech | 8237 | 0x1106 | 0x3149 | — | SATA |
| VIA Tech | 82C586B | 0x1106 | 0x0571 | 0x6+ | UDMA 2 |
| VIA Tech | 82C586B | 0x1106 | 0x0571 | 8231 bridge | UDMA 5 (untested) |
| VIA Tech | 82C586B | 0x1106 | 0x0571 | 8233 bridge | UDMA 5 (untested) |
| VIA Tech | 82C586B | 0x1106 | 0x0571 | 8233A bridge | UDMA 6 |
| VIA Tech | 82C586B | 0x1106 | 0x0571 | 8233C bridge | UDMA 5 (untested) |
| VIA Tech | 82C586B | 0x1106 | 0x0571 | 8235A bridge | UDMA 6 (untested) |
| VIA Tech | 82C586B | 0x1106 | 0x0571 | 8237 bridge | UDMA 6 (untested) |
| VIA Tech | 82C586B | 0x1106 | 0x0571 | 82686B PCI-ISA bridge 0x40+ | UDMA 5 |
| Winbond | W83C553F | 0x10ad | 0x0105 | — | MDMA 2 |
Security updates
In 1990, we wrote the QNX qcrypt() function, using our own methods of encryption. DES was available at that time, but the export restrictions in place meant that we wouldn't have been able to ship our products internationally. This simply wasn't an option at the time.
Subsequently, we heard that the QNX 4 crypt() function had been cracked. We immediately created Security updates that use the standard Unix DES crypt() methods.
Components
The Security updates change the encryption method used in /etc/shadow, which is used by the products listed below to verify passwords.
![]() |
You must install the Security update for all of the following packages that you've installed. For example, if you install the update for Photon but not for the QNX 4 OS, phlogin will fail because it isn't using the same encryption as login. |
| For this product: | We updated these utilities/libs: |
|---|---|
| QNX OS v4.25 | login passwd su |
| Photon v1.14 | phlogin |
| TCP/IP Runtime v4.25 | ftpd pcnfsd popper pppd rexecd tn3270 map3270 |
| Watcom v10.6 | unix3r.lib unix3s.lib unixc.lib unixg3r.lib unixh.lib unixl.lib unixm.lib unixs.lib |
| QNX Windows v4.24 | olwm |
The only fixes in the Security updates are those related to crypt().
Installation issues
Only root users can affect security on your system — normal users don't have read access to the /etc/shadow file.
Before you install or uninstall a Security update, we recommend that you back up /etc/passwd and /etc/shadow, perhaps on a diskette. If you find that users can't login after the installation, copy these files back to their original locations.
During installation, the install program first backs up all files that need to be updated. The backup files are named filename.qcrypt.
![]() |
To maintain a secure system after installing the Security update and making sure that all users can successfully login, be sure to remove /etc/shadow.qcrypt. |
After installing the Security update, you must relink any executables that use the crypt() library function against the updated libraries. Otherwise, the decryption will fail.
Source code
The Security update includes a utility, fix-shadow, that decrypts the current /etc/shadow file and then encrypts the shadow file again using the standard Unix crypt().
Under /etc/readme/security, we've included the source code for the files that we used to create the fix-shadow utility:
- main.c
- Main function
- quncrypt.c
- Decrypt function
- crypt.c
- Standard Unix crypt() function
We used this cc command line to build the fix-shadow executable:
cc -l main.c quncrypt.c crypt.c -o fix-shadow
![]() |
We've included the source code used to fix the security problem for your information. You don't need to actually build and run the fix-shadow utility, because installing the Security update automatically produces a secure /etc/shadow file for you. |
Troubleshooting: safe mode
When your machine first boots from the CD, you'll see a message telling you to press any key for safe mode. If you do this, you'll see a menu of installation instructions containing several options:
- Diagnostic Mode – F1
- This option lets you specify the hardware that will be auto-detected. If you have any unusual devices, you may choose to select/unselect them. After Auto-detection, you may add additional devices manually by using the Add... button.
- VGA 16 Color only – F2
- You can use this option if any video problems appear when first booting or entering graphics mode. Later on during the installation, you'll be prompted for a video probe to obtain the better resolution.
- Keyboard only (no PS/2 Mouse) – F3
- If you have problems with your keyboard or pointing device, you may try this option.
- Verbose – F4
- This option will display all the available information when device drivers or other programs are run. You may find this option useful if there's a problem that's difficult to recognize/diagnose. The additional details provided may be required to help resolve problems.
- Reset Keyboard – F5
- If you have problems with your keyboard or pointing device, you may try this option.
- Reset PS/2 Mouse – F6
- If you have problems with your PS/2-compatible pointing device, you may select this option. Some controllers don't get initialized properly.
- Emulate Video BIOS – F9
- You can use this option if any video problems appear when first booting or entering graphics mode. Often laptops will “emulate” video chipsets through software.
Video support
Some video cards (e.g. in some portables) might not be supported in Photon. Even though the Product Installer can support many of these cards, in order to run Photon itself on such computers you might need a newer version of the Photon graphics drivers.
If this is the case, install all of the latest patches for Photon from the CD. If your video card still isn't supported, please contact Tech Support.
Known issues
The known issues for this edition of the QNX 4 Product Suite include the following:
- The CD installer won't run if your system has more than 1 GB of RAM. (Ref# 55856)
- The Fsys.atapi driver supports SATA drives only in legacy IDE mode. (Ref# 56067)
- If you insert a USB key (or other types of USB devices) into the Dell T3400, the entire system will stop responding. (Ref# 56626).
Where to find release notes for specific products
Each product we ship includes an online “readme” file that contains important information for each release (e.g. recent changes, known problems, configuration hints, and so on).
The files containing the release notes for each of the products you purchased are as follows:
| Part# | Version | Description | Release Notes |
|---|---|---|---|
| 007010 | 4.25 | QNX Operating System Runtime | /etc/readme/qnx425 |
| 007047 | 1.14 | Photon Runtime | /etc/readme/photon |
| 007012 | 4.25 | TCP/IP Runtime | /etc/readme/tcp425 |
| 007057 | 2.02 | Voyager Runtime | /etc/readme/voyager |
| 007005 | 10.6 | WATCOM C Compiler | /etc/readme/wcc10.6 |
| 007006 | 10.6 | WATCOM C++ Compiler | /etc/readme/wcc10.6 |
| 007013 | 4.25 | TCP/IP SDK | /etc/readme/tcp425 |
| 007048 | 1.14 | Photon SDK | /etc/readme/photon |
| 007071 | 2.02 | Voyager SDK | /etc/readme/voyager |
| 007081 | 1.10 | Citrix ICA Client Runtime | /etc/readme/ica |
| 007018 | 1.10 | Photon Chinese Supplement | /etc/readme/phcn |
| 007019 | 1.12 | Photon Japanese Supplement | /etc/readme/phjp |
| 007020 | 4.24 | QNX Windows Runtime | /etc/readme/windows |
Online documentation
You can read our HTML-based online documentation by using the Photon Helpviewer or a browser, such as our Voyager HTML browser.
Technical support
To obtain technical support for any QNX product, visit the Support + Services area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.
