Re: SATA drives

Maybe more help here ..

Marc wrote:


I will have to download the current version before doing anything
else... Now I have to remember how to compile the license into
the .ISO disk image file.

Unless I don't understand whatever with DFSEE, you have to update your license code if his toolset moves forward off 7, for example, to 8 level code. I've done this every time as needed with BMT Micro here in the USA now able to take USPO or Western Union money orders for the US25$ or so for the renewal. Then they can cross-pay that to Mensys for the new update key just fine.

Saves the credit card mess and ID mashing and whatever. If you need this service, call Barb at BMT Micro and she can help you get this done very well from here in the USA or North America using these to simple and cheap money order formats.

I believe I'm running 1.6.?

OK, if this is Dani's driver, the last level of her code that would work as a renamed driver for OS/2 to the IBM1S506.ADD name was I think 1.7.10 per my notes. I saved that package and have it installed on my Warp 4 boxes where it works just fine. As well, that way I can make floppy diskettes for the utility diskette OS/2 needs for the Warp4 boxes without any issues about driver names that don't match and so on. That's why I kept the 1.7.10 code set.


ML> That level of her code cannot be just re-named to
ML> IBM1S506.ADD. and it must have her coordinated ATAPI driver
ML> as well instead of the IBM code to work if you need that.

I don't think 1.6.? can be renamed either, but I may be wrong on
that. Is the SATA drive seen as an ATAPI device?

Well, I think the 1.7 level code can be renamed. But it isn't necessarily the way I saw that made sense for utility diskettes and OS/2 install diskettes at that point.

As to 1.6 level code working with SATA drives seen as an ATAPI device, I can't speak to that. All I know is that using the later code here it sees and works fine with SATA drives.

The box I;m posting this from is not an SATA drive box, but a SCSI box. The CONFIG.SYS file entries that are related here on it are:

BASEDEV=DANIS506.ADD /A:0 /P:1F0 /IRQ:14 /U:0 /V

REM ** IDE CD-ROM SUPPORT
REM BASEDEV=IBMIDECD.FLT
REM ** IDE CD-ROM SUPPORT needed for later devices plus above only need
REM BASEDEV=IBMATAPI.FLT

BASEDEV=DaniATAPI.FLT /!SCSI



ML> Using DFSEE you can do a floppy diskette boot run, then see
ML> both the IDE and SATA drive in Jan's toolset.

> > I've only used the CD to boot to DFSEE. Should work just
> > as well I suppose. (?)

Yes .. and depending on what is really needed for the hard drive SATA, IDE and CD Rom device drivers, you can go forward beyond the CD boot run if you have not updated all this stuff and created a more recent bootable CD that has all the fixes there.

> Well, the folks at Microage here which have worked very
> carefully with me for some 20 years now were STUNNED when I
> took in a DOS floppy diskette to them.

It is surprising indeed that MS-DOS 6.2.x can allow DFSEE to even
find, much less work with an HPFS, NTFS or any other "Non-DOS"
partition. Interesting indeed!

That was what was so cunning about this!

> If you go to the DFSEE menu and select an item to work with
> from even the DOS floppy boot, you will get to choose a hard
> disk to work with. Then you swing right on the menu master
> folder choices. You pick the COPY option.

IIRC, there is also a "clone" option presented on the pull-down.
Is that not correct? What is the difference between the "COPY"
and the "CLONE" operations? ... Or am I thinking of some other
program.(?)

I think I chose the wrong word here. "CLONE" is correct.

> You just tell it to copy the whole drive to another drive.
> Whole OS/2, LVM info, everything just fine. Whoosh, Off it
> goes and does it.

Err .. clone ...

What happens if the drives are a different size? With Ghost, if
the new drive is larger, it will do the drive copy operation and
seemingly autoformat the remaining unused space in the partition
of the target drive. How's that work with DFSEE?

DFSEE used this way behaves exactly the same way. It auto creates the new hard drive with the same parameters as the smaller original drive. It then winds up with the larger drive just showing 'free space' beyond what the smaller original drive operation consumed.


I don't use DHCP on any of the OS/2 machines; all are fixed IP.

OK, then that is possibly why you have never run into the horrible crash operations with DHCP in the past. What happened is that every time the OS/2 box with DHCP opened a new DOS-VDM session, it failed to clear the file handle for AUTOEXEC.BAT or whatever form of that you use in the DOS-VDM initialization for that object! Well, after days of renewal of DHCP leases and playing with DOS-VDM's in OS/2, the box ran out of available file handles! You could look at the box with THESEUS and see line after line of AUTOEXEC.BAT or whatever still 'in use' that simply were not.

IBM released test code to cure this and it was, per my memory, formally released in Fix Pack XRC05 for MCP2. If you didn't install that but chose to stay with an earlier Fix Pack, they also released a custom fix for the issue that at least started with a custom DHCPCD.EXE dated February 9, 2004, that began this process. The formal total fix was eventually cast into the Fix Pack cauldren itself later, per my recall. The formal file which was cast into Fix Pack 17 for Warp 4 as well as used in MCP2 is the same size in bytes of 256127 bytes, but is dated 5-21-04 in the case of Warp 4 here and is exactly the same file which eventually wound up in the MCP2 machines also in the MPTN\BIN directory. If you do not have that file, as far as I know you are seriously at risk for crazy lockups and system failures in any version of OS/2 from the bug.


