Re: W4 Installation Diskettes: where to load drivers from?

Am 25.04.07 23.09 schrieb My Name:
Wolfi wrote:
Am 22.04.07 05.57 schrieb Marcel Müller:
Wolfi wrote:
Could somebody please tell me, how W4 decides, which drivers to load from which Installation Disk?

The order of the BASEDEV files is documented. Off the top of my head is something like:

*.SYS
*.ADD
*.FLT
*.DMD

Theses types of files are loaded in this order, but withing that type are loaded in the order that they are found in the CONFIG.SYS file. So, for instance, the PCMCIA.SYS file is required to be listed and loaded before other SYS files, and before the OS2PCARD.DMD file, etc.

Thank you for that information. That basically sums it up to what I kind of concluded in the meantime during all my boot-up tries. At the beginning I just thought, there might be some kind of list hidden somewhere, letting the system know, what to load from where and ignoring additional statements in config.sys. But apparently theu just have been of the wrong type to already be allowed to load from Disk1. So I might need to experiment a bit further in that direction.

DEVICE files are loaded in the order in which they are found in the CONFIG.SYS file. Since UNICODE.SYS is required to be loaded for the JFS.IFS file to be loaded, the UNICODE.SYS file must be listed and loaded before the JFS.IFS file. And the MOUSE.SYS file must be listed and loaded before the COM.SYS file. Some special device drivers state to load them in some particular place in the CONFIG.SYS file.

Interesting, I wasn't aware that there is a sequential dependency between MOUSE and COM.sys.

Usually one choices this order according to what one wants their system find and use first. So when booting from floppies, one might list the floppy disk driver before an Instable File System driver (*.IFS), etc.

As I recall, I moved the files between the second and third disks (labled Disk #1 and Disk #2), but the very first Disk (Disk $0) has to have it kernel file there, etc.
>
If you want to squeeze files than use a third-party utility program that will create bootable floppies for you, such as BOOTOS2, or BOOTABLE. Both are available from your favorite OS/2 software web site. But they are not setup to create the *installation* floppies that OS/2 requires to boot-up and use a CD-ROM to install an operating system from. But, one can easily see how to do this by comparing the CONFIG.SYS file on the original installation floppy disk, and the CONFIG.SYS file created by one of these third party programs.

That's what I'm going to do now. I hesitated so far to get started with UpdCD, since I still have two older 486-133, which depend on those floppies and cannot boot from CD. So I wanted to have one working solution for all my systems, but now having seen a freshly installed W4 system again after some 7 years, came as kind of a shock.
Being used to my over the years evolved work box with all the updates, extensions, helpers and tools installed, the original W4 appears to be so horribly naked and incomplete, I had forgotten all about that. XWP alone makes already a huge difference.

Are you using the correct files that are made for booting-up from floppy disks, such as the extremely small *.DCP files, and VGA driver, etc.?

I didn't replace any files by type but rather tried to update as much from the original installation diskettes as possible, since the whole deal basically started out to be a try to replace the dumb, 8032MB limited FDisk-BM with LVM for an existing W4 system, to allow for partitions to be booted beyond that artificial limit imposed by the FDisk-BM. I was absolutely sure that IBM also removed that limitation from FDisk back then in 2002, when the ExtPart package gor released, but they didn't. Apparently all they did was adding those new M$ invented partition types for "large" HDDs, was it >512MB?, but nothing more.
And in order to do so, a whole lot of stuff had to be updated.
Only problem then, the W4 installation wouldn't work anymore.
.

Relevant Pages

  • scsi vhci driver and QLA2310, multi-path
    ... Hello I have installed qla2310 adapter in sunfire with solaris 8. ... the installation of driver for QLA2310 there I can see disks on the ... more than one path to the disk. ... SFS_base_packages.S8.tar.Z in which is vhci driver but it was not ...
    (comp.arch.storage)
  • scsi vhci driver and QLA2310, multi-path
    ... Hello I have installed qla2310 adapter in sunfire with solaris 8. ... the installation of driver for QLA2310 there I can see disks on the ... more than one path to the disk. ... SFS_base_packages.S8.tar.Z in which is vhci driver but it was not ...
    (comp.sys.sun.hardware)
  • Re: Connect HP Deskjet 812c to XP Pro
    ... Installation instructions ... Driver for this is included with XP. ... can you borrow a disk? ... converter cable rather than just hooking it up to the parallel port. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Spell checking
    ... that you can get a bad installation. ... What is the difference between Empty Trash and Empty Trash Securely? ... the disk file table to mark the file as "available for overwriting". ...
    (microsoft.public.mac.office.excel)
  • Re: Can you reduce bloated Windows Folder to increase disk space on La
    ... Installed Windows XP Home Edition SP1 from disk, ... Restore Point created and System files backed up in installation ... Highlight one of your drives and click on ...
    (microsoft.public.windowsxp.newusers)