Create Utility Diskettes - OS2

This is a discussion on Create Utility Diskettes - OS2 ; I am sharing the good and bad news on this subject. I felt I needed the diskettes to edit files on a SCSI drive which I had moved from a dead U160 mobo to a new U320 mobo. The drive ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Create Utility Diskettes

  1. Create Utility Diskettes


    I am sharing the good and bad news on this subject.

    I felt I needed the diskettes to edit files on a SCSI drive which I had moved
    from a dead U160 mobo to a new U320 mobo. The drive had aicu160.add but needed
    aicu320.add in order to boot past the earliest reports from config.sys.

    I took ages to experiment and read the archives and arrive at what is almost a
    winning formula:-

    I altered only diskette 1.
    I avoided everything associated with snooping.
    I deleted aic78u2.add because it was big and not associated with snooping.
    I deleted ibm2*.add because I needed the extra space.
    I added aicu320.add.
    In config.sys I remmed the references to the files I had deleted and added
    basedev=aicu320.add (twice because the controller is a dual).

    I noted that the u160 box that created the diskettes copied across aicu160.add
    but not aicu320.add, perhaps because, although present it was not loaded.

    This set of diskettes booted the box that created them and one other, but not
    the new box. The failure occurred when loading from diskette 2, and Warp kindly
    created a popuplog on the diskette.

    ------------------------------------------------------------

    04-25-2008 17:53:08 SYS3175 PID 0001 TID 0006 Slot 0008
    sysinit
    c0000005
    fb833124
    P1=00000008 P2=000009d8 P3=XXXXXXXX P4=XXXXXXXX
    EAX=00000000 EBX=00f60000 ECX=000c0000 EDX=bfeb0000
    ESI=ffde0100 EDI=fe7f44ce
    DS=0000 DSACC=**** DSLIM=********
    ES=0130 ESACC=00f3 ESLIM=000057f5
    FS=0000 FSACC=**** FSLIM=********
    GS=0000 GSACC=**** GSLIM=********
    CS:EIP=08ab:00000124 CSACC=009f CSLIM=00000c7d
    SS:ESP=001f:00000f76 SSACC=00f3 SSLIM=00000fff
    EBP=0000dbf3 FLG=00013246

    ------------------------------------------------------------

    04-25-2008 17:53:09 SYS3170 PID 0001 TID 0006 Slot 0008
    sysinit
    c0010001
    1c029e3a
    EAX=00000000 EBX=00f60000 ECX=00000053 EDX=bfeb0000
    ESI=ffde0100 EDI=fe7f44ce
    DS=0053 DSACC=d0f3 DSLIM=3fffffff
    ES=0053 ESACC=d0f3 ESLIM=3fffffff
    FS=150b FSACC=00f3 FSLIM=00000030
    GS=0000 GSACC=**** GSLIM=********
    CS:EIP=005b:00000000 CSACC=d0df CSLIM=3fffffff
    SS:ESP=0053:00030a72 SSACC=d0f3 SSLIM=3fffffff
    EBP=00030b8a FLG=00013246

    DOSCALL1.DLL 0002:00009e3a

    ------------------------------------------------------------

    04-25-2008 17:53:09 SYS3170 PID 0001 TID 0006 Slot 0008
    sysinit
    c0010001
    1c029e3a
    EAX=00000000 EBX=00f60000 ECX=00000053 EDX=bfeb0000
    ESI=ffde0100 EDI=fe7f44ce
    DS=0053 DSACC=d0f3 DSLIM=3fffffff
    ES=0053 ESACC=d0f3 ESLIM=3fffffff
    FS=150b FSACC=00f3 FSLIM=00000030
    GS=0000 GSACC=**** GSLIM=********
    CS:EIP=005b:00000000 CSACC=d0df CSLIM=3fffffff
    SS:ESP=0053:0003056e SSACC=d0f3 SSLIM=3fffffff
    EBP=00030686 FLG=00013246

    DOSCALL1.DLL 0002:00009e3a

    ------------------------------------------------------------

    04-25-2008 17:53:11 SYS3171 PID 0001 TID 0006 Slot 0008
    sysinit
    c0010001
    1c029e3a
    EAX=00000000 EBX=00f60000 ECX=00000001 EDX=bfeb0000
    ESI=ffde0100 EDI=fe7f44ce
    DS=0053 DSACC=d0f3 DSLIM=3fffffff
    ES=0053 ESACC=d0f3 ESLIM=3fffffff
    FS=150b FSACC=00f3 FSLIM=00000030
    GS=0000 GSACC=**** GSLIM=********
    CS:EIP=005b:1c02a40a CSACC=d0df CSLIM=3fffffff
    SS:ESP=0053:0002fffe SSACC=d0f3 SSLIM=3fffffff
    EBP=00030016 FLG=00013212

    DOSCALL1.DLL 0002:00009e3a


    I will be grateful if you will suggest what I should try next.




  2. Re: Create Utility Diskettes

    johnsuth@nospam.com.au wrote:
    > I am sharing the good and bad news on this subject.
    >
    > I felt I needed the diskettes to edit files on a SCSI drive which I had moved
    > from a dead U160 mobo to a new U320 mobo. The drive had aicu160.add but needed
    > aicu320.add in order to boot past the earliest reports from config.sys.
    >
    > I took ages to experiment and read the archives and arrive at what is almost a
    > winning formula:-
    >
    > I altered only diskette 1.
    > I avoided everything associated with snooping.
    > I deleted aic78u2.add because it was big and not associated with snooping.
    > I deleted ibm2*.add because I needed the extra space.
    > I added aicu320.add.
    > In config.sys I remmed the references to the files I had deleted and added
    > basedev=aicu320.add (twice because the controller is a dual).
    >
    > I noted that the u160 box that created the diskettes copied across aicu160.add
    > but not aicu320.add, perhaps because, although present it was not loaded.
    >
    > This set of diskettes booted the box that created them and one other, but not
    > the new box. The failure occurred when loading from diskette 2, and Warp kindly
    > created a popuplog on the diskette.
    >
    > ------------------------------------------------------------
    >
    > 04-25-2008 17:53:08 SYS3175 PID 0001 TID 0006 Slot 0008
    > sysinit
    > c0000005
    > fb833124
    > P1=00000008 P2=000009d8 P3=XXXXXXXX P4=XXXXXXXX
    > EAX=00000000 EBX=00f60000 ECX=000c0000 EDX=bfeb0000
    > ESI=ffde0100 EDI=fe7f44ce
    > DS=0000 DSACC=**** DSLIM=********
    > ES=0130 ESACC=00f3 ESLIM=000057f5
    > FS=0000 FSACC=**** FSLIM=********
    > GS=0000 GSACC=**** GSLIM=********
    > CS:EIP=08ab:00000124 CSACC=009f CSLIM=00000c7d
    > SS:ESP=001f:00000f76 SSACC=00f3 SSLIM=00000fff
    > EBP=0000dbf3 FLG=00013246
    >
    > ------------------------------------------------------------
    >
    > 04-25-2008 17:53:09 SYS3170 PID 0001 TID 0006 Slot 0008
    > sysinit
    > c0010001
    > 1c029e3a
    > EAX=00000000 EBX=00f60000 ECX=00000053 EDX=bfeb0000
    > ESI=ffde0100 EDI=fe7f44ce
    > DS=0053 DSACC=d0f3 DSLIM=3fffffff
    > ES=0053 ESACC=d0f3 ESLIM=3fffffff
    > FS=150b FSACC=00f3 FSLIM=00000030
    > GS=0000 GSACC=**** GSLIM=********
    > CS:EIP=005b:00000000 CSACC=d0df CSLIM=3fffffff
    > SS:ESP=0053:00030a72 SSACC=d0f3 SSLIM=3fffffff
    > EBP=00030b8a FLG=00013246
    >
    > DOSCALL1.DLL 0002:00009e3a
    >
    > ------------------------------------------------------------
    >
    > 04-25-2008 17:53:09 SYS3170 PID 0001 TID 0006 Slot 0008
    > sysinit
    > c0010001
    > 1c029e3a
    > EAX=00000000 EBX=00f60000 ECX=00000053 EDX=bfeb0000
    > ESI=ffde0100 EDI=fe7f44ce
    > DS=0053 DSACC=d0f3 DSLIM=3fffffff
    > ES=0053 ESACC=d0f3 ESLIM=3fffffff
    > FS=150b FSACC=00f3 FSLIM=00000030
    > GS=0000 GSACC=**** GSLIM=********
    > CS:EIP=005b:00000000 CSACC=d0df CSLIM=3fffffff
    > SS:ESP=0053:0003056e SSACC=d0f3 SSLIM=3fffffff
    > EBP=00030686 FLG=00013246
    >
    > DOSCALL1.DLL 0002:00009e3a
    >
    > ------------------------------------------------------------
    >
    > 04-25-2008 17:53:11 SYS3171 PID 0001 TID 0006 Slot 0008
    > sysinit
    > c0010001
    > 1c029e3a
    > EAX=00000000 EBX=00f60000 ECX=00000001 EDX=bfeb0000
    > ESI=ffde0100 EDI=fe7f44ce
    > DS=0053 DSACC=d0f3 DSLIM=3fffffff
    > ES=0053 ESACC=d0f3 ESLIM=3fffffff
    > FS=150b FSACC=00f3 FSLIM=00000030
    > GS=0000 GSACC=**** GSLIM=********
    > CS:EIP=005b:1c02a40a CSACC=d0df CSLIM=3fffffff
    > SS:ESP=0053:0002fffe SSACC=d0f3 SSLIM=3fffffff
    > EBP=00030016 FLG=00013212
    >
    > DOSCALL1.DLL 0002:00009e3a
    >
    >
    > I will be grateful if you will suggest what I should try next.
    >



    OS/2 had a problem with the Athlon 64 running more than 512mb of memory
    if the 'testcfg.sys' and 'apm.sys' drivers were loaded in the config.sys
    file. You could work around the problem by either using 512mb or less
    of memory or by remming out the testcfg.sys and apm.sys drivers in
    config.sys. This problem was fixed in kernel 103a and also in 104a, the
    final OS/2 kernel. There were also sometimes problems with traps when
    loading the ibmint13.i13 driver in config.sys. This is an old fallback
    disk controller driver that most systems do not need. In all cases, the
    problem would appear as a trap during booting and the fix was to rem out
    the statement. Finally, some systems have a problem with OPL3.SYS so try
    remming that out.

    >
    >



    --
    Posted with OS/2 Warp 4.52
    and Sea Monkey 1.5a
    

  3. Re: Create Utility Diskettes

    On Fri, 25 Apr 2008 08:28:53 UTC, johnsuth@nospam.com.au wrote:

    >
    > I am sharing the good and bad news on this subject.
    >
    > I felt I needed the diskettes to edit files on a SCSI drive which I had moved
    > from a dead U160 mobo to a new U320 mobo. The drive had aicu160.add but needed
    > aicu320.add in order to boot past the earliest reports from config.sys.

    ....snip...
    > I will be grateful if you will suggest what I should try next.


    Why are you wasting your time with diskettes? Even 2.8 meg diskettes
    aren't big enough to hold all that is required for a lot of the newer
    systems. Go to:

    > http://www.xs4all.nl/~hrbaan/bootAble/


    and get bootAble (I highly recommend the WPI version, with the CONFIG
    MAKER program, which helps to guide you through the complexities of
    building an initial config file). That will build a bootable CD (or
    DVD), or a maintenance partition on your hard disk, which works very
    much like the normal system. It has support for networking, as well as
    the WPS. About the only thing that it doesn't have (yet), is the
    ability to print.

    Hope this helps...
    --
    From the eComStation 2.0 RC2 of Doug Bissett
    dougb007 at telus dot net
    (Please make the obvious changes, to e-mail me)


  4. Re: Create Utility Diskettes

    In , "David T. Johnson" writes:
    >johnsuth@nospam.com.au wrote:
    >> I am sharing the good and bad news on this subject.
    >>
    >> I felt I needed the diskettes to edit files on a SCSI drive which I had moved
    >> from a dead U160 mobo to a new U320 mobo. The drive had aicu160.add but needed
    >> aicu320.add in order to boot past the earliest reports from config.sys.
    >>
    >> I took ages to experiment and read the archives and arrive at what is almost a
    >> winning formula:-
    >>
    >> I altered only diskette 1.
    >> I avoided everything associated with snooping.
    >> I deleted aic78u2.add because it was big and not associated with snooping.
    >> I deleted ibm2*.add because I needed the extra space.
    >> I added aicu320.add.
    >> In config.sys I remmed the references to the files I had deleted and added
    >> basedev=aicu320.add (twice because the controller is a dual).
    >>
    >> I noted that the u160 box that created the diskettes copied across aicu160.add
    >> but not aicu320.add, perhaps because, although present it was not loaded.
    >>
    >> This set of diskettes booted the box that created them and one other, but not
    >> the new box. The failure occurred when loading from diskette 2, and Warp kindly
    >> created a popuplog on the diskette.
    >>
    >> I will be grateful if you will suggest what I should try next.
    >>

    >
    >
    >OS/2 had a problem with the Athlon 64 running more than 512mb of memory
    >if the 'testcfg.sys' and 'apm.sys' drivers were loaded in the config.sys
    >file. You could work around the problem by either using 512mb or less
    >of memory or by remming out the testcfg.sys and apm.sys drivers in
    >config.sys. This problem was fixed in kernel 103a and also in 104a, the
    >final OS/2 kernel. There were also sometimes problems with traps when
    >loading the ibmint13.i13 driver in config.sys. This is an old fallback
    >disk controller driver that most systems do not need. In all cases, the
    >problem would appear as a trap during booting and the fix was to rem out
    >the statement. Finally, some systems have a problem with OPL3.SYS so try
    >remming that out.




    Add to my steps above:-

    In config.sys, rem device=testcfg.sys; that was the culprit.

    I can't thank you enough David.

    I copied the aicu320.add to the hard drive and edited config.sys. The hard
    drive booted but the Adaptec driver failed to load and wrote an
    Adaptec error code to the screen (c0003003h). The mystery is why the
    driver loaded from the floppies but not from the hard disk.


+ Reply to Thread