Here is what SYSINFO tells me I'm running:
==============cut==============
CPU: Intel Pentium 4 0Kb Cacche at 2337.9MHz (Family:15 Model:3
Stepping:3)
Memory: Physical: 479.6Mb ( 16.5% Used), SwapFile: 2.0Mb
Video: Res: 1024 x 768 x 16777216 Colors, Intel i865 Springdale-G
(Build 23), 31.8Mb Ram
Multimedia: CD: IDE CDROM Drive, Audio/Video: OS/2 Universal
Audio
Version: OS/2 4.51 US (Convenience Package -
OS/2 Warp 4 Base Operating System)
Kernel level: 14.103 (from WSeB CP#2/Warp 4 CP#2 PostFix)
FixPack level: WSeB CP#1/Warp 4 CP#1 FixPack #5 US (XR0C005)
DOS Support: Installed.
Printer/Queue: LS:\\WIN98C-XP\EPSONSTY
==============cut==============

OK, that seems to mean you are updated to XRC005 then. At this point, your Kernel level probably ought to be moved up to the 14.104a release Scott made which is available from several OS/2 related BBS systems per what I recall. At any rate that is the version I'm using on all the MCP2 boxes here.


> I known that there have been people who have been unhappy
> with XRC05 with failures. But I've never seen this on any of
> a large number of systems here. At least XRC04, I guess, is
> really needed. Together with kernel updates past this.

I suppose then that I should update the kernel on all the
machines, yes/no?

Not sure. Pay attention to what others here may suggest. Hopefully some others will chime in here and comment.

> > This contains fixes since xr_e002/xr_m015/mcp/acp.
> > Important note: If you use the OS/2 SES facility,

Not familiar with SES. Describe please.

Blank expression here too. I know there is a toolset which has been released that lets you upgrade the kernel with the ability to back out the change and revert to what was there before you upgraded.

> > Finally, note that os2ldr is only required for the >64mb
> > memory detection mentioned below.

I presume that the os2ldr is part of the kernel upgrade you
mentioned above?

Yes ..

Here's what I use to upgrade the released packages I call UPKERNEL.CMD that is used in the C:\ root boot directory here for OS/2:

echo off
echo --------
echo UPKERNEL.CMD for OS/2 Warp 4.5 echo Last revised on 23-Mar-2003
echo 
echo Place the desired W4####.ZIP diskette in drive A.
echo Enter the command UPKERNEL W4#### to start process.
echo --------
echo 
echo 
pause
dir A:%1.ZIP

echo 
echo If not correct enter CRTL C below
pause
c:
cd c:\
copy a:%1.zip
unzip -t %1.zip

echo 
echo If archive did not test correct enter CRTL C below
pause
c:
cd c:\
copy a:%1.zip
unzip -t %1.zip

echo 
echo If archive did not test correct enter CRTL C below
pause

attrib -r -s -h os2krnl
attrib -r -s -h os2ldr
if exist c:\os2\system\trace\save\*.tdf goto doneit

copy os2krnl os2krnl.sav
copy os2ldr os2ldr.sav
md c:\os2\system\trace\save
copy \os2\system\trace\*.tdf c:\os2\system\trace\save

:doneit

unzip -o %1.zip

Hope this helps.

--


--> Sleep well; OS2's still awake! ;)

Mike Luther
.

Relevant Pages

  • Re: 500GB USB drive
    ... I can not figure out how to 'eject' it that does NOT need a chkdsk /f ... recall ever trying it with the Drives object. ... As well as the entire eject issue here, has anyone noticed that if you operate with a CD-ROM in the appropriate drive tray, use it, then EJECT it 'normally', OS/2 has another interesting issue for me? ... An example of this is that I routinely do a complete CD-RW disk of tons of directories in which I store critical backup and support files. ...
    (comp.os.os2.setup.storage)
  • Re: Need Help with a DOS script (if possible)
    ... Closes Command Prompt ... echo Checking the target folder xxx%Target%yyy ... Will this work on either network drives, ...
    (microsoft.public.windowsxp.general)
  • RE: cannot install from existing UFS thumb drive with sysinstall
    ... There is a outstanding PR on sysinstall from usb flash drive which is now ... The sysinstall install program needs to be updated to use ... usb drives as the source of the install media. ... echo " " ...
    (freebsd-questions)
  • Re: bad news
    ... still can't get bootman to install, and have tried at every step of this effort. ... Since I wanted the other drives to be logical, for easy maintenance, I guess it ... someone knew a way to use grub to chainload an OS/2 bootable logical drive ... to really operate smoothly with the 10krpm Ultrastar and Cheetah LVD drives. ...
    (comp.os.os2.apps)
  • Re: "U3" USB Flash Memory
    ... I recently purchased a "Sandisk Cruzer Micro 4GB with U3 technology", and I can access it under OS/2 4.51 FP3. ... The so called "U3 technology" is only a means to install windows 2000/XP applications on a flash drive, so that the apps can be launched from the flash drive on any machine. ... The drive was NOT immediately accessible under OS/2, due to the way the partition table is written. ... the 4.51 LVM will also fix partition tables on you hard drives if you have the unfortunate idea to run "Norton Ghost" to back up your system. ...
    (comp.os.os2.misc)
Loading