
                   comp.os.os2.setup.storage        (Usenet)

                 Saturday, 11-Dec-1999 to Friday, 17-Dec-1999

+----------------------------------------------------------------------------+

From: not@here.invalid                                  11-Dec-99 04:12:11
  To: All                                               11-Dec-99 03:29:26
Subj: Re: Is it safe to use PQMagic version 3.x on 10+gig UDMA drives ???

From: not@here.invalid (Braxton Burrsaddle)

On Thu, 9 Dec 1999 23:14:44, xyxmadxyx@xyxziplinkxyx.xyxnetxyx (mark 
davidson) say:
> 
> isn't the sticky bit that PM3 works OK on disks > 8 gb but only if the
> partitions are first created using os/2 fdisk? 

Haven't seen this behavior on my 10.8 GB Fujitsu.  

However.  In a 'mixed' environment where a partition is NTFS, do NOT 
use PM<v4 if you have applied NT SP4.  You =will= trash the NTFS 
partition.  There is an error message you can look up on PQ's web site
that tells you so - after the NT partition is rendered useless.

zgzw2@dnzai.com  :  reply-to bogus, remove z's to construct email 
address.

It don't mean a thing ... if it ain't got that other thing.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: lsunley@mb.sympatico.ca                           11-Dec-99 05:46:00
  To: All                                               11-Dec-99 03:29:26
Subj: Re: IDE ZIP drive was (No subject)

From: lsunley@mb.sympatico.ca (Lorne Sunley)

On Sat, 11 Dec 1999 02:28:09, rgibson@ix.netcom.com (Ron Gibson) 
wrote:

> On Sat, 11 Dec 1999 01:00:54, lsunley@mb.sympatico.ca (Lorne Sunley) 
> wrote:
>  
> > > How about configuring it? What swiches are required on IBM's IDE driver.
>  
> > The IDE ZIP drive requires that you have the latest update
> > for the IDE device drivers installed and that you are using
> > Fixpack 6 for Warp 4 or later to obtain the removable device
> > support.
> 
> Hmmm...I'm using W3 FP 40 and the DANIS IDE driver. Any problems there?

I should have mentioned that for Warp 3 FP 35 or greater
is required. You should be OK with 40. DANIS506.ADD
works fine AFAIK.

> 
> > Device drivers have been moved to their own fixpack
> > series so if you install FP 12 you should also install
> > the DD01 fixpack.
> > 
> > You can obtain these through RSU updates or through
> > the FTP site ftp://ftp.software.ibm.com/ps/products/os2/
> > 
> > With the IDE ZIP you just connect it to the IDE cable
> > (checking for Slave or Master of course) and if you
> > have the device support installed it comes up automatically.
> > 
> > The base device driver that is required (besides IBM1S506.add)
> > is IBMATAPI.FLT
>  
> > Partition the cartridge and format for FAT or HPFS.
> 
> So then is it seen as a HDD, IOW appears in FDISK?

FDISK finds it and treats it as a hard drive. That's why
you can partition it. IIRC when you first use a cartridge
irt will appear to have some kind of partition. Use
FDISK to delete what's there and then allocate the
partition. You can have more than one partition on
the cartridge if you want. There is some obscure
command line parameters for the driver that allow 
you to reserve drive letters for multi-partition cartridges
but I can't remember what they are....

--

Lorne Sunley

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: tomp@st.net.au                                    11-Dec-99 15:26:08
  To: All                                               11-Dec-99 03:29:27
Subj: Re: Is it safe to use PQMagic version 3.x on 10+gig UDMA drives ???

From: "Tom Perrett" <tomp@st.net.au>

On Fri, 10 Dec 1999 19:38:44 +0000 (GMT), Trevor Hemsley wrote:

>Make the OS/2 utility diskettes (not connected with Partition Magic at
   ETC., ETC., ETC.

Thanks for that Trevor.

Tom


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Customer of Telstra Big Pond Direct (1:109/42)

+----------------------------------------------------------------------------+

From: rwatts@clear.net.nz                               11-Dec-99 21:22:20
  To: All                                               11-Dec-99 05:07:10
Subj: Fujitsu 13gig  MPD3130AT Drive

From: "Roger Watts" <rwatts@clear.net.nz>

For the same reason I am feeling dumb asking this question, I feel kind of
clever at the same time. I have a file server running warp3 in a small
office that has been turned off 4 times in 5 years. I am upgrading this for
various reasons and have chosen the above drives. I have problems with 528mb
limits I think (fwiw the file IBM1S506.ADD has a date stamp 4-21-95).
I think my major problem when I originally installed was a 2x CD-Rom and how
what was the number for the local BBS.
Any ideas as to whether I can resurect the old install cd or should I
upgrade of get FP 9xxx or whatever it is up to?
All replies appreciated.

cheers,
Roger
roger@natex.co.nz



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: CLEAR Net New Zealand (1:109/42)

+----------------------------------------------------------------------------+

From: Trevor-Hemsley@dial.pipex.com                     11-Dec-99 10:45:06
  To: All                                               11-Dec-99 10:16:29
Subj: Re: Fujitsu 13gig  MPD3130AT Drive

From: "Trevor Hemsley" <Trevor-Hemsley@dial.pipex.com>

On Sat, 11 Dec 1999 21:22:41 +1300, Roger Watts wrote:

->For the same reason I am feeling dumb asking this question, I feel kind of
->clever at the same time. I have a file server running warp3 in a small
->office that has been turned off 4 times in 5 years. I am upgrading this for
->various reasons and have chosen the above drives. I have problems with 528mb
->limits I think (fwiw the file IBM1S506.ADD has a date stamp 4-21-95).

Any version of IBM1S506.ADD dated prior to about January 1998 has problems
with IDE drives greater than 4GB in size. You need to obtain
ftp://service.boulder.ibm.com/ps/products/os2/os2ddpak/idedasd.exe and run
it to get the latest version that supports drives greater than 8GB.


Trevor Hemsley, Brighton, UK
(Trevor-Hemsley@dial.pipex.com or 75704.2477@compuserve.com)



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: UUNET WorldCom server (post doesn't reflect views
(1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        11-Dec-99 11:00:13
  To: All                                               11-Dec-99 10:16:29
Subj: JFS problem

From: jpolt@bradnet.legend.co.uk (John Poltorak)

After tidying up some directories on a JFS formatted partition, I have
strange file left which cannot be deleted, or even accessed:-

20-04-98   4:27p      7971          35  MBSUP

I can't 'TYPE' this file, although I am able to create a file with the same
name
and delete that.

CHKDSK /f:3 does not remove this file although it did initially clean up the
disk when several thousand instances of this file appeared.

Any suggestions about how to remove this file would be appreciated...

I guess I will have to resort to reformating but I have 2GB of data on this
drive.

--
John


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: donnelly@tampabay.rr.com                          11-Dec-99 14:16:25
  To: All                                               11-Dec-99 14:33:26
Subj: Re: JFS problem

From: donnelly@tampabay.rr.com (Buddy Donnelly)

On Sat, 11 Dec 1999 11:00:26, jpolt@bradnet.legend.co.uk (John 
Poltorak) wrote:

> After tidying up some directories on a JFS formatted partition, I have
> strange file left which cannot be deleted, or even accessed:-
> 
> 20-04-98   4:27p      7971          35  MBSUP
> 
> I can't 'TYPE' this file, although I am able to create a file with the same
name
> and delete that.
> 
> CHKDSK /f:3 does not remove this file although it did initially clean up the
> disk when several thousand instances of this file appeared.
> 
> Any suggestions about how to remove this file would be appreciated...
> 
> I guess I will have to resort to reformating but I have 2GB of data on this
drive.

Reboot to floppies, or just Alt-F1 to a command line session, and try 
deleting (with DEL) from there. 

I don't know what that filename is, but I doubt that it's a JFS issue.
There is a longstanding PMSHELL issue that can keep it from being able
to delete certain files, sometimes if they're corrupted, sometimes if 
they come from Open32 code. It acts similar to the CodePage problem 
that can keep you from deleting (under PMSHELL) filenames containing 
certain characters and written with some CPs, but during sessions with
different CPs.

-- 

Good luck,

Buddy

Buddy Donnelly
donnelly@tampabay.rr.com


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: RoadRunner - TampaBay (1:109/42)

+----------------------------------------------------------------------------+

From: matthickman@my-deja.com                           11-Dec-99 23:39:27
  To: All                                               11-Dec-99 21:20:14
Subj: Re: TP 760CD with Dock/2

From: Matt Hickman <matthickman@my-deja.com>

In article <81ma4f$g9e$1@nnrp1.deja.com>,
  Matt Hickman <matthickman@my-deja.com> wrote:
>
>
> My Thinkpad 760CD locks up on bootup when I load the driver for
> the Dock/2's built in SCSI.  It worked with my original Wap 4
> install. I think it stopped working as a result of installing an IDE
> busmaster driver a year or so ago (I was too lazy to back it out
> at the time).  I did not need to use the SCSI then, but now I
> would like to use the SCSI to hook up a JAZZ drive.

Got the system to access the Jazz drive and not lockup
on boot-up by removing the /F:0,... parameter from the scsi
aha152x.add driver.  Basically as the result of desperation
experimentation.  Nor did I find what the /F:0, etc was for --
it had been there since the original Warp install in Oct 1996.

BASEDEV=AHA152X.ADD /A:0 /F:0,1,2,3,4,5,6

Does anyone know what the /F paramneter is for?  Or even the
/A parameter?

Thanks.

--
Matt Hickman
I don't even see how a four-dimensional coffee cup
could even hold coffee, much less a whole galaxy.
              - Robert A. Heinlein (1907-1988)


Sent via Deja.com http://www.deja.com/
Before you buy.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Deja.com - Before you buy. (1:109/42)

+----------------------------------------------------------------------------+

From: rde@tavi.co.uk                                    11-Dec-99 23:59:26
  To: All                                               11-Dec-99 21:20:15
Subj: Re: JFS problem

From: rde@tavi.co.uk (Bob Eager)

On Sat, 11 Dec 1999 11:00:26, jpolt@bradnet.legend.co.uk (John 
Poltorak) wrote:

> After tidying up some directories on a JFS formatted partition, I have
> strange file left which cannot be deleted, or even accessed:-
> 
> 20-04-98   4:27p      7971          35  MBSUP

Sounds to me like it has a non-printing character in the filename.

Have you tried using wildcards? Being careful not to delete files you 
want.

-- 
Bob Eager
rde at tavi.co.uk
PC Server 325; PS/2s 8595*3, 9595*3 (2*P60 + P90), 8535, 8570, 9556*2,
8580*6,
8557*2, 8550, 9577, 8530, P70, PC/AT..

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Tavi Systems (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        12-Dec-99 12:04:06
  To: All                                               12-Dec-99 10:13:27
Subj: Re: JFS problem

From: jpolt@bradnet.legend.co.uk (John Poltorak)

In <176uZD2KcidF-pn2-4dbLuVdFi4Lw@man-140.dialup.zetnet.co.uk>, rde@tavi.co.uk 
(Bob Eager) writes:
>On Sat, 11 Dec 1999 11:00:26, jpolt@bradnet.legend.co.uk (John 
>Poltorak) wrote:
>
>> After tidying up some directories on a JFS formatted partition, I have
>> strange file left which cannot be deleted, or even accessed:-
>> 
>> 20-04-98   4:27p      7971          35  MBSUP
>
>Sounds to me like it has a non-printing character in the filename.

No, there is some sort of file corruption here.

I can create a new file with the same name in this directory and delete that
one.

If I run SysFiletree on this direcory, CPU gets pegged at 100% and never
finishes.

If I try using the DRIVES object the system locks up completely when I open
the folder containing this file and a re-boot is required. 

>Have you tried using wildcards? Being careful not to delete files you 
>want.

Looks like a re-format is in order....

>
>-- 
>Bob Eager
>rde at tavi.co.uk
>PC Server 325; PS/2s 8595*3, 9595*3 (2*P60 + P90), 8535, 8570, 9556*2,
>8580*6,
>8557*2, 8550, 9577, 8530, P70, PC/AT..
--
John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: gateway@tsc.bbs.de                                12-Dec-99 15:00:13
  To: All                                               12-Dec-99 14:24:13
Subj: When 32bit CHKDSK first came out...

From: Armin Schaefer <gateway@tsc.bbs.de>

Hallo Charles!

Antwort auf eine Nachricht von Charles Christacopoulos an Armin Schaefer:

 CC> Sorry I am being nasty about it, but nearly all of the
 CC> hardware/drivers problems I have had with OS/2 related to Adaptec
 CC> controllers.  Things are so smooth since I binned them.

 CC> I hope it gets fixed, but it might be worth your while checking DPT
 CC> too (I know you now got the adapter).
That's no problem! I've got the chance to get a new U2W SCSI controller free
of charge.

 CC> Until DPT got to the new
 CC> generation of U2W cards with I2O technology they worked with a kind
 CC> of generic driver for all their products. Nice :-)  (OS/2 Warp 4 to
 CC> my surprise runs on an I2O card without any specific I2O drivers).
In germany the DPT controllers are not known well. It would be a big problem
to catch such a U2W SCSI controller. What about Tekram or Dawicontrol? Do
these controllers work with the same drivers? Has anyone these U2W SCSI
controllers working under OS/2 with large hard drives?

Ciao, Armin!

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: TsC Fidonet /-/ Internet Gateway (1:109/42)

+----------------------------------------------------------------------------+

From: dcasey@ibm.net                                    12-Dec-99 10:14:28
  To: All                                               12-Dec-99 14:24:14
Subj: Re: TP 760CD with Dock/2

From: dcasey@ibm.net (Dan Casey)

According to the online docs, the /A: parameter is used to point  to
the Adapter Number (in case of multiple adapters). There is no /F
parameter on that driver.

In article <82uncb$c80$1@nnrp1.deja.com>,
Matt Hickman <matthickman@my-deja.com> wrote:
>In article <81ma4f$g9e$1@nnrp1.deja.com>,
>  Matt Hickman <matthickman@my-deja.com> wrote:
>>
>>
>> My Thinkpad 760CD locks up on bootup when I load the driver for
>> the Dock/2's built in SCSI.  It worked with my original Wap 4
>> install. I think it stopped working as a result of installing an IDE
>> busmaster driver a year or so ago (I was too lazy to back it out
>> at the time).  I did not need to use the SCSI then, but now I
>> would like to use the SCSI to hook up a JAZZ drive.
>
>Got the system to access the Jazz drive and not lockup
>on boot-up by removing the /F:0,... parameter from the scsi
>aha152x.add driver.  Basically as the result of desperation
>experimentation.  Nor did I find what the /F:0, etc was for --
>it had been there since the original Warp install in Oct 1996.
>
>BASEDEV=AHA152X.ADD /A:0 /F:0,1,2,3,4,5,6
>
>Does anyone know what the /F paramneter is for?  Or even the
>/A parameter?
>
>Thanks.
>
>--
>Matt Hickman
>I don't even see how a four-dimensional coffee cup
>could even hold coffee, much less a whole galaxy.
>              - Robert A. Heinlein (1907-1988)
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.

--
**************************************************************
*  Dan Casey                                                 *
*  President                                                 *
*  V.O.I.C.E. (Virtual OS/2 International Consumer Education *
*  http://www.os2voice.org                                   *
*  Abraxas on IRC                                            *
*  http://members.iquest.net/~dcasey                         *
*  Charter Associate member, Team SETI                       *
*  Warpstock 99 in Atlanta  http://www.warpstock.org         *
**************************************************************
*  E-Mail (subject: Req. PGP Key) for Public Key             *
**************************************************************

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: V.O.I.C.E., Indianapolis, IN (1:109/42)

+----------------------------------------------------------------------------+

From: mgreene@exis.net                                  12-Dec-99 13:30:24
  To: All                                               12-Dec-99 16:45:15
Subj: TRAPDUMP to a ZIP100 (SCSI)

From: "Michael K Greene" <mgreene@exis.net>

Ok, I understand the TRAPDUMP process but I can not get the dump to my ZIP100
(SCSI) drive. The command say that it can not find the drive. Something
wrong?

Michael K Greene <mgreene@exis.net>     |      OS/2 Warp / Linux / Win95-311



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Exis Net Inc (1:109/42)

+----------------------------------------------------------------------------+

From: nospam_n.saxon@mindspring.com                     12-Dec-99 13:40:21
  To: All                                               12-Dec-99 16:45:15
Subj: Re: Formatting a 100 mb zip drive to HPFS format

From: "Nick Saxon" <nospam_n.saxon@mindspring.com>

On Fri, 10 Dec 1999 13:18:42 -0500, Scott Vetter wrote:

>Richard:
>
>    Thank you for the info.   I'll give it a try.
>
>Scott
>
>-----------------------
>
>Richard Johnston wrote:
>
>> Scott Vetter <svetter@ameritech.net> wrote:
>> >    I have OS/2 V4 with an IOMEGA 100 Mb zip drive attached via a
>> > parallel port.  Is there a way to format a disk with the HPFS format?
>>
>> You have to use fdisk (os2) first. create a partiton on the zip disk, save
>> it, then you can use the command "format x: /fs:hpfs" Works like a charm
>>
>> dj
>


I don't believe it's possible with parallel port. IBM's IDEDASD.EXE support
for
Removable Media states clearly that it's possible if and only if the device
support
comes in the form of .ADD driver. Probably your Iomega ZIP comes with a .sys
driver
for parallel port connection.

Nick Saxon


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Golde Code Development (1:109/42)

+----------------------------------------------------------------------------+

From: Trevor-Hemsley@dial.pipex.com                     12-Dec-99 18:58:18
  To: All                                               12-Dec-99 16:45:15
Subj: Re: TP 760CD with Dock/2

From: "Trevor Hemsley" <Trevor-Hemsley@dial.pipex.com>

On Sun, 12 Dec 1999 10:14:56 -0500, Dan Casey wrote:

->According to the online docs, the /A: parameter is used to point  to
->the Adapter Number (in case of multiple adapters). There is no /F
->parameter on that driver.

It's there in the driver itself but there's no doc about what it does.


Trevor Hemsley, Brighton, UK
(Trevor-Hemsley@dial.pipex.com or 75704.2477@compuserve.com)



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: UUNET WorldCom server (post doesn't reflect views
(1:109/42)

+----------------------------------------------------------------------------+

From: rwatts@clear.net.nz                               13-Dec-99 08:14:26
  To: All                                               12-Dec-99 19:56:10
Subj: Re: Fujitsu 13gig  MPD3130AT Drive

From: "Roger Watts" <rwatts@clear.net.nz>

Many thanks Trevor.


Trevor Hemsley <Trevor-Hemsley@dial.pipex.com> wrote in message
news:geribeurzfyrlqvnycvcrkpbz.fml2fc0.pminews@news.dial.pipex.com...
> On Sat, 11 Dec 1999 21:22:41 +1300, Roger Watts wrote:
>
> ->For the same reason I am feeling dumb asking this question, I feel kind
of
> ->clever at the same time. I have a file server running warp3 in a small
> ->office that has been turned off 4 times in 5 years. I am upgrading this
for
> ->various reasons and have chosen the above drives. I have problems with
528mb
> ->limits I think (fwiw the file IBM1S506.ADD has a date stamp 4-21-95).
>
> Any version of IBM1S506.ADD dated prior to about January 1998 has problems
> with IDE drives greater than 4GB in size. You need to obtain
> ftp://service.boulder.ibm.com/ps/products/os2/os2ddpak/idedasd.exe and run
> it to get the latest version that supports drives greater than 8GB.
>
>
> Trevor Hemsley, Brighton, UK
> (Trevor-Hemsley@dial.pipex.com or 75704.2477@compuserve.com)



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: CLEAR Net New Zealand (1:109/42)

+----------------------------------------------------------------------------+

From: hemo_jr@attglobal.net                             12-Dec-99 17:27:18
  To: All                                               12-Dec-99 21:19:04
Subj: Re: TP 760CD with Dock/2

From: hemo_jr@attglobal.net (Matt Hickman)

In <wv7U4kDg6NLL090yn@ibm.net>, on 12/12/99 
   at 10:14 AM, dcasey@ibm.net (Dan Casey) said:
>According to the online docs, the /A: parameter is used to point  to the
>Adapter Number (in case of multiple adapters). There is no /F parameter
>on that driver.
>>  Nor did I find what the /F:0, etc was for --
>>it had been there since the original Warp install in Oct 1996.
>>
>>BASEDEV=AHA152X.ADD /A:0 /F:0,1,2,3,4,5,6

I wonder how the /F: parameter got put in the config.sys?  Possibly 
it was set that way in one of the betas and stayed there because I didn't 
reformat and re-install.  I guess I paid for that :)  Let this be a lesson
for the younger folk out there to reformat after running a Beta!

The /F:0... must do something.  Because my system halts (It think when the 
HPFS.IFS is run) saying it can't read the hard drive when the parameter
is active in my config.sys.

-- 
Matt Hickman
  You may fancy being eaten by a dragon; I don't.  It's 
  humiliating.  And final.
                     Robert A. Heinlein (1907 - 1988)
                     _Glory Road_ 1963       




--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: frank_mckenney@mindspring.com                     13-Dec-99 14:21:22
  To: All                                               13-Dec-99 14:26:29
Subj: Re: TRAPDUMP to a ZIP100 (SCSI)

From: frank_mckenney@mindspring.com (Frank McKenney)

Michael,

You left off a Followup-To:  newsgroup, so I've set it to
comp.os.os2.misc

In <zterrarrkvfarg.fmn4rd0.pminews@news.exis.net>, "Michael K Greene"
<mgreene@exis.net> writes:
>Ok, I understand the TRAPDUMP process but I can not get the dump to my ZIP100
>(SCSI) drive. The command say that it can not find the drive. Something
>wrong?

I assume you've already set up the ZIP cartridge as FAT and given it the
correct name.

Given that this is for a standalone system dump (e.g.  "dump as much as
we can without depending on anything that might have been tromped on and
without disturbing anything"), I'd expect it to be using BIOS Int13h
calls to write the data to disk(ette).

Is your ZIP drive BIOS-addressable?  Or is it only available once OS/2
drivers have been loaded (which the standalone dump code has to assume
_might_ have been mangled)?


Frank McKenney, McKenney Associates
Richmond, Virginia / (804) 320-4887
E-mail: frank_mckenney@mindspring.com

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: McKenney Associates (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        13-Dec-99 16:06:15
  To: All                                               13-Dec-99 14:27:00
Subj: Optical disk ejects randomly

From: jpolt@bradnet.legend.co.uk (John Poltorak)

I have an IBM 128MB MO disk drive and find that it ejects the disk randomly
for no apparent reason.

Can anyone suggest a cause for this?

It is installed on an IBM PC Server 320 running WSeB.

--
John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: merlins@ibm.net                                   13-Dec-99 00:33:14
  To: All                                               13-Dec-99 14:27:00
Subj: Re: TP 760CD with Dock/2

From: Meinolf Sondermann <merlins@ibm.net>


Trevor Hemsley wrote:
> 
> On Sun, 12 Dec 1999 10:14:56 -0500, Dan Casey wrote:
> 
> ->According to the online docs, the /A: parameter is used to point  to
> ->the Adapter Number (in case of multiple adapters). There is no /F
> ->parameter on that driver.
> 
> It's there in the driver itself but there's no doc about what it does.
> 
> Trevor Hemsley, Brighton, UK
> (Trevor-Hemsley@dial.pipex.com or 75704.2477@compuserve.com)


Just a guess:

It may be a warmdocking option. When booting undocked it may force
the driver to load and accompanied with the appropiate parms reserve
a driveletter so that when docking without a boot, the attached
devices immediatly become available. I remember that there was such
an option for swapping floppy/CDROM without booting.

There once were some docs on warmdocking on IBM's Notebook support page.
Old link: http://www.us.pc.ibm.com/support/index.html .

Bye/2

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: pjfloyd@my-deja.com                               13-Dec-99 17:10:27
  To: All                                               13-Dec-99 17:04:10
Subj: Re: CDRECORD, MULTISESSION and editing OS2CDROM.DMD...

From: pjfloyd@my-deja.com

In article <TQzU48D5wSHJ090yn@erols.com>,
  mcbrides@erols.com (Jerry McBride) wrote:
> Ok you guys...

> I've been working on tackling the creation of multisession cdroms
> using warp connect, cdrecord 18a32, adaptec aha1522b and a yamaha
> 4416s...

I have:
Warp 4, Tekram SCSI card and a Yamaha 6416S.
And also a Tosh SD-M1201.

> The short story is, I have it working, but it's not 100% correct.

> With a "box stock" Warp connect system and fixpak #40, multisession
> is not possible using the above listed tools. However, it was
> discussed a while back that OS2CDROM.DMD could be edited with the
> name "YAMAHA" overlaying one of the other listed cdrom manufacturers
> and multisession would magically appear...

I guess this is more or less the case.

> Well, it does to some degree, but it's not perfect.

> First off, not having the source code to OS2CDROM.DMD makes it a
> bit difficult to know what is going on in those tables. But I
> would hazard a guess that they are a "feature support table"
> using oem names and specific model numbers to switch in code so
> that the desired features are available to the OS.

> No proof of this, but it's a strong suspicion.

You can download the source (or at least, I did) and all
the tools required to compile it. I did this for the above
two models.

I haven't yet been able to test this thoroughly. I've only one
multisession CD at the moment, though I expect I'll do
some more testing with a multisession CD-RW disk.


> Overwriting "TEXEL" with "YAMAHA" allows me to read multisession
> cd's with some minor difficulties. Namely there are garbaged
> directories listed at the root level, along with the "real"
> directories. The garbaged ones appear to be of
> totally bogus origins and writing my own multisession cd's results
> in the same behaviour. My written directories appear perfect,
> amongst garbage...

> It's kinda' a bummer as I was hoping for the usual flawless
> operations... but a hack is a hack... I'll leave it for someone
> else to polish up...

I may.

> Anyway, I use the following routine to "build" a multisession cd...

[snip - mkisofs]

> I believe you can keep doing this, up until your cd is full or you
> get tired...

I don't know so much about mkisofs.

> From the best that I can tell, I can write multisession cdroms
> without hacking the OS2CDROM.DMD file. Reading them is the problem...

> There was also a gentleman that mentioned that he had taken an
> old copy of cdrom drivers from IBM's website and was able to compile
> a driver that correctly handles multisession cd's. If you read
> this, contact me. I'd like totrade a few emails with you. :')

That could be me. I'll be in touch.

I've also crossposted to comp.os.os2.setup.storage, rather more
appropriate I think.

A bientot
Paul
--
Paul Floyd
Is atrophy a shiny cup?


Sent via Deja.com http://www.deja.com/
Before you buy.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Deja.com - Before you buy. (1:109/42)

+----------------------------------------------------------------------------+

From: letang.sybille@hydro.qc.ca                        13-Dec-99 18:08:16
  To: All                                               13-Dec-99 17:04:10
Subj: Re: Recovery lost data (HELP!!)

From: Sybille =?iso-8859-1?Q?L=E9tang?= <letang.sybille@hydro.qc.ca>

Hi,

I tried CHKDSK it's found a problem with my table partition.  I decide to
buy the Gammatech utilities, a lot of people recommended me.

Tank you,

Sybille.

Glen D wrote:

> On Wed, 8 Dec 1999 20:11:57, Sybille =?iso-8859-1?Q?L=E9tang?=
> <letang.sybille@hydro.qc.ca> wrote:
>
> > Hi!
> >
> > Does anyone know how can I retrieve my data on my HPFS drive? My file
> > table has been corrupted, but I desperately need the data on my drive.
> >
> > What about Gammatech?  It is a good software?
> >
> > Sybille
> >
> Have you tried CHKDSK?  What errors, if any, does it give?
>
>
> Glen D
> -<remove Z from my e-mail Address>-

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: IREQ http://www.ireq.ca/ (1:109/42)

+----------------------------------------------------------------------------+

From: shSoPdgAeM@nctr.fda.gov                           13-Dec-99 14:05:16
  To: All                                               13-Dec-99 17:04:11
Subj: Does NTFS preclude the installation of Warp 4?

From: Steve Hodge <shSoPdgAeM@nctr.fda.gov>

I received a Pentium III 500 MHz with a 13.3 GB WDC IDE with Windows NT
already installed. I installed PartitionMagic 4.0 and backed up the 4GB
Windows NT partition before trying to installing OS/2 Warp 4.  I created
a set of Utility Disks from a Warp 4 FP 12 machine to use with a Warp 4
CD-ROM, but still I can't get an OS/2 primary partition to boot.

I set up two machines like this previously.  Same hard-drive model, the
only difference was setting up on NT preinstalled instead of Win95
preinstalled.
   Another difference is installing Partition Magic before getting down
to business with OS/2.   I was able to get by with Warp 4 FP 9 on the
earlier installations.

The installation seems to go fine until it's time to reboot, then I
receive either a blinking cursor on a black screen, or  a complaint from
NT that "a kernel file is missing from your disk ... insert a system
diskette and restart"


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: NatCenToxRes (1:109/42)

+----------------------------------------------------------------------------+

From: mgreene@exis.net                                  13-Dec-99 15:21:11
  To: All                                               13-Dec-99 19:44:00
Subj: Re: TRAPDUMP to a ZIP100 (SCSI)

From: "Michael K Greene" <mgreene@exis.net>

On 13 Dec 1999 14:21:44 GMT, Frank McKenney wrote:

>
>Michael,
>
>You left off a Followup-To:  newsgroup, so I've set it to
>comp.os.os2.misc
>
>In <zterrarrkvfarg.fmn4rd0.pminews@news.exis.net>, "Michael K Greene"
<mgreene@exis.net> writes:
>>Ok, I understand the TRAPDUMP process but I can not get the dump to my
ZIP100
>>(SCSI) drive. The command say that it can not find the drive. Something
>>wrong?
>
>I assume you've already set up the ZIP cartridge as FAT and given it the
>correct name.
>
>Given that this is for a standalone system dump (e.g.  "dump as much as
>we can without depending on anything that might have been tromped on and
>without disturbing anything"), I'd expect it to be using BIOS Int13h
>calls to write the data to disk(ette).
>
>Is your ZIP drive BIOS-addressable?  Or is it only available once OS/2
>drivers have been loaded (which the standalone dump code has to assume
>_might_ have been mangled)?

Frank,

The ZIP100 is running off an Adaptec 1505 and depends on the SCSI drivers.

>Frank McKenney, McKenney Associates
>Richmond, Virginia / (804) 320-4887
>E-mail: frank_mckenney@mindspring.com
>

Michael K Greene <mgreene@exis.net>     |      OS/2 Warp / Linux / Win95-311



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Exis Net Inc (1:109/42)

+----------------------------------------------------------------------------+

From: lsunley@mb.sympatico.ca                           14-Dec-99 02:00:21
  To: All                                               14-Dec-99 03:29:05
Subj: Re: Adding IDE CDROM - will drive letters change?

From: lsunley@mb.sympatico.ca (Lorne Sunley)

On Tue, 14 Dec 1999 01:38:38, "Terry Raymond" 
<traymond@craftedsmalltalk.com> wrote:

> Hi
> 
> I am thinking of replacing my 2x cdrom, it has a Mitsumi interface,
> with an IDE CD-RW Drive and I would like to know if adding one
> would cause my existing drive letters to change.  I presently have
> a 3.6 GB drive on the primary controller partitioned with
> C: as a primary bootable partition and three additional logical
> drives in the extended partition.  OS/2 is on one of the logical
> drives, the system boots into System Commander.
> 
> If I add the CD-RW drive as the slave on the secondary controller
> will my OS/2 drive letter change?

The CD-ROM drive letter is always assigned AFTER
all the drive letters for HD and removable disks
(like ZIP or JAZ or ORB etc)


--

Lorne Sunley

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: gjoseph2@home.com                                 14-Dec-99 02:52:04
  To: All                                               14-Dec-99 03:29:05
Subj: Re: Internal LS-120 as B-Drive fails to work

From: "Gary Joseph" <gjoseph2@home.com>

Same product different question.  Have been trying to get OS/2 to install
from an LS-120 as the only floppy type device in the system.  Get through
startup disks, then get message saying system can't operate hard / removable
disks.  Have tried latest NEWDASD download.  Any ideas?

Gary


Billy Ko <billko@postoffice.worldnet.att.net> wrote in message
news:ovyyxbcbfgbssvprjbeyqargnggarg.flzths0.pminews@netnews.worldnet.att.net
...
> On Mon, 29 Nov 1999 00:54:10 -0500, J. Ken Zur wrote:
>
> :>    Hi! I am running Warp 4. During my original install, for some reason
> :>the system ended up with an A and B floppy drive. Well my B is really
> :>the LS-120 and after adding the support for large/removable drives the
> :>LS-120 still doesn't work as a 120mg floppy. Attempts to Format "B"
> :>suggest a max size of 2.88mg.
>
> I used to have the same exact problem.  The latest IDEDASD fixes that, I
> believe.
>
> Bill
> Team OS/2
>
> -----
>
> OS/2 - If you want "productivity" to be more than a few
> four-letter words.
>
>
>


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network Canada (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               14-Dec-99 04:01:26
  To: All                                               14-Dec-99 03:29:06
Subj: Re: Does NTFS preclude the installation of Warp 4?

From: "William L. Hartzell" <wlhartzell@home.com>

Dear Steve:
I had the same symptoms when I installed Win98 second edition.  I found that
if MS large drive partition scheme was used OS/2 would crash just like you
described.  Solution is to partition the drive using Warp 4 fixpack 9 or
later.  The other problem with NT boot means that you must install NT
first.  NT will not like OS/2 written MBR, But it will install.  Do not
install Boot Manager, but reserve a space for it at the start of free space
until after you install NT!  If your drive has more than 1024 cylinders, do
not under any circumstances have a bootable partition include them.  Write a
FAT data partition there.  If you need more assistance, please e-mail me at
<wlhartzell@home.com>

Steve Hodge wrote:

> I received a Pentium III 500 MHz with a 13.3 GB WDC IDE with Windows NT
> already installed. I installed PartitionMagic 4.0 and backed up the 4GB
> Windows NT partition before trying to installing OS/2 Warp 4.  I created
> a set of Utility Disks from a Warp 4 FP 12 machine to use with a Warp 4
> CD-ROM, but still I can't get an OS/2 primary partition to boot.
>
> I set up two machines like this previously.  Same hard-drive model, the
> only difference was setting up on NT preinstalled instead of Win95
> preinstalled.
>    Another difference is installing Partition Magic before getting down
> to business with OS/2.   I was able to get by with Warp 4 FP 9 on the
> earlier installations.
>
> The installation seems to go fine until it's time to reboot, then I
> receive either a blinking cursor on a black screen, or  a complaint from
> NT that "a kernel file is missing from your disk ... insert a system
> diskette and restart"

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               14-Dec-99 04:08:18
  To: All                                               14-Dec-99 03:29:06
Subj: Re: Optical disk ejects randomly

From: "William L. Hartzell" <wlhartzell@home.com>

Dear John:
Did you try locking the drive?  If you did, have you tried the hacked
CDrom.dmd
that is available for cd changers?  Look for it on tim web page for new users
at os2 super site.  The PMSHELL.EXE has bugs and is the source of the problem,
I believe.

John Poltorak wrote:

> I have an IBM 128MB MO disk drive and find that it ejects the disk randomly
> for no apparent reason.
>
> Can anyone suggest a cause for this?
>
> It is installed on an IBM PC Server 320 running WSeB.
>
> --
> John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: istephan@NOSPAM.rodgau.netsurf.de                 14-Dec-99 07:44:09
  To: All                                               14-Dec-99 11:41:16
Subj: Re: DVD-ROM and OS/2 ?

From: istephan@NOSPAM.rodgau.netsurf.de (Ingo Stephany)

On Sat, 27 Nov 1999 20:07:35, reimers@theo.physik.uni-giessen.de 
(Roland Reimers) wrote:

> I am considering to acquire a new computer and like to take a DVD-ROM drive 
> instead of a CDROM. Does anybody know if there is one out there for OS/2 ? 
> ATAPI or SCSI, this does not matter for me. If there were only SCSI-DVDs
this 
> would be a strong argument for me to buy a SCSI-controller, too.
> Thanks in advance
> Roland

Hi, 
I'm using a "Creative Labs Encore Kit" which is containing a MPEG-card

and a DVD-ROM drive on my machine (WARP + W95 (for gaming)).

Warp is using the DVD-drive as CD-ROM just fine with the WARP  
included 
ATAPI-CDROM drivers.
Regards
Ingo Stephany 









--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Unspecified Organisation (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        14-Dec-99 10:13:21
  To: All                                               14-Dec-99 11:41:17
Subj: Re: Optical disk ejects randomly

From: jpolt@bradnet.legend.co.uk (John Poltorak)

In <3855C2D1.5866CA62@home.com>, "William L. Hartzell" <wlhartzell@home.com>
writes:
>Dear John:
>Did you try locking the drive?

Actually, I hadn't tried this. I just noticed a 'Lock Disk' option on the
popup menu,
so selected that and will see how it goes. If this works, I'd like to know how 
it
can be done automatically - I'm not a great fan of clicking on icons.

> If you did, have you tried the hacked CDrom.dmd
>that is available for cd changers?  Look for it on tim web page for new users
>at os2 super site.  The PMSHELL.EXE has bugs and is the source of the
problem,
>I believe.

This is a 3.5 in MO disk. I don't think it would use OS2CDROM.DMD, AFAIK.

>John Poltorak wrote:
>
>> I have an IBM 128MB MO disk drive and find that it ejects the disk randomly
>> for no apparent reason.
>>
>> Can anyone suggest a cause for this?
>>
>> It is installed on an IBM PC Server 320 running WSeB.
>>
>> --
>> John
>

--
John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        14-Dec-99 14:37:06
  To: All                                               14-Dec-99 14:35:14
Subj: ExaByte 8200 & tar

From: jpolt@bradnet.legend.co.uk (John Poltorak)

Has anyone managed to use tar (part of GTAK258) with an ExaByte 8200
tape drive?

--
John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: nospam@nospam.com                                 14-Dec-99 09:23:13
  To: All                                               14-Dec-99 14:35:14
Subj: What did LVM do to my HPFS partition?

From: No Spam <nospam@nospam.com>

I guess my basic question is, Can I get my HPFS partition back?

I have a single hard disk, partitioned as follows:

P1: Primary, Boot Manager
P2: Primary, OS/2 Warp v4, HPFS
P3: Primary, Warp Server for eBusiness, HPFS
P4: Logical
     L1: FAT16
     L2: FAT32
     L3: HPFS

When I boot OS/2 Warp, using FAT32.IFS and PARTFLT.FLT, my boot drive
(P2) would be C:, my FAT16 drive (L1) would be D:, my FAT32 drive (L2)
would be E:, and my HPFS drive (L3) would be F:.  Everything was as it
should be.

I then installed a copy of WSEB in it's own primary partition.  When
booted (after installing FAT32.IFS w/o PARTFLT.FLT), I would get my boot
drive (P3) as drive C:, my FAT16 drive (L1) as drive D:, and that's it.
No drive letters were allocated for the FAT32 or the HPFS drives.  I was
told that, to get the FAT32.IFS to recognize a partition, I needed to
use the Logical Volume Manager to create a compatibility volume.  So I
ran LVM, and from the menu selected Volume -> Create Volume -> Create
Non-bootable Volume -> Create Compatibility Volume.  That brought up a
dialogue box, which allowed me to select the FAT32 partition, and which
drive letter to assign to it.  After a reboot, Bingo!, there was my
FAT32 partition as drive E:.  That was half the battle, but it still was
not recognizing my HPFS partition, so...

I went back into LVM and selected Volume -> Create Volume -> Create
Non-bootable Volume -> Create LVM Volume.  When the dialogue box came
up, I selected my HPFS partition, and which drive letter to use.  After
rebooting, my HPFS partition shows up as drive F:, but shows as
UNFORMATTED, and thus inaccessible to OS/2 Warp or WSEB.

What did LVM do to it, and can it be undone?

Any help is appreciated.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: nospam@nospam.com                                 14-Dec-99 09:24:07
  To: All                                               14-Dec-99 14:35:14
Subj: What did LVM do to my HPFS partition?

From: No Spam <nospam@nospam.com>

I guess my basic question is, Can I get my HPFS partition back?

I have a single hard disk, partitioned as follows:

P1: Primary, Boot Manager
P2: Primary, OS/2 Warp v4, HPFS
P3: Primary, Warp Server for eBusiness, HPFS
P4: Logical
     L1: FAT16
     L2: FAT32
     L3: HPFS

When I boot OS/2 Warp, using FAT32.IFS and PARTFLT.FLT, my boot drive
(P2) would be C:, my FAT16 drive (L1) would be D:, my FAT32 drive (L2)
would be E:, and my HPFS drive (L3) would be F:.  Everything was as it
should be.

I then installed a copy of WSEB in it's own primary partition.  When
booted (after installing FAT32.IFS w/o PARTFLT.FLT), I would get my boot
drive (P3) as drive C:, my FAT16 drive (L1) as drive D:, and that's it.
No drive letters were allocated for the FAT32 or the HPFS drives.  I was
told that, to get the FAT32.IFS to recognize a partition, I needed to
use the Logical Volume Manager to create a compatibility volume.  So I
ran LVM, and from the menu selected Volume -> Create Volume -> Create
Non-bootable Volume -> Create Compatibility Volume.  That brought up a
dialogue box, which allowed me to select the FAT32 partition, and which
drive letter to assign to it.  After a reboot, Bingo!, there was my
FAT32 partition as drive E:.  That was half the battle, but it still was
not recognizing my HPFS partition, so...

I went back into LVM and selected Volume -> Create Volume -> Create
Non-bootable Volume -> Create LVM Volume.  When the dialogue box came
up, I selected my HPFS partition, and which drive letter to use.  After
rebooting, my HPFS partition shows up as drive F:, but shows as
UNFORMATTED, and thus inaccessible to OS/2 Warp or WSEB.

What did LVM do to it, and can it be undone?

Any help is appreciated.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: donnelly@tampabay.rr.com                          14-Dec-99 14:53:25
  To: All                                               14-Dec-99 14:35:14
Subj: Re: What did LVM do to my HPFS partition?

From: donnelly@tampabay.rr.com (Buddy Donnelly)

On Tue, 14 Dec 1999 14:23:26, No Spam <nospam@nospam.com> wrote:

> I guess my basic question is, Can I get my HPFS partition back?
> 
> I have a single hard disk, partitioned as follows:
> 
> P1: Primary, Boot Manager
> P2: Primary, OS/2 Warp v4, HPFS
> P3: Primary, Warp Server for eBusiness, HPFS
> P4: Logical
>      L1: FAT16
>      L2: FAT32
>      L3: HPFS
> 
> When I boot OS/2 Warp, using FAT32.IFS and PARTFLT.FLT, my boot drive
> (P2) would be C:, my FAT16 drive (L1) would be D:, my FAT32 drive (L2)
> would be E:, and my HPFS drive (L3) would be F:.  Everything was as it
> should be.
> 
> I then installed a copy of WSEB in it's own primary partition.  When
> booted (after installing FAT32.IFS w/o PARTFLT.FLT), I would get my boot
> drive (P3) as drive C:, my FAT16 drive (L1) as drive D:, and that's it.
> No drive letters were allocated for the FAT32 or the HPFS drives.  I was
> told that, to get the FAT32.IFS to recognize a partition, I needed to
> use the Logical Volume Manager to create a compatibility volume.  So I
> ran LVM, and from the menu selected Volume -> Create Volume -> Create
> Non-bootable Volume -> Create Compatibility Volume.  That brought up a
> dialogue box, which allowed me to select the FAT32 partition, and which
> drive letter to assign to it.  After a reboot, Bingo!, there was my
> FAT32 partition as drive E:.  That was half the battle, but it still was
> not recognizing my HPFS partition, so...
> 
> I went back into LVM and selected Volume -> Create Volume -> Create
> Non-bootable Volume -> Create LVM Volume.  When the dialogue box came
> up, I selected my HPFS partition, and which drive letter to use.  After
> rebooting, my HPFS partition shows up as drive F:, but shows as
> UNFORMATTED, and thus inaccessible to OS/2 Warp or WSEB.
> 
> What did LVM do to it, and can it be undone?
> 
> Any help is appreciated.
> 
Okay, let's start with some basics: 

1. Don't post the same article twice.
2. Sign your articles, somehow. It's more respectful of the rest of 
us. ("Psst! Hey! Over here in the shadows. I'm new in town. Where can 
a righteous dude get some good smoke?")
3. Make sure you've got all your important partition data backed up 
before trying to install a new OS. (I should say that again, for 
emphasis, but since I myself've learned it by screwing up REAL BAD I 
won't do.)
4. Be happy you got both WSeB and FAT32.IFS up in the same go. That's 
more than I would have bitten off.
5. Verify that the versions of IBM1S506.ADD everywhere on your system 
are either the same, or at least all very recent builds. This 
includes: The Warp 4 system that last ran your HPFS drive, the 
Installation diskettes you used to install, and the current HD version
in WSeB. If they're different, try copying the one from Warp 4 to your
WSeB system and reboot. That failing, copy the same one to your WSeB 
Installation diskette #1, (second disk) and adding the line SET 
COPYFROMFLOPPY=1 to the CONFIG.SYS on that diskette, then reinstall 
WSeB.
6. If your HPFS partition is on a SCSI drive, the above same holds 
true for the device driver for your SCSI card, say, AIC7870.ADD for 
many Adaptec cards.

7. Last, whatever you do, do not use LVM to "Delete" a partition. It 
really deletes it. Even though you are able to "Create" existing 
partitions into drive letters. (Obviously, if you've got a good 
backup, go ahead and delete it, because that's sometimes the fastest 
way to make drive changes.)

-- 

Good luck,

Buddy

Buddy Donnelly
donnelly@tampabay.rr.com


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: RoadRunner - TampaBay (1:109/42)

+----------------------------------------------------------------------------+

From: jkrim@ecrix.com                                   14-Dec-99 15:22:13
  To: All                                               14-Dec-99 14:35:15
Subj: FDISK corrupt trying to install WARP 4

From: jkrim@ecrix.com  (Jordan Krim)

I have the following hard disk setup according to
FDISK under WARP 3.0:

Drive Name  Partition Vtype FStype Status   Start     Size

    1 WIN 98       :    1    0c      1          0     3004
    1 005de2bf     :    1    0a      2       3004        7 <- Bootmanager
    1 WARP 3.0    C:    1    07      1       3012      258 <- HPFS
    1 006638a0    D:    2    06      0       3271     1004 <- FAT share
    1 00859920    E:    2    06      4       4275      258 <- Linux swap
    1 RH LINUX    F:    2    06      5       4534     2000
    1 00cc3240    G:    2    07      0       6534      502 <- HPFS
    1 00dbe280    H:    2    06      0       7036      902 <- FAT share
    1 00f81333    I:    2    07      0       7938      768 <- HPFS
                                             **BIOS:8032MB
    2 0000003f     :    1    00      0          0        7
    2 00003f00    J:    2    07      0          7     3004 <- Win 98 filtered

When I go to install WARP 4.0 (in partition G:), the FDISK
is corrupted to the point I get this:

Drive Name  Partition Vtype FStype Status   Start     Size

    1 0000003f     :    1    0c      0          0     3004
    1 005de2bf     :    1    0a      2       3004        7
    1 005e2180    C:    1    07      4       3012      258
    1 00663861     :    3    00      0       3271     5436
                                             **BIOS:8032MB

Nothing is formatted and BootManager is lost.  What can I do to get FDISK
for WARP 4.0 the same as FDISK for WARP 3.0 so I can proceed with installing
WARP 4.0?  I have already updated Diskette #1 with IDEDASD.EXE.  Didn't seem
to work the same as WARP 3.0.  Why?

Jordan Krim
jkrim@ecrix.com
jkrim@mho.com






















































--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: RMI.NET (1:109/42)

+----------------------------------------------------------------------------+

From: shSoPdgAeM@nctr.fda.gov                           14-Dec-99 10:03:10
  To: All                                               14-Dec-99 14:35:15
Subj: Re: Does NTFS preclude the installation of Warp 4?

From: Steve Hodge <shSoPdgAeM@nctr.fda.gov>

"William L. Hartzell" wrote:

> I had the same symptoms when I installed Win98 second edition.  I found that
> if MS large drive partition scheme was used OS/2 would crash just like you
> described.  Solution is to partition the drive using Warp 4 fixpack 9 or
> later.

>
> Steve Hodge wrote:

That's one option -- dump the NT configuration and do all partition set up
with
OS/2. I have the latest drivers (included with FixPack 12).

One thing that's helped is using Warp's FDISK /NEWMBR and getting the Boot
Manager installed.  Perhaps I can get NT to boot the OS/2 Boot Manager, then
boot Warp 4.

> > I received a Pentium III 500 MHz with a 13.3 GB WDC IDE with Windows NT
> > already installed

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: NatCenToxRes (1:109/42)

+----------------------------------------------------------------------------+

From: donnelly@tampabay.rr.com                          14-Dec-99 19:12:09
  To: All                                               14-Dec-99 16:42:03
Subj: Re: What did LVM do to my HPFS partition?

From: donnelly@tampabay.rr.com (Buddy Donnelly)

On Tue, 14 Dec 1999 17:53:35, "Buffalo Bill" <BuffaloBill@Shadow.net> 
wrote:

> 
> >3. Make sure you've got all your important partition data backed up 
> >before trying to install a new OS. (I should say that again, for 
> >emphasis, but since I myself've learned it by screwing up REAL BAD I 
> >won't do.)
> 
> (Me, too!) I do have that partition backed up, but only as recently as 1
week
> ago.  Although the world won't end if I just restore it, I wanted to know if
> it could be salvaged, since there is some new data on it that was added
after
> the backup that I'd like to have back.

Can you just boot back into Warp 4 and access it? Then do another 
Backup? Or can you see the drive contents when booted to Warp 4 
install floppies? (All of these, if true, would tend to point to 
inconsistent use of IBM1S506.ADD versions, since it would then sound 
like different geometries are being read.)


> "Create" is alittle more confusing when it comes to LVM, and the
> documentation is poor.
> 
> One thing I do see is that the drive type has been changed to 'Type 35'.  Is
> that all LVM did, and would changing it back restore accessibility to the
> drive?  What utilities are there to modify the partition table on a hard
> disk?

I wouldn't advise messing with ANYTHING that LVM needs, unless you're 
100% backed up, have all your personal bills paid, Xmas presents 
wrapped, and have run the vacuum cleaner. You're correct that it is 
badly documented, but it is capable of making a real mess of things. 
For instance, if you link separate drives into one LVM partition, you 
can't unlink them. You have to get everything saved off, then delete 
the partition, then start all over again. Pretty damned stupid, if 
this is intended for a Server.

The latest update for System Commander Deluxe contains a new utility 
that appears to allow manual editing of the "Type xx" entries, but I 
haven't been bold enough to test it.


> 
> Thanks very much for your help.  I always read your posts to this group and
> others.

(God, don't hold all those against me. I have been known to Drink And 
Post.)


-- 

Good luck,

Buddy

Buddy Donnelly
donnelly@tampabay.rr.com


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: RoadRunner - TampaBay (1:109/42)

+----------------------------------------------------------------------------+

From: jima@eda.ds.boeing.com                            14-Dec-99 17:27:04
  To: All                                               14-Dec-99 16:42:03
Subj: PCMCIA Card for USB Zip 250 Drive

From: "James F. Adams" <jima@eda.ds.boeing.com>

Does anyone have any experiences with the PCMCIA USB to ATAPI card for
the
ZIP 250 drive.  In my setup, in recognizes the card as a hard disk and
the the card
is inserted.  It wont make it ready however.  This is Warp 4, current
drivers, fix pack


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Electronics Computing Support (1:109/42)

+----------------------------------------------------------------------------+

From: BuffaloBill@Shadow.net                            14-Dec-99 12:53:17
  To: All                                               14-Dec-99 16:42:04
Subj: Re: What did LVM do to my HPFS partition?

From: "Buffalo Bill" <BuffaloBill@Shadow.net>

On Tue, 14 Dec 1999 14:53:50 GMT, Buddy Donnelly wrote:

>On Tue, 14 Dec 1999 14:23:26, No Spam <nospam@nospam.com> wrote:
>
>> I guess my basic question is, Can I get my HPFS partition back?

[snip]

>Okay, let's start with some basics: 
>
>1. Don't post the same article twice.

Sorry; I normally read news groups with PMInews, but the setup for this app
resides on the aforementioned HPFS drive.  So I tried using Netscape
Communicator, and it choked on the first try to post (i guess it managed to
post the article before it died).  Assuming it hadn't worked, I posted again
(I know, I know, never assume...)

>2. Sign your articles, somehow. It's more respectful of the rest of 
>us. ("Psst! Hey! Over here in the shadows. I'm new in town. Where can 
>a righteous dude get some good smoke?")

Sorry; again, I was using Communicator which I'm unfamiliar with, and it used
the "No Spam" entires that I always load in the browser.  I've got PMInews up
and running again now.

>3. Make sure you've got all your important partition data backed up 
>before trying to install a new OS. (I should say that again, for 
>emphasis, but since I myself've learned it by screwing up REAL BAD I 
>won't do.)

(Me, too!) I do have that partition backed up, but only as recently as 1 week
ago.  Although the world won't end if I just restore it, I wanted to know if
it could be salvaged, since there is some new data on it that was added after
the backup that I'd like to have back.

>4. Be happy you got both WSeB and FAT32.IFS up in the same go. That's 
>more than I would have bitten off.

'Risk' is my middle name; 'Unecessary' is my first. ;-)

>5. Verify that the versions of IBM1S506.ADD everywhere on your system 
>are either the same, or at least all very recent builds. This 
>includes: The Warp 4 system that last ran your HPFS drive, the 
>Installation diskettes you used to install, and the current HD version
>in WSeB. If they're different, try copying the one from Warp 4 to your
>WSeB system and reboot. That failing, copy the same one to your WSeB 
>Installation diskette #1, (second disk) and adding the line SET 
>COPYFROMFLOPPY=1 to the CONFIG.SYS on that diskette, then reinstall 
>WSeB.

I'll give that a try...

>6. If your HPFS partition is on a SCSI drive, the above same holds 
>true for the device driver for your SCSI card, say, AIC7870.ADD for 
>many Adaptec cards.

..using this, since I'm alittle bit SCSI.

>7. Last, whatever you do, do not use LVM to "Delete" a partition. It 
>really deletes it. Even though you are able to "Create" existing 
>partitions into drive letters. (Obviously, if you've got a good 
>backup, go ahead and delete it, because that's sometimes the fastest 
>way to make drive changes.)

Delete is bad.  I'm pretty sure I don't want to delete anything today. 
"Create" is alittle more confusing when it comes to LVM, and the
documentation is poor.

One thing I do see is that the drive type has been changed to 'Type 35'.  Is
that all LVM did, and would changing it back restore accessibility to the
drive?  What utilities are there to modify the partition table on a hard
disk?

>-- 
>
>Good luck,
>
>Buddy
>
>Buddy Donnelly
>donnelly@tampabay.rr.com
>

Thanks very much for your help.  I always read your posts to this group and
others.

Bill Thompson



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: bobmcl@ibm.net                                    13-Dec-99 11:27:20
  To: All                                               14-Dec-99 19:59:12
Subj: Re: IDE ZIP drive was (No subject)

From: Bob McLellan <bobmcl@ibm.net>


Lorne Sunley wrote:

> On Sat, 11 Dec 1999 02:28:09, rgibson@ix.netcom.com (Ron Gibson)
> wrote:
>
> > On Sat, 11 Dec 1999 01:00:54, lsunley@mb.sympatico.ca (Lorne Sunley)
> > wrote:
> >
> > > > How about configuring it? What swiches are required on IBM's IDE
driver.
> >
> > > The IDE ZIP drive requires that you have the latest update
> > > for the IDE device drivers installed and that you are using
> > > Fixpack 6 for Warp 4 or later to obtain the removable device
> > > support.
> >
> > Hmmm...I'm using W3 FP 40 and the DANIS IDE driver. Any problems there?
>
> I should have mentioned that for Warp 3 FP 35 or greater
> is required. You should be OK with 40. DANIS506.ADD
> works fine AFAIK.
>
> >
> > > Device drivers have been moved to their own fixpack
> > > series so if you install FP 12 you should also install
> > > the DD01 fixpack.
> > >
> > > You can obtain these through RSU updates or through
> > > the FTP site ftp://ftp.software.ibm.com/ps/products/os2/
> > >
> > > With the IDE ZIP you just connect it to the IDE cable
> > > (checking for Slave or Master of course) and if you
> > > have the device support installed it comes up automatically.
> > >
> > > The base device driver that is required (besides IBM1S506.add)
> > > is IBMATAPI.FLT
> >
> > > Partition the cartridge and format for FAT or HPFS.
> >
> > So then is it seen as a HDD, IOW appears in FDISK?
>
> FDISK finds it and treats it as a hard drive. That's why
> you can partition it. IIRC when you first use a cartridge
> irt will appear to have some kind of partition. Use
> FDISK to delete what's there and then allocate the
> partition. You can have more than one partition on
> the cartridge if you want. There is some obscure
> command line parameters for the driver that allow
> you to reserve drive letters for multi-partition cartridges
> but I can't remember what they are....
>
> --
>
> Lorne Sunley

 The extra switches are documented in readme.rms which is in the fixpack.
------------------------------------------------------
Bob McLellan
The Little Blue Kiwi
OS/2 Solutions for New Zeland


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: crh@physics.purdue.edu                            14-Dec-99 22:42:05
  To: All                                               14-Dec-99 19:59:13
Subj: Re: ExaByte 8200 & tar

From: crh@physics.purdue.edu (Charles Hunter)

jpolt@bradnet.legend.co.uk (John Poltorak) writes:

>Has anyone managed to use tar (part of GTAK258) with an ExaByte 8200
>tape drive?

I've used it fine for a long time on a 8100. I was even able to use
the "recommended" driver, which from my ( probably bad) memory was the ASPI
driver?

I couldn't ever use compression on it though. The archives would be corrupted
when I'd try to restore.


Charles

--
Charles R. Hunter                                        
Computer Systems Engineer        Physics Computer Network
Purdue University                crh@physics.purdue.edu

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Purdue University (1:109/42)

+----------------------------------------------------------------------------+

From: retsiemynnaht@spammoc.beoohaygon...               14-Dec-99 16:40:29
  To: All                                               14-Dec-99 19:59:13
Subj: Re: FDISK corrupt trying to install WARP 4

Message sender: retsiemynnaht@spammoc.beoohaygone.net

From: "Mike Ruskai" <retsiemynnaht@spammoc.beoohaygone.net>

On Tue, 14 Dec 1999 15:22:27 GMT, Jordan Krim wrote:

>I have the following hard disk setup according to
>FDISK under WARP 3.0:
[snip]

Put a /V switch next to IBM1S506.ADD on the boot disks for Warp 3 and Warp
4.

Try to catch the information (locate and use pause.sys, if you can), and
write it down.

It might show whether they're seeing the drive in two different fashions,
which will be a start towards a resolution.


--
 - Mike

Remove 'spambegone.net' and reverse to send e-mail.


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: TLF (1:109/42)

+----------------------------------------------------------------------------+

From: BuffaloBill@Shadow.net                            14-Dec-99 18:46:02
  To: All                                               14-Dec-99 21:14:07
Subj: Re: What did LVM do to my HPFS partition?

From: "Buffalo Bill" <BuffaloBill@Shadow.net>

On Tue, 14 Dec 1999 19:12:19 GMT, Buddy Donnelly wrote:

>Can you just boot back into Warp 4 and access it? Then do another 
>Backup? Or can you see the drive contents when booted to Warp 4 
>install floppies? (All of these, if true, would tend to point to 
>inconsistent use of IBM1S506.ADD versions, since it would then sound 
>like different geometries are being read.)

Nope; I have the same problem booting from the HD that I have booting from
the floppies - no joy.  Either way, the drive the drive can't be accessed. 
Under Warp v4, it doesn't even get assigned a drive letter.  Under WSEB, it
has the drive letter I gave it under LVM, but shows as 'Unformatted'.

>I wouldn't advise messing with ANYTHING that LVM needs, unless you're 
>100% backed up, have all your personal bills paid, Xmas presents 
>wrapped, and have run the vacuum cleaner. You're correct that it is 
>badly documented, but it is capable of making a real mess of things. 
>For instance, if you link separate drives into one LVM partition, you 
>can't unlink them. You have to get everything saved off, then delete 
>the partition, then start all over again. Pretty damned stupid, if 
>this is intended for a Server.
>
>The latest update for System Commander Deluxe contains a new utility 
>that appears to allow manual editing of the "Type xx" entries, but I 
>haven't been bold enough to test it.

I think I have that program laying around somewhere.  I may just give it a
whirl, as soon as I finish vacuuming...

>
>(God, don't hold all those against me. I have been known to Drink And 
>Post.)

Where's M.A.D.P. when you need them?

Thanks again!

Bill Thompson



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: traymond@craftedsmalltalk.com                     14-Dec-99 21:12:22
  To: All                                               15-Dec-99 03:46:00
Subj: Will Warp 3 work with all IDE CD-RW drives?

From: "Terry Raymond" <traymond@craftedsmalltalk.com>

Hi

Is there a list of compatible IDE CD-RW drives for OS/2, or
will they all work?

What additional software is required?

Thanks.
--
Terry
===========================================================
Terry Raymond       Smalltalk Professional Debug Package
Crafted Smalltalk   *Breakpoints* and *Watchpoints* for
19 Tilley Ave.                  VW and ENVY/Developer
Newport, RI  02840
(401) 846-6573      traymond@craftedsmalltalk.com
http://www.craftedsmalltalk.com
===========================================================




--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: IDT (Best News In The World) (1:109/42)

+----------------------------------------------------------------------------+

From: kmwhite1@magma.ca                                 15-Dec-99 04:10:25
  To: All                                               15-Dec-99 03:46:01
Subj: Re: Will Warp 3 work with all IDE CD-RW drives?

From: "Kyle M. White" <kmwhite1@magma.ca>

Hi Terry,

    If you go IDE (which I did, inadvertently [long story])
you're going to have to use the RSJ software, which,
while it works very well, is a tad expensive.

Check out RSJ's home page at:

    http://www.rsj.de

They've got a pretty extensive list of both SCSI and IDE
CD-WR drives supported.

    It would appear that there is freeware/shareware available
to support SCSI drives.

--
TTFN

Kyle

As you type through the keyboard of life,
always keep one finger on the ESC key.


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Magma Communications Ltd. (1:109/42)

+----------------------------------------------------------------------------+

From: rjlapham@infinet.com                              14-Dec-99 23:28:18
  To: All                                               15-Dec-99 03:46:01
Subj: Re: Adding IDE CDROM - will drive letters change?

From: rjlapham@infinet.com (Jerry Lapham)

In <qpkdVVNoMoTk-pn2-GTLRTwByqMZX@tcpserver>, on 12/14/99 
   at 02:00 AM, lsunley@mb.sympatico.ca (Lorne Sunley) said:

> The CD-ROM drive letter is always assigned AFTER
> all the drive letters for HD and removable disks
> (like ZIP or JAZ or ORB etc)

Presumably you're thinking of IDE or ATAPI removables.  My parallel port
Zip 100 comes after my CD-ROM.

    -Jerry
-- 
============================================================
Jerry Lapham, Monroe, OH
E-Mail: rjlapham@infinet.com
Written Tuesday, December 14, 1999 - 11:28 PM (EST)
============================================================
MR/2 Ice tag:  WARNING:  Check your toilet paper stockpile.  Make sure it's
Y2K compliant. Word has it, if it isn't, come Jan 1, 2000, it will roll back
to 1900, then turn into a Sears Catalog.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Voyager.Net - East Lansing, MI (1:109/42)

+----------------------------------------------------------------------------+

From: jdparker@erols.com                                15-Dec-99 00:02:23
  To: All                                               15-Dec-99 03:46:01
Subj: Re: Does NTFS preclude the installation of Warp 4?

From: Jim Parker <jdparker@erols.com>

Steve Hodge wrote:

> "William L. Hartzell" wrote:
>
> > I had the same symptoms when I installed Win98 second edition.  I found
that
> > if MS large drive partition scheme was used OS/2 would crash just like you
> > described.  Solution is to partition the drive using Warp 4 fixpack 9 or
> > later.
>
> >
> > Steve Hodge wrote:
>
> That's one option -- dump the NT configuration and do all partition set up
with
> OS/2. I have the latest drivers (included with FixPack 12).
>
> One thing that's helped is using Warp's FDISK /NEWMBR and getting the Boot
> Manager installed.  Perhaps I can get NT to boot the OS/2 Boot Manager, then
> boot Warp 4.
>
> > > I received a Pentium III 500 MHz with a 13.3 GB WDC IDE with Windows NT
> > > already installed

Becareful. The latest drivers are not included with Fix Pack 12. Since Fix
Pack 10
(or there abouts), drivers are packaged separately.

Jim


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: jrop@verso.st.jyu.fi                              15-Dec-99 09:34:07
  To: All                                               15-Dec-99 10:26:21
Subj: Installing NT with OS/2

From: Janne Ropponen <jrop@verso.st.jyu.fi>

Hello,

I currently have Warp 4 (FP12), DOS and BeOS installed on two disks
with the following configuration (the drive letters refer to how
OS/2 sees them):

Primary Master (6.5 GB):
 -   boot manager
 -c: 1 GB FAT (DOS boot)
 -d: 2 GB FAT
 -   2 GB BeOS
 -e: 1.5 GB HPFS (OS/2 boot)
Secondary Master (9 GB):
 -f: 9 GB HPFS (data)
Primary Slave (ZIP-100) g:
Secondary Slave (CD-ROM) h:
SCSI: (CD-R/W) i:

I bought a new 20 GB disk and I'd like to replace the 6.5 GB one with
the 9 GB and use the new 20 GB disk to replace the former 9 GB one.
I also have to install NT 4.0 on the 9 GB disk.

Ok. I am going to do the following: 
 1) Copy all the data on the 9 GB disk to the 20 GB disk
 2) Repartition the 9 GB disk so that everything else is like on the
    old 6.5 GB disk, but a new 2.5 GB partition for NT is between
    the BeOS and 1.5 GB HPFS partition
 3) Copy all the data from the 6.5 GB disk to the right
    partitions on the 20 GB disk (xcopying OS/2 from one drive 
    to another is a thing I've done many times before, has 
    worked every time)
 4) Install BeOS again
 5) Install NT
 6) Configure the Boot Manager to boot to DOS/BeOS/NT and OS/2.
 7) Run my system happily everafter?

Will this work? I require that the drive letters OS/2 sees won't change 
(I DON'T want to install the whole thing and all my programs, etc. again,
and I have found my drive lettering to work perfectly for me). I don't
need (or even want) OS/2 to see the NTFS partitions, but NT should
see the HPFS partitions, and BeOS should also see the NTFS partition.
(I don't know if there's a driver for it yet, but at least in the
future it might be important)

What I see as potential problems are:
 a) The OS/2 boot partition on the 9.1 GB disk will (partly) go 
    over the 1024 cylinder "limit". Is this a problem anymore?
 b) NT might not like to install after everything else (although
    that would be very stupid, as every other OS will install where
    I want it to and when I want it to.

Is there anything special I should take into consideration? If the 
1024 cylinder limit still exists, I am perfectly happy to let the
extra space over the 1024 cylinders go unpartitioned - I just shrink
the other partitions a bit.
 
Thanks for any help.


 - Janne (jrop@st.jyu.fi)

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: University of Jyvaskyla, Finland (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 11:19:03
  To: All                                               15-Dec-99 10:26:22
Subj: Re: Does NTFS preclude the installation of Warp 4?

From: "William L. Hartzell" <wlhartzell@home.com>

Dear Steve:
I'm predicating my statements upon the assumption that NT is behaving like
Win98.
Microsoft's installer looks into the partition table to find the types of
partitions available.  If it finds a partition labeled as Boot Manager or
OS/2, it
will either refuse to install or install incorrectly.  This is why I say to
install
NT first, leaving freespace for them.  Likewise, if you want Win98 on the same
disk, you must install it before NT or OS/2 and Boot Manager.  It is best to
leave
the MBR as virgin or let NT write it to point to itself.  You will be using
OS/2's
fdisk.exe to later write the MBR to point to Boot Manager, overwriting
whatever NT
puts there.  You'll be then using Boot Manager to select the partition to
boot.  I
am going to further assume that you are going to copy the OS/2 partition from
another disk where it has the same drive letter (possibly over a LAN).  Else
you
will need to know that there are additional problems to be overcomed doing the 
OS/2
install from the GA CDROM.  Note that the latest drivers are not in fixpack
12, but
can be found in Device Driver Fixpack 01.  If you have a cd-changer install,
there
are even more problems that revolve around the DD 01 fixpack.  I've a
workaround
for these problems if you need them.  I've never tried Partition Magic as part 
of
my solution, so others may have a better solution for you.

Steve Hodge wrote:

> "William L. Hartzell" wrote:
>
> > I had the same symptoms when I installed Win98 second edition.  I found
that
> > if MS large drive partition scheme was used OS/2 would crash just like you
> > described.  Solution is to partition the drive using Warp 4 fixpack 9 or
> > later.
>
> >
> > Steve Hodge wrote:
>
> That's one option -- dump the NT configuration and do all partition set up
with
> OS/2. I have the latest drivers (included with FixPack 12).
>
> One thing that's helped is using Warp's FDISK /NEWMBR and getting the Boot
> Manager installed.  Perhaps I can get NT to boot the OS/2 Boot Manager, then
> boot Warp 4.
>
> > > I received a Pentium III 500 MHz with a 13.3 GB WDC IDE with Windows NT
> > > already installed

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 11:58:23
  To: All                                               15-Dec-99 10:26:22
Subj: Re: FDISK corrupt trying to install WARP 4

From: "William L. Hartzell" <wlhartzell@home.com>

Dear Jordan:
You have a larger than 8.4 GB disk, thus you must be using Warp 3.0 with
fixpack
later than 35 installed.  If you are using Warp 4.0 before fixpack 9, you do
not
have equilivant system utilies installed.  If install fixpack 12 over a GA
install, you do not have equilivant system utilites installed, as fixpacks
after
10 don't have drivers included.  You will need to install Device Driver
Fixpack
01 found the same place as Warp fixpacks.  Then the missing data will appear.
Don't do anything to the drive using the Warp 4.0 utilities until you up-dated
them.

Jordan Krim wrote:

> I have the following hard disk setup according to
> FDISK under WARP 3.0:
>
> Drive Name  Partition Vtype FStype Status   Start     Size
>
>     1 WIN 98       :    1    0c      1          0     3004
>     1 005de2bf     :    1    0a      2       3004        7 <- Bootmanager
>     1 WARP 3.0    C:    1    07      1       3012      258 <- HPFS
>     1 006638a0    D:    2    06      0       3271     1004 <- FAT share
>     1 00859920    E:    2    06      4       4275      258 <- Linux swap
>     1 RH LINUX    F:    2    06      5       4534     2000
>     1 00cc3240    G:    2    07      0       6534      502 <- HPFS
>     1 00dbe280    H:    2    06      0       7036      902 <- FAT share
>     1 00f81333    I:    2    07      0       7938      768 <- HPFS
>                                              **BIOS:8032MB
>     2 0000003f     :    1    00      0          0        7
>     2 00003f00    J:    2    07      0          7     3004 <- Win 98
filtered
>
> When I go to install WARP 4.0 (in partition G:), the FDISK
> is corrupted to the point I get this:
>
> Drive Name  Partition Vtype FStype Status   Start     Size
>
>     1 0000003f     :    1    0c      0          0     3004
>     1 005de2bf     :    1    0a      2       3004        7
>     1 005e2180    C:    1    07      4       3012      258
>     1 00663861     :    3    00      0       3271     5436
>                                              **BIOS:8032MB
>
> Nothing is formatted and BootManager is lost.  What can I do to get FDISK
> for WARP 4.0 the same as FDISK for WARP 3.0 so I can proceed with installing
> WARP 4.0?  I have already updated Diskette #1 with IDEDASD.EXE.  Didn't seem
> to work the same as WARP 3.0.  Why?
>
> Jordan Krim
> jkrim@ecrix.com
> jkrim@mho.com

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 12:00:25
  To: All                                               15-Dec-99 10:26:22
Subj: Re: PCMCIA Card for USB Zip 250 Drive

From: "William L. Hartzell" <wlhartzell@home.com>

Dear James:
Try the Dani drivers found on Hobbes.  She has said that she has them
working in the configuration that you got.

"James F. Adams" wrote:

> Does anyone have any experiences with the PCMCIA USB to ATAPI card for
> the
> ZIP 250 drive.  In my setup, in recognizes the card as a hard disk and
> the the card
> is inserted.  It wont make it ready however.  This is Warp 4, current
> drivers, fix pack

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 12:22:22
  To: All                                               15-Dec-99 10:26:22
Subj: Re: Installing NT with OS/2

From: "William L. Hartzell" <wlhartzell@home.com>

Dear Janne:
Yes, the 1024 cylinder limit still exist.  Make a data partition out of the
cylinders over 1023.  Do the partitioning with OS/2's fdisk.exe.  Install NT
before you format any partition (except NT's) or install Boot Manager.  After
installing NT use OS/2's Fdisk.exe to install Boot Manager.  Xcopy the
systems as you described.  Be sure before you start that your Warp 4.0 has
Device Driver 01 installed and that your utilities disks were made after you
install that fixpack.  Let us know how it went.  P.S.  No disk in the process
can be slave.

Janne Ropponen wrote:

> Hello,
>
> I currently have Warp 4 (FP12), DOS and BeOS installed on two disks
> with the following configuration (the drive letters refer to how
> OS/2 sees them):
>
> Primary Master (6.5 GB):
>  -   boot manager
>  -c: 1 GB FAT (DOS boot)
>  -d: 2 GB FAT
>  -   2 GB BeOS
>  -e: 1.5 GB HPFS (OS/2 boot)
> Secondary Master (9 GB):
>  -f: 9 GB HPFS (data)
> Primary Slave (ZIP-100) g:
> Secondary Slave (CD-ROM) h:
> SCSI: (CD-R/W) i:
>
> I bought a new 20 GB disk and I'd like to replace the 6.5 GB one with
> the 9 GB and use the new 20 GB disk to replace the former 9 GB one.
> I also have to install NT 4.0 on the 9 GB disk.
>
> Ok. I am going to do the following:
>  1) Copy all the data on the 9 GB disk to the 20 GB disk
>  2) Repartition the 9 GB disk so that everything else is like on the
>     old 6.5 GB disk, but a new 2.5 GB partition for NT is between
>     the BeOS and 1.5 GB HPFS partition
>  3) Copy all the data from the 6.5 GB disk to the right
>     partitions on the 20 GB disk (xcopying OS/2 from one drive
>     to another is a thing I've done many times before, has
>     worked every time)
>  4) Install BeOS again
>  5) Install NT
>  6) Configure the Boot Manager to boot to DOS/BeOS/NT and OS/2.
>  7) Run my system happily everafter?
>
> Will this work? I require that the drive letters OS/2 sees won't change
> (I DON'T want to install the whole thing and all my programs, etc. again,
> and I have found my drive lettering to work perfectly for me). I don't
> need (or even want) OS/2 to see the NTFS partitions, but NT should
> see the HPFS partitions, and BeOS should also see the NTFS partition.
> (I don't know if there's a driver for it yet, but at least in the
> future it might be important)
>
> What I see as potential problems are:
>  a) The OS/2 boot partition on the 9.1 GB disk will (partly) go
>     over the 1024 cylinder "limit". Is this a problem anymore?
>  b) NT might not like to install after everything else (although
>     that would be very stupid, as every other OS will install where
>     I want it to and when I want it to.
>
> Is there anything special I should take into consideration? If the
> 1024 cylinder limit still exists, I am perfectly happy to let the
> extra space over the 1024 cylinders go unpartitioned - I just shrink
> the other partitions a bit.
>
> Thanks for any help.
>
>  - Janne (jrop@st.jyu.fi)

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 12:44:19
  To: All                                               15-Dec-99 10:26:22
Subj: Re: Installing NT with OS/2

From: "William L. Hartzell" <wlhartzell@home.com>

Addendum:  Format NT to NTFS and OS/2 will keep the same drive letter.  Use
the
drive utilites on Leo or Hobbes if you want OS/2 to read or write to NT.
Likewise, there are drive utilites for NT that permit it to see HPFS without
changing either NT or OS/2 drive letters, resp. by placing these foriegn file
system after the one they recognize as built-in.

"William L. Hartzell" wrote:

> Dear Janne:
> Yes, the 1024 cylinder limit still exist.  Make a data partition out of the
> cylinders over 1023.  Do the partitioning with OS/2's fdisk.exe.  Install NT
> before you format any partition (except NT's) or install Boot Manager. 
After
> installing NT use OS/2's Fdisk.exe to install Boot Manager.  Xcopy the
> systems as you described.  Be sure before you start that your Warp 4.0 has
> Device Driver 01 installed and that your utilities disks were made after you
> install that fixpack.  Let us know how it went.  P.S.  No disk in the
process
> can be slave.
>
> Janne Ropponen wrote:
>
> > Hello,
> >
> > I currently have Warp 4 (FP12), DOS and BeOS installed on two disks
> > with the following configuration (the drive letters refer to how
> > OS/2 sees them):
> >
> > Primary Master (6.5 GB):
> >  -   boot manager
> >  -c: 1 GB FAT (DOS boot)
> >  -d: 2 GB FAT
> >  -   2 GB BeOS
> >  -e: 1.5 GB HPFS (OS/2 boot)
> > Secondary Master (9 GB):
> >  -f: 9 GB HPFS (data)
> > Primary Slave (ZIP-100) g:
> > Secondary Slave (CD-ROM) h:
> > SCSI: (CD-R/W) i:
> >
> > I bought a new 20 GB disk and I'd like to replace the 6.5 GB one with
> > the 9 GB and use the new 20 GB disk to replace the former 9 GB one.
> > I also have to install NT 4.0 on the 9 GB disk.
> >
> > Ok. I am going to do the following:
> >  1) Copy all the data on the 9 GB disk to the 20 GB disk
> >  2) Repartition the 9 GB disk so that everything else is like on the
> >     old 6.5 GB disk, but a new 2.5 GB partition for NT is between
> >     the BeOS and 1.5 GB HPFS partition
> >  3) Copy all the data from the 6.5 GB disk to the right
> >     partitions on the 20 GB disk (xcopying OS/2 from one drive
> >     to another is a thing I've done many times before, has
> >     worked every time)
> >  4) Install BeOS again
> >  5) Install NT
> >  6) Configure the Boot Manager to boot to DOS/BeOS/NT and OS/2.
> >  7) Run my system happily everafter?
> >
> > Will this work? I require that the drive letters OS/2 sees won't change
> > (I DON'T want to install the whole thing and all my programs, etc. again,
> > and I have found my drive lettering to work perfectly for me). I don't
> > need (or even want) OS/2 to see the NTFS partitions, but NT should
> > see the HPFS partitions, and BeOS should also see the NTFS partition.
> > (I don't know if there's a driver for it yet, but at least in the
> > future it might be important)
> >
> > What I see as potential problems are:
> >  a) The OS/2 boot partition on the 9.1 GB disk will (partly) go
> >     over the 1024 cylinder "limit". Is this a problem anymore?
> >  b) NT might not like to install after everything else (although
> >     that would be very stupid, as every other OS will install where
> >     I want it to and when I want it to.
> >
> > Is there anything special I should take into consideration? If the
> > 1024 cylinder limit still exists, I am perfectly happy to let the
> > extra space over the 1024 cylinders go unpartitioned - I just shrink
> > the other partitions a bit.
> >
> > Thanks for any help.
> >
> >  - Janne (jrop@st.jyu.fi)

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 13:07:01
  To: All                                               15-Dec-99 10:26:22
Subj: Re: Optical disk ejects randomly

From: "William L. Hartzell" <wlhartzell@home.com>

Dear John:
One additional thing to try is the Dani drivers that are on Hobbes and Leo. 
These are
better versions of IBM1S506.add and ATAPI.Add.  They may contain the fix that
you need.

John Poltorak wrote:

> In <3855C2D1.5866CA62@home.com>, "William L. Hartzell" <wlhartzell@home.com> 
writes:
> >Dear John:
> >Did you try locking the drive?
>
> Actually, I hadn't tried this. I just noticed a 'Lock Disk' option on the
popup menu,
> so selected that and will see how it goes. If this works, I'd like to know
how it
> can be done automatically - I'm not a great fan of clicking on icons.
>
> > If you did, have you tried the hacked CDrom.dmd
> >that is available for cd changers?  Look for it on tim web page for new
users
> >at os2 super site.  The PMSHELL.EXE has bugs and is the source of the
problem,
> >I believe.
>
> This is a 3.5 in MO disk. I don't think it would use OS2CDROM.DMD, AFAIK.
>
> >John Poltorak wrote:
> >
> >> I have an IBM 128MB MO disk drive and find that it ejects the disk
randomly
> >> for no apparent reason.
> >>
> >> Can anyone suggest a cause for this?
> >>
> >> It is installed on an IBM PC Server 320 running WSeB.
> >>
> >> --
> >> John
> >
>
> --
> John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: waugh@wcc.govt.nz                                 15-Dec-99 20:12:09
  To: All                                               15-Dec-99 16:48:08
Subj: Re: ExaByte 8200 & tar

From: "Kevin Waugh" <waugh@wcc.govt.nz>

I have used it on an EXB-8205 and it worked OK
I no longer have the 8205 (4mmDAT now) and cannot remember any details but I
did get it to work.

John Poltorak wrote in message <38565619.0@katana.legend.co.uk>...
>Has anyone managed to use tar (part of GTAK258) with an ExaByte 8200
>tape drive?
>
>--
>John


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Wellington City Council, New Zealand - http://www
(1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 13:16:04
  To: All                                               15-Dec-99 16:48:09
Subj: Re: Moving to a new, larger hard drive--HELP!

From: "William L. Hartzell" <wlhartzell@home.com>

Dear Jejones:
The secret is to the copy from master to master, not master to slave.  Don't
know why but something about slave makes OS/2 do weird things. Be sure that
Warp 4.0 has Device Driver Fixpack 01 installed and all utilities disks are
made after it was installed.  Also would not hurt if you install fixpack 12
for Merlin.

jejones@ibm.net wrote:

> OK...Now I'm in trouble.
>
> I used PQ Drive Copy to copy C: (primary) and D: (logical) to a new 17
> Gbyte
> hard drive from a 6.1 Gbyte hard drive, and marked C: as startable.  All
> appeared
> to go well...but when I rejumpered and reconnected--disconnecting the
> old drive
> and making the new drive master instead of slave--it wouldn't boot.
>
> I see some references to SYSINSTX.COM to make a partition bootable, but
> OTOH I've seen claims that HPFS file systems don't require that.
>
> Tonight I thought I'd try going ahead and using FDISK and XCOPY
> /H/O/T/S/E/R/V as I've seen described (but what would that do that Drive
>
> Copy didn't?).  Of course, I reset the jumpers on the new drive to make
> it the
> slave again. At first I thought I'd drop back to the "original"
> CONFIG.SYS,
> but that, I think, predates the IBM1S506 that knows about large IDE
> drives,
> so I rebooted and let it proceed.  Oops...now the new drive is
> partitioned, so
> that things on D: couldn't be found, and the system crashed in SINGLEQ$.
>
> I went back to just having the old drive connected...but now the BIOS
> doesn't
> even recognize the old drive;  I fear that I've done something to fry
> the old
> drive.  (The new drive is recognized; I tried it by itself.)
>
> Now I'm up the proverbial creek without a paddle.  Why on earth won't
> the
> new drive boot?  Any advice would be greatly appreciated.
>
>     James Jones
>
> Opinions herein are those of the author, and not necessarily those of
> any
> organization.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        15-Dec-99 13:22:19
  To: All                                               15-Dec-99 16:48:09
Subj: Re: Optical disk ejects randomly

From: jpolt@bradnet.legend.co.uk (John Poltorak)

In <38579287.B02140DC@home.com>, "William L. Hartzell" <wlhartzell@home.com>
writes:
>Dear John:
>One additional thing to try is the Dani drivers that are on Hobbes and Leo. 
These are
>better versions of IBM1S506.add and ATAPI.Add.  They may contain the fix that 
you need.

I thought they were for IDE. I'm using all SCSI...

BTW the 'Lock Disk' option which was suggested, seemed to work for a while,
but the disk has popped out by itself again.

>John Poltorak wrote:
>
>> In <3855C2D1.5866CA62@home.com>, "William L. Hartzell"
<wlhartzell@home.com> writes:
>> >Dear John:
>> >Did you try locking the drive?
>>
>> Actually, I hadn't tried this. I just noticed a 'Lock Disk' option on the
popup menu,
>> so selected that and will see how it goes. If this works, I'd like to know
how it
>> can be done automatically - I'm not a great fan of clicking on icons.
>>
>> > If you did, have you tried the hacked CDrom.dmd
>> >that is available for cd changers?  Look for it on tim web page for new
users
>> >at os2 super site.  The PMSHELL.EXE has bugs and is the source of the
problem,
>> >I believe.
>>
>> This is a 3.5 in MO disk. I don't think it would use OS2CDROM.DMD, AFAIK.
>>
>> >John Poltorak wrote:
>> >
>> >> I have an IBM 128MB MO disk drive and find that it ejects the disk
randomly
>> >> for no apparent reason.
>> >>
>> >> Can anyone suggest a cause for this?
>> >>
>> >> It is installed on an IBM PC Server 320 running WSeB.
>> >>
>> >> --
>> >> John
>> >
>>
>> --
>> John
>

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 13:38:05
  To: All                                               15-Dec-99 16:48:09
Subj: Re: OS/2 Install can't find CD-ROM drive

From: "William L. Hartzell" <wlhartzell@home.com>

Dear Gilbert:
We need to go back to basics.  You need the ABios configuration disk to set up
CMOS for IDE and to make sure that SCSI is gone.  If already done this,  then
and since you correctly state that ibmidecd.flt isn't loading, find drivers
for the CDrom.  Before going to look for drivers that might not exist and may
not be needed, try updating the install floppies with the dani drivers from
Hobbes or Leo.  DaniS506.add might solve your problem. You will have to change
the config.sys on second disk to include the new driver and add a line that
says "SET COPYFROMFLOPPY=1".  The danis506.add replaces IBM1S506.add on the
second disk.  I've never used an ABios machine.  Thus I don't know if this
will help.

Gilbert Saint-flour wrote:

> Hello:
>
> I'm trying to install OS/2 on an IBM PC 750 (PCI/MCA 6886-4CH) which has a
> 540MB Maxtor drive and a BTC 16X IDE CD-ROM.   Installation fails with a
> message stating that IBMIDECD.FLT doesn't load, apparently, because it
> failed to recognize my IDE CD-ROM drive.  The drive works fine under Win95
> on the same machine.  I tried a 2nd drive (GoldStar 32X) which works fine
> with 95 also but isn't recognized by OS/2 install either.
>
> This machine has on-board IDE; 4CH models originally came with a SCSI
> controller and hard-drive, but the SCSI stuff is no longer there and I'd
> like to set it up with IDE, at least for the time being.  The CD-ROM drive
> was initially slave on IDE0; I changed it to be master on IDE1, which
> didn't help with my problem.
>
> I tried with Warp Connect and Warp 4, using the original installation
> disks, then with the Disk 1 images from the October release of the WarpUP!
> CD, and got the same symptoms in all cases (IBMIDECD not loaded).  This is
> a 4 year-old machine with a 540MB hard-drive, I shouldn't need the latest
> IDE drivers, should I ?
>
> I added the /V switch to IBM1S506, which had no visible effect; I suspect
> IBM1S506 isn't used because this is an ABIOS machine.
>
> I could copy the CD-ROM to the hard-disk and run the install from there,
> but I need the CD-ROM to work on OS/2, so I feel I have to resolve this
> problem one way or another.
>
> Any idea anyone?
>
> Thanks for your help.
>
>  Gilbert Saint-flour

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: jkrim@ecrix.com                                   15-Dec-99 15:42:01
  To: All                                               15-Dec-99 16:48:09
Subj: Re: FDISK corrupt trying to install WARP 4

From: jkrim@ecrix.com  (Jordan Krim)

In <38578286.943AD4D3@home.com>, "William L. Hartzell" <wlhartzell@home.com>
writes:
>Dear Jordan:
>You have a larger than 8.4 GB disk, thus you must be using Warp 3.0 with
fixpack
>later than 35 installed.  If you are using Warp 4.0 before fixpack 9, you do
not
>have equilivant system utilies installed.  If install fixpack 12 over a GA
>install, you do not have equilivant system utilites installed, as fixpacks
after
>10 don't have drivers included.  You will need to install Device Driver
Fixpack
>01 found the same place as Warp fixpacks.  Then the missing data will appear.
>Don't do anything to the drive using the Warp 4.0 utilities until you
up-dated
>them.
>
William,

Thanks for the information, however, remember that I haven't installed Warp 4, 
yet,
so I'm not sure how to apply Device Driver Fixpak 01.  This is good to know
once
I can install it.

It turns out that after cruising the Web for a short time, I stumbled on to a
file at:

http://www.os2bbs.com/file_f/fixes4x/WARP411.TXT

This file describes my problem *exactly*.   The strange part is that this fix
for Warp 4 diskettes #1 and #2 applies to Thinkpads (765/760, 380/386, 770).
I do not have a Thinkpad.  I have a Dell Pentium III.

Now in comparing my 2 diskettes which don't work and the fixed Thinkpad
diskettes,
I found the following files different:

IBM1S506.ADD
OS2DASD.DMD
IBMIDECD.FLT
DOSCALL1.DLL
PCIBUS.SNP

My diskettes contain the latest of the first 3 (IDEDASD.EXE).  The Thinkpad
ones are older by a few months.

Because I am curious as to what may have 'broken' in the new IDEDASD.EXE
relative
to my system, I plan to try to 'update' my diskettes which each file until I
discover the file(s) causing the corruption.

Jordan Krim
jkrim@ecrix.com
jkrim@mho.com

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: RMI.NET (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 16:15:06
  To: All                                               15-Dec-99 16:48:09
Subj: Re: FDISK corrupt trying to install WARP 4

From: "William L. Hartzell" <wlhartzell@home.com>

The drives in Warp 3.0 fixpack 40 are basicly the same ones as in Warp 4.0
device
drivers fixpack 01.  Copy them from Warp 3.0 to the Warp 4.0 install disks
over the
device drivers of the exact same name.  Edit the config.sys file on the second 
disk to
include "SET COPYFROMFLOPPY=1".  If you are doing a single disk install of
Warp 4.0, you
will have more problems.  Please consider get a loaner from a friend of a
drive less
than 4 GB.  Do an install of Warp 4.0 on it.  Xcopy the system from there to
your drive,
after you have installed the fixpacks.  Make the utilities disks from the
updated
system.  If this is not possible, I do have a workaround that is a pain to do. 
 I am
willing to give it to you.  Let me know.  The important files are IBM1S506.add 
and
IDECDROM.FLT.  There are others that are fixpack dependent, like fdisk.exe.

Jordan Krim wrote:

> In <38578286.943AD4D3@home.com>, "William L. Hartzell" <wlhartzell@home.com> 
writes:
> >Dear Jordan:
> >You have a larger than 8.4 GB disk, thus you must be using Warp 3.0 with
fixpack
> >later than 35 installed.  If you are using Warp 4.0 before fixpack 9, you
do not
> >have equilivant system utilies installed.  If install fixpack 12 over a GA
> >install, you do not have equilivant system utilites installed, as fixpacks
after
> >10 don't have drivers included.  You will need to install Device Driver
Fixpack
> >01 found the same place as Warp fixpacks.  Then the missing data will
appear.
> >Don't do anything to the drive using the Warp 4.0 utilities until you
up-dated
> >them.
> >
> William,
>
> Thanks for the information, however, remember that I haven't installed Warp
4, yet,
> so I'm not sure how to apply Device Driver Fixpak 01.  This is good to know
once
> I can install it.
>
> It turns out that after cruising the Web for a short time, I stumbled on to
a
> file at:
>
> http://www.os2bbs.com/file_f/fixes4x/WARP411.TXT
>
> This file describes my problem *exactly*.   The strange part is that this
fix
> for Warp 4 diskettes #1 and #2 applies to Thinkpads (765/760, 380/386, 770).
> I do not have a Thinkpad.  I have a Dell Pentium III.
>
> Now in comparing my 2 diskettes which don't work and the fixed Thinkpad
diskettes,
> I found the following files different:
>
> IBM1S506.ADD
> OS2DASD.DMD
> IBMIDECD.FLT
> DOSCALL1.DLL
> PCIBUS.SNP
>
> My diskettes contain the latest of the first 3 (IDEDASD.EXE).  The Thinkpad
> ones are older by a few months.
>
> Because I am curious as to what may have 'broken' in the new IDEDASD.EXE
relative
> to my system, I plan to try to 'update' my diskettes which each file until I
> discover the file(s) causing the corruption.
>
> Jordan Krim
> jkrim@ecrix.com
> jkrim@mho.com

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 16:39:02
  To: All                                               15-Dec-99 16:48:09
Subj: Re: Optical disk ejects randomly

From: "William L. Hartzell" <wlhartzell@home.com>

Dear John:
At the Transport command level IDE and SCSI are the same.  The DaniS506.add as 
well as the
IBM1S506.ADD handles SCSI drives.  The pop out problem is caused by the
PMShell calling for
status on the drive everytime you do somethimg with any drive.  I think there
was a switch
mentioned with Warp 3.0 fixpack 36 readme that is applicable to this problem.  
This switch
was added to 'add' device driver to force it to recognize removable media.  It 
is still
present to both drivers I mentioned above.  Get the Dani driver and read the
readme for it.
Let me know what happens.

John Poltorak wrote:

> In <38579287.B02140DC@home.com>, "William L. Hartzell" <wlhartzell@home.com> 
writes:
> >Dear John:
> >One additional thing to try is the Dani drivers that are on Hobbes and Leo. 
 These are
> >better versions of IBM1S506.add and ATAPI.Add.  They may contain the fix
that you need.
>
> I thought they were for IDE. I'm using all SCSI...
>
> BTW the 'Lock Disk' option which was suggested, seemed to work for a while,
> but the disk has popped out by itself again.
>
> >John Poltorak wrote:
> >
> >> In <3855C2D1.5866CA62@home.com>, "William L. Hartzell"
<wlhartzell@home.com> writes:
> >> >Dear John:
> >> >Did you try locking the drive?
> >>
> >> Actually, I hadn't tried this. I just noticed a 'Lock Disk' option on the 
popup menu,
> >> so selected that and will see how it goes. If this works, I'd like to
know how it
> >> can be done automatically - I'm not a great fan of clicking on icons.
> >>
> >> > If you did, have you tried the hacked CDrom.dmd
> >> >that is available for cd changers?  Look for it on tim web page for new
users
> >> >at os2 super site.  The PMSHELL.EXE has bugs and is the source of the
problem,
> >> >I believe.
> >>
> >> This is a 3.5 in MO disk. I don't think it would use OS2CDROM.DMD, AFAIK.
> >>
> >> >John Poltorak wrote:
> >> >
> >> >> I have an IBM 128MB MO disk drive and find that it ejects the disk
randomly
> >> >> for no apparent reason.
> >> >>
> >> >> Can anyone suggest a cause for this?
> >> >>
> >> >> It is installed on an IBM PC Server 320 running WSeB.
> >> >>
> >> >> --
> >> >> John
> >> >
> >>
> >> --
> >> John
> >

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: jkrim@ecrix.com                                   15-Dec-99 16:57:06
  To: All                                               15-Dec-99 16:48:09
Subj: Re: FDISK corrupt trying to install WARP 4

From: jkrim@ecrix.com  (Jordan Krim)

"William L. Hartzell" <wlhartzell@home.com> writes:
>The drives in Warp 3.0 fixpack 40 are basicly the same ones as in Warp 4.0
device
>drivers fixpack 01.  Copy them from Warp 3.0 to the Warp 4.0 install disks
over the
>device drivers of the exact same name.  Edit the config.sys file on the
second disk to
>include "SET COPYFROMFLOPPY=1".  If you are doing a single disk install of
Warp 4.0, you
>will have more problems.  Please consider get a loaner from a friend of a
drive less
>than 4 GB.  Do an install of Warp 4.0 on it.  Xcopy the system from there to
your drive,
>after you have installed the fixpacks.  Make the utilities disks from the
updated
>system.  If this is not possible, I do have a workaround that is a pain to
do.  I am
>willing to give it to you.  Let me know.  The important files are
IBM1S506.add and
>IDECDROM.FLT.  There are others that are fixpack dependent, like fdisk.exe.
>
William,
I would be grateful if you can send me the instructions for the workaround,
since at this point I want to do an install from the CD as shipped with Warp
4,
and then I will apply Fixpak 12 and the Device Driver Fixpak 01 as you
mentioned
before.

BTW, I found replacing *only* the IBM1S506.ADD on diskette #1 fixes my
corruption
problem.  Unfortunately, as I stated this IBM1S506.ADD is the older one, not
the latest one from IDEDASD.EXE.

Jordan Krim
jkrim@ecrix.com
jkrim@mho.com

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: RMI.NET (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 17:03:01
  To: All                                               15-Dec-99 16:48:09
Subj: Re: FDISK corrupt trying to install WARP 4

From: "William L. Hartzell" <wlhartzell@home.com>

It will take me a few minutes to edit the file for public consumption.

Jordan Krim wrote:

> "William L. Hartzell" <wlhartzell@home.com> writes:
> >The drives in Warp 3.0 fixpack 40 are basicly the same ones as in Warp 4.0
device
> >drivers fixpack 01.  Copy them from Warp 3.0 to the Warp 4.0 install disks
over the
> >device drivers of the exact same name.  Edit the config.sys file on the
second disk to
> >include "SET COPYFROMFLOPPY=1".  If you are doing a single disk install of
Warp 4.0, you
> >will have more problems.  Please consider get a loaner from a friend of a
drive less
> >than 4 GB.  Do an install of Warp 4.0 on it.  Xcopy the system from there
to your drive,
> >after you have installed the fixpacks.  Make the utilities disks from the
updated
> >system.  If this is not possible, I do have a workaround that is a pain to
do.  I am
> >willing to give it to you.  Let me know.  The important files are
IBM1S506.add and
> >IDECDROM.FLT.  There are others that are fixpack dependent, like fdisk.exe.
> >
> William,
> I would be grateful if you can send me the instructions for the workaround,
> since at this point I want to do an install from the CD as shipped with Warp 
4,
> and then I will apply Fixpak 12 and the Device Driver Fixpak 01 as you
mentioned
> before.
>
> BTW, I found replacing *only* the IBM1S506.ADD on diskette #1 fixes my
corruption
> problem.  Unfortunately, as I stated this IBM1S506.ADD is the older one, not
> the latest one from IDEDASD.EXE.
>
> Jordan Krim
> jkrim@ecrix.com
> jkrim@mho.com

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: Trevor-Hemsley@dial.pipex.com                     16-Dec-99 00:28:19
  To: All                                               15-Dec-99 21:17:22
Subj: Re: Optical disk ejects randomly

From: "Trevor Hemsley" <Trevor-Hemsley@dial.pipex.com>

On Wed, 15 Dec 1999 23:55:34 GMT, William L. Hartzell wrote:

->Those of you who are all SCSI and no IDE, delete
->IBM1S506.add or equilvant from config.sys to see if you can boot.

You can. Are you saying that you think you can't?


Trevor Hemsley, Brighton, UK
(Trevor-Hemsley@dial.pipex.com or 75704.2477@compuserve.com)



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: UUNET WorldCom server (post doesn't reflect views
(1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               15-Dec-99 23:55:17
  To: All                                               15-Dec-99 21:17:22
Subj: Re: Optical disk ejects randomly

From: "William L. Hartzell" <wlhartzell@home.com>

Dear John:
While I was napping, not quite snoring, I remembered that there were a pair of 
programs that
came with the early modifications for removable media.  They were lock.exe and 
eject.exe.

A little story about OS/2 architecture.  OS/2 has harware independent device
drivers and
hareware dependent device drivers.  Those basedev that end with DMD are
hardware independent
device managers.  Those that end with sys or add are hardware dependent device 
drivers.  The
ones that end with FLT are in between filters.  (True until people started to
rename them.)
Dasd.dmd, Cdrom.dmd, Tape.dmd, Optical.dmd, Scsi.dmd, and Aspi.dmd should be
the order that one
can find these device independent drivers listed in their config.sys file. 
The first one is the
Block storage device driver.  It grabs all block storage devices, unless !DM
is placed for the
Chain, Device, Lun id of a device.  The Cdrom.dmd then grabs all Cdroms, Dvds, 
Changers,
Jukeboxes, and Burners that it can.  Again unless !DM is placed thereafter. 
The Tape.dmd grabs
all sequential data devices.  The Optical.dmd grabs all video disk devices. 
Finally the
Scsi.dmd grabs all remaining devices, unless !DM is included.  If any devices
are left, the
Aspi.dmd attempts to attach them.  They all attempt to attach by issuing SCSI
2 commands.
The hardware dependent drivers are loaded in the order that they appear in the 
config.sys and
are loaded before the hardware independent drivers.  These drivers are like
port drivers.  Each
knows how to handle certain ports.  The IBM1S506.add knows about addressing on 
ISA, EISA, MCA,
SCSI, IDE buses.  It does not know about co-processors.  But it does know
about IDC.  It knows
how to address the co-processor device drivers- device to device.  It sends
out a query in SCSI
2 command language to everything asking "are you a Block device driver?"  If
it gets a reply,
then it attaches that device to itself.  It then send out a query "are you a
cdrom?"  Actually
since it was split into two parts, the IBMIDECD.FLT does this and chains to
IBM1S506.add.  This
drive then ignores all other devices as it quota is met.  Tape devices have
their driver.  The
other devices have their own drivers.  SCSI adapters also have their ADD
drivers, but only
because they are co-processor driven.  Not all ports are covered under this
architecture.  These
other  port drivers don't communicate IDC like with these drivers.  That is
why parallel port
devices need their own drivers.  Dito for USB, firewire, PC Card, and other
buses/ports.  This
defect came into being because way back when OS/2 1.1 was written, these
devices did not exist,
and nobody has changed the code since.  Those of you who are all SCSI and no
IDE, delete
IBM1S506.add or equilvant from config.sys to see if you can boot.
Sorry for the Rant.

John Poltorak wrote:

> In <3857C439.3049B7FD@home.com>, "William L. Hartzell" <wlhartzell@home.com> 
writes:
> >Dear John:
> >At the Transport command level IDE and SCSI are the same.  The DaniS506.add 
as well as the
> >IBM1S506.ADD handles SCSI drives.  The pop out problem is caused by the
PMShell calling for
> >status on the drive everytime you do somethimg with any drive.  I think
there was a switch
> >mentioned with Warp 3.0 fixpack 36 readme that is applicable to this
problem.  This switch
> >was added to 'add' device driver to force it to recognize removable media.  
It is still
> >present to both drivers I mentioned above.  Get the Dani driver and read
the readme for it.
> >Let me know what happens.
>
> The Dani driver mentions nothing about SCSI drives, but I had a look through 
the
> basedev section in the cmdref to see what parameters were available...
>
> I was thinking of trying
>
> basedev=ibm2scsi.add /!dm:1
>
> where 1 is the SCSI ID of the MO drive. I also noticed that I have an
OPTICAL.DMD
> and wondered if this was being used at all. I'll add the /v switch to that
> just so I know the system recognises it properly
>
> >John Poltorak wrote:
> >
> >> In <38579287.B02140DC@home.com>, "William L. Hartzell"
<wlhartzell@home.com> writes:
> >> >Dear John:
> >> >One additional thing to try is the Dani drivers that are on Hobbes and
Leo.  These are
> >> >better versions of IBM1S506.add and ATAPI.Add.  They may contain the fix 
that you need.
> >>
> >> I thought they were for IDE. I'm using all SCSI...
> >>
> >> BTW the 'Lock Disk' option which was suggested, seemed to work for a
while,
> >> but the disk has popped out by itself again.
> >>
> >> >John Poltorak wrote:
> >> >
> >> >> In <3855C2D1.5866CA62@home.com>, "William L. Hartzell"
<wlhartzell@home.com> writes:
> >> >> >Dear John:
> >> >> >Did you try locking the drive?
> >> >>
> >> >> Actually, I hadn't tried this. I just noticed a 'Lock Disk' option on
the popup menu,
> >> >> so selected that and will see how it goes. If this works, I'd like to
know how it
> >> >> can be done automatically - I'm not a great fan of clicking on icons.
> >> >>
> >> >> > If you did, have you tried the hacked CDrom.dmd
> >> >> >that is available for cd changers?  Look for it on tim web page for
new users
> >> >> >at os2 super site.  The PMSHELL.EXE has bugs and is the source of the 
problem,
> >> >> >I believe.
> >> >>
> >> >> This is a 3.5 in MO disk. I don't think it would use OS2CDROM.DMD,
AFAIK.
> >> >>
> >> >> >John Poltorak wrote:
> >> >> >
> >> >> >> I have an IBM 128MB MO disk drive and find that it ejects the disk
randomly
> >> >> >> for no apparent reason.
> >> >> >>
> >> >> >> Can anyone suggest a cause for this?
> >> >> >>
> >> >> >> It is installed on an IBM PC Server 320 running WSeB.
> >> >> >>
> >> >> >> --
> >> >> >> John
> >> >> >
> >> >>
> >> >> --
> >> >> John
> >> >
> >

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        16-Dec-99 01:28:15
  To: All                                               16-Dec-99 00:43:21
Subj: Re: Optical disk ejects randomly

From: jpolt@bradnet.legend.co.uk (John Poltorak)

In <38582A85.CA3756F4@home.com>, "William L. Hartzell" <wlhartzell@home.com>
writes:

>and nobody has changed the code since.  Those of you who are all SCSI and no
IDE, delete
>IBM1S506.add or equilvant from config.sys to see if you can boot.

I always delete it from my SCSI systems, and have done for many years.

IBM1S506.ADD is an:-

ISA DMA Adapter Driver for ST506/IDE DASD

This is text from within the file itself.

>Sorry for the Rant.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: traymond@craftedsmalltalk.com                     15-Dec-99 21:50:20
  To: All                                               16-Dec-99 00:43:21
Subj: Re: Will Warp 3 work with all IDE CD-RW drives?

From: "Terry Raymond" <traymond@craftedsmalltalk.com>


Kyle M. White <kmwhite1@magma.ca> wrote in message
news:385714C6.4779C884@magma.ca...
> Hi Terry,
>
>     If you go IDE (which I did, inadvertently [long story])
> you're going to have to use the RSJ software, which,
> while it works very well, is a tad expensive.
>
> Check out RSJ's home page at:
>
>     http://www.rsj.de
>
> They've got a pretty extensive list of both SCSI and IDE
> CD-WR drives supported.
>
>     It would appear that there is freeware/shareware available
> to support SCSI drives.
>

Boy, at that price you can afford to get a SCSI version instead.

Thanks for the info.

--
Terry
===========================================================
Terry Raymond       Smalltalk Professional Debug Package
Crafted Smalltalk   *Breakpoints* and *Watchpoints* for
19 Tilley Ave.                  VW and ENVY/Developer
Newport, RI  02840
(401) 846-6573      traymond@craftedsmalltalk.com
http://www.craftedsmalltalk.com
===========================================================




--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: IDT (Best News In The World) (1:109/42)

+----------------------------------------------------------------------------+

From: dd@dandrake.com                                   15-Dec-99 18:29:29
  To: All                                               16-Dec-99 02:11:08
Subj: Re: ExaByte 8200 & tar

From: dd@dandrake.com (Dan Drake)

On Tue, 14 Dec 1999 22:42:10, crh@physics.purdue.edu (Charles Hunter) 
wrote:

> jpolt@bradnet.legend.co.uk (John Poltorak) writes:
> 
> >Has anyone managed to use tar (part of GTAK258) with an ExaByte 8200
> >tape drive?
> 
> I've used it fine for a long time on a 8100. I was even able to use
> the "recommended" driver, which from my ( probably bad) memory was the ASPI
> driver?
>...

Using it regularly on an 8700, and have restored from it many times 
without problem.
Here are the settings in config.sys:

Rem drivers, using Adaptec SCSI
BASEDEV=OS2SCSI.DMD
BASEDEV=AIC7870.ADD
BASEDEV=OS2ASPI.DMD

Rem GTAK
device=g:\gtak\sys\aspitape.sys tape$2 3 S2
set tape=scsi:lb,tape$2

-- 
Dan Drake
dd@dandrake.com
http://www.dandrake.com/index.html

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: csaba_r@my-deja.com                               15-Dec-99 16:54:18
  To: All                                               16-Dec-99 02:11:09
Subj: Re: Need help with HD setup

From: csaba_r@my-deja.com (Csaba Raduly)

lsunley@mb.sympatico.ca (Lorne Sunley) wrote in <qpkdVVNoMoTk-pn2
-zF5gTB6KI4LY@tcpserver>: 

>On Wed, 8 Dec 1999 16:48:50, Charles Christacopoulos 
><c.k.chrsitacopoulos_removeme@dundee.ac.uk> wrote:
>
[snip]
>
> You only get 4 partitions. The extended ones can contain
>sub-allocations (logical drives) but you are limited
>to 4 partitions (includes Boot Manager).
>

You mean 4 _primary_ partitions.

>This is a restriction invented sometime in the past
>and has been carried forward to maintain compatibility.
>
>--
>
>Lorne Sunley
>

The partition table has only 4 entries (remember, some code has to fit 
in that 512 byte sector!)

If it's not too late, change your partitions around to have the 
bootables under the 1024 cylinder limit (partition 6 is causing 
trouble). Reserve a 10 MB hole for the Linux "boot" partition.
Mount that on /boot in Linux. The rest of the Linux partition(s) need 
not be under the 1024 cylinder limit.

-- 
Csaba Raduly,    Software Developer (OS/2),    Sophos Anti-Virus
mailto:csaba.raduly@sophos.com            http://www.sophos.com/
US Support +1 888 SOPHOS 9            UK Support +44 1235 559933
Life is complex, with real and imaginary parts.

-----BEGIN GEEK CODE BLOCK----- 
Version 3.1
GCS/IT/MU d- s:- a30 C++$ UL+ P+>+++ L++ E- W+ N++ o? K? w++>$ O++$ 
M-(+) V- PS PE Y PGP- t+ 5 X++ R* tv++ b++ DI+++ D++ G- e+++ h-- r-- 
!y+
-----END GEEK CODE BLOCK----- 

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: SOPHOS Plc (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        15-Dec-99 19:10:24
  To: All                                               16-Dec-99 02:11:09
Subj: Re: Optical disk ejects randomly

From: jpolt@bradnet.legend.co.uk (John Poltorak)

In <3857C439.3049B7FD@home.com>, "William L. Hartzell" <wlhartzell@home.com>
writes:
>Dear John:
>At the Transport command level IDE and SCSI are the same.  The DaniS506.add
as well as the
>IBM1S506.ADD handles SCSI drives.  The pop out problem is caused by the
PMShell calling for
>status on the drive everytime you do somethimg with any drive.  I think there 
was a switch
>mentioned with Warp 3.0 fixpack 36 readme that is applicable to this problem. 
 This switch
>was added to 'add' device driver to force it to recognize removable media. 
It is still
>present to both drivers I mentioned above.  Get the Dani driver and read the
readme for it.
>Let me know what happens.

The Dani driver mentions nothing about SCSI drives, but I had a look through
the
basedev section in the cmdref to see what parameters were available...

I was thinking of trying 

basedev=ibm2scsi.add /!dm:1  

where 1 is the SCSI ID of the MO drive. I also noticed that I have an
OPTICAL.DMD
and wondered if this was being used at all. I'll add the /v switch to that
just so I know the system recognises it properly


>John Poltorak wrote:
>
>> In <38579287.B02140DC@home.com>, "William L. Hartzell"
<wlhartzell@home.com> writes:
>> >Dear John:
>> >One additional thing to try is the Dani drivers that are on Hobbes and
Leo.  These are
>> >better versions of IBM1S506.add and ATAPI.Add.  They may contain the fix
that you need.
>>
>> I thought they were for IDE. I'm using all SCSI...
>>
>> BTW the 'Lock Disk' option which was suggested, seemed to work for a while,
>> but the disk has popped out by itself again.
>>
>> >John Poltorak wrote:
>> >
>> >> In <3855C2D1.5866CA62@home.com>, "William L. Hartzell"
<wlhartzell@home.com> writes:
>> >> >Dear John:
>> >> >Did you try locking the drive?
>> >>
>> >> Actually, I hadn't tried this. I just noticed a 'Lock Disk' option on
the popup menu,
>> >> so selected that and will see how it goes. If this works, I'd like to
know how it
>> >> can be done automatically - I'm not a great fan of clicking on icons.
>> >>
>> >> > If you did, have you tried the hacked CDrom.dmd
>> >> >that is available for cd changers?  Look for it on tim web page for new 
users
>> >> >at os2 super site.  The PMSHELL.EXE has bugs and is the source of the
problem,
>> >> >I believe.
>> >>
>> >> This is a 3.5 in MO disk. I don't think it would use OS2CDROM.DMD,
AFAIK.
>> >>
>> >> >John Poltorak wrote:
>> >> >
>> >> >> I have an IBM 128MB MO disk drive and find that it ejects the disk
randomly
>> >> >> for no apparent reason.
>> >> >>
>> >> >> Can anyone suggest a cause for this?
>> >> >>
>> >> >> It is installed on an IBM PC Server 320 running WSeB.
>> >> >>
>> >> >> --
>> >> >> John
>> >> >
>> >>
>> >> --
>> >> John
>> >
>

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: Trevor-Hemsley@dial.pipex.com                     15-Dec-99 20:35:29
  To: All                                               16-Dec-99 02:11:09
Subj: Re: Optical disk ejects randomly

From: "Trevor Hemsley" <Trevor-Hemsley@dial.pipex.com>

On Wed, 15 Dec 1999 16:39:05 GMT, William L. Hartzell wrote:

->At the Transport command level IDE and SCSI are the same.  The DaniS506.add
as well as the
->IBM1S506.ADD handles SCSI drives.

Neither driver has anything to do with SCSI.


Trevor Hemsley, Brighton, UK
(Trevor-Hemsley@dial.pipex.com or 75704.2477@compuserve.com)



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: UUNET WorldCom server (post doesn't reflect views
(1:109/42)

+----------------------------------------------------------------------------+

From: jbarring@arn.net                                  15-Dec-99 21:58:24
  To: All                                               16-Dec-99 03:34:19
Subj: Re: What did LVM do to my HPFS partition?

From: jbarring@arn.net (Jerry)

On Tue, 14 Dec 1999 19:12:19, donnelly@tampabay.rr.com (Buddy 
Donnelly) wrote:

> On Tue, 14 Dec 1999 17:53:35, "Buffalo Bill" <BuffaloBill@Shadow.net> 
> wrote:
> 
> > 
> > >3. Make sure you've got all your important partition data backed up 
> > >before trying to install a new OS. (I should say that again, for 
> > >emphasis, but since I myself've learned it by screwing up REAL BAD I 
> > >won't do.)
> > 
> 
> > "Create" is alittle more confusing when it comes to LVM, and the
> > documentation is poor.
> > 
> > One thing I do see is that the drive type has been changed to 'Type 35'. 
Is
> > that all LVM did, and would changing it back restore accessibility to the
> > drive?  What utilities are there to modify the partition table on a hard
> > disk?
> 
I think I went through something like this when installing.  Your 
first statement included Create Compatibility Volume.  This was 
correct.  Your second statement included Create LVM Volume.  This 
seems to create a new and unformatted volume at the location 
specified.  It now needs formatted HPFS to be used.  You probably lost
the data in it.

Hope this helps.
Jerry

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: wlhartzell@home.com                               16-Dec-99 07:54:18
  To: All                                               16-Dec-99 04:48:29
Subj: Re: Optical disk ejects randomly

From: "William L. Hartzell" <wlhartzell@home.com>

To Everyone:
I apologies for my rant.  It is often that having the documentation and no
hardware to test
one's concepts, leads one to sticking one's foot in it.
Aside note:  How does the WSeB play compared to Warp 4?  I don't know if the
eject and lock
programs will even run on that advance a platform. But if they do...

John Poltorak wrote:

> In <38582A85.CA3756F4@home.com>, "William L. Hartzell" <wlhartzell@home.com> 
writes:
>
> >and nobody has changed the code since.  Those of you who are all SCSI and
no IDE, delete
> >IBM1S506.add or equilvant from config.sys to see if you can boot.
>
> I always delete it from my SCSI systems, and have done for many years.
>
> IBM1S506.ADD is an:-
>
> ISA DMA Adapter Driver for ST506/IDE DASD
>
> This is text from within the file itself.
>
> >Sorry for the Rant.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: @Home Network (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        16-Dec-99 14:10:05
  To: All                                               16-Dec-99 10:57:20
Subj: Re: MO Disk & HPFS

From: jpolt@bradnet.legend.co.uk (John Poltorak)

In <noynvevozarg.fmt8rm0.pminews@news-s01.ny.us.ibm.net>, "Alex Blair"
<aablair@ibm.net> writes:
>I am trying again to get HPFS support for a Fujitsu Dynamo 640 SE drive with
>the n512dasd.flt file as suggested by others. All is well when using the
>Fujitsu driver (modisk.sys) except that it supports only FAT drives.
>
>I have tried this on 2 systems but cannot get either to function properly.
>The last attempts on both systems show that a removable device is virtualized
>at boot time. However, the device is recognized as an ATAPI CD ROM drive, not
>an MO drive (or is the n512dasd.flt virtualizing the CDROM drive a second
>time?). What might I be doing wrong?
>
>Here are the pertinent config.sys lines from the home office system in
>(relative) order of appearance in the config.sys file :
>
>REM ** Optical Drive **
>rem BASEDEV=OS2ASPI.DMD /SHARE
>BASEDEV=OS2ASPI.DMD /ALL
>
>REM ** For HPFS support on Optical Drives **
>BASEDEV=N512DASD.FLT /v
>
>REM /rf Switch for Removeable Media
>REM BASEDEV=OS2DASD.DMD /rf
>
>REM /of Switch for Optical Media
>BASEDEV=OS2DASD.DMD /of /rf
>REM ** I have tried also the /of swith alone **

Where did you see these switches for OS2DASD.DMD documented?

According to my command reference (WSeB):-

 'This device driver has no parameters'

>REM ** SCSI Card **
>BASEDEV=SIGSCSI.ADD
>BASEDEV=OS2SCSI.DMD
>
>REM ** Fujitsu 3.5" SCSI MO Disk Device Driver (ver 2.1 US) **
>rem DEVICE=\OS2\MODISK.SYS /R1
>
>Any help is greatly appreciated.
>
>Alex Blair
>ablair@ibm.net
>
>
>

There is another basedev - OPTICAL.DMD. See if that offers you anything...

Also, I've had some 128MB disks for many years and some of those used
HPOFS.IFS - HPFS for optical disks. This is no longer supported, but in
desperation might be worth trying. Not sure where you would find it, though...

--
John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: Peter.Druck@tp2.ruhr-uni-bochum.de                16-Dec-99 16:29:18
  To: All                                               16-Dec-99 10:57:20
Subj: Bootmanager and 9GB SCSI-Disk

From: Peter Druck <Peter.Druck@tp2.ruhr-uni-bochum.de>

I'm trying to install the Bootmanager (Warp 4) on an 9GB 
SCSI-U2W HD. FDISK only shows 8 GB, the remaining 800 MB 
are unusable.
I was told that it is a problem with an outdated device 
driver. So I copied the new aic78u2.add to install-disk #1. 
Now it does not boot at all from floppy.
Is there any way to get the bootmanager running (and use 
all the disk)?

Peter

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Institut fuer Theoretische Physik II, Ruhr Uni Bo
(1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        16-Dec-99 14:21:20
  To: All                                               16-Dec-99 10:57:20
Subj: Re: Optical disk ejects randomly

From: jpolt@bradnet.legend.co.uk (John Poltorak)

In <38589ACB.AD597E89@home.com>, "William L. Hartzell" <wlhartzell@home.com>
writes:
>To Everyone:
>I apologies for my rant.  It is often that having the documentation and no
hardware to test
>one's concepts, leads one to sticking one's foot in it.
>Aside note:  How does the WSeB play compared to Warp 4? 

>I don't know if the eject and lock
>programs will even run on that advance a platform. But if they do...

There is an eject but no lock. There is no help for eject. 

eject h:

makes the light flash on the drive, but a 'drive is not ready' msg comes up.
although I can read the drive without problems (until it decides to call it a
day).

--
John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

From: svetter@ameritech.net                             16-Dec-99 09:44:06
  To: All                                               16-Dec-99 10:57:20
Subj: Re: Formatting a 100 mb zip drive to HPFS format

From: Scott Vetter <svetter@ameritech.net>

Nick:

    After trying to partition it I tend to agree with you since FDISK won't
touch
it.  It is unfortunate that I can't.

Scott

Nick Saxon wrote:

> On Fri, 10 Dec 1999 13:18:42 -0500, Scott Vetter wrote:
>
> >Richard:
> >
> >    Thank you for the info.   I'll give it a try.
> >
> >Scott
> >
> >-----------------------
> >
> >Richard Johnston wrote:
> >
> >> Scott Vetter <svetter@ameritech.net> wrote:
> >> >    I have OS/2 V4 with an IOMEGA 100 Mb zip drive attached via a
> >> > parallel port.  Is there a way to format a disk with the HPFS format?
> >>
> >> You have to use fdisk (os2) first. create a partiton on the zip disk,
save
> >> it, then you can use the command "format x: /fs:hpfs" Works like a charm
> >>
> >> dj
> >
>
> I don't believe it's possible with parallel port. IBM's IDEDASD.EXE support
> for
> Removable Media states clearly that it's possible if and only if the device
> support
> comes in the form of .ADD driver. Probably your Iomega ZIP comes with a .sys
> driver
> for parallel port connection.
>
> Nick Saxon

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Ameritech.Net www.ameritech.net  Complaints: abus
(1:109/42)

+----------------------------------------------------------------------------+

From: pjfloyd@my-deja.com                               16-Dec-99 17:10:17
  To: All                                               16-Dec-99 16:52:16
Subj: Re: DVD-ROM and OS/2 ?

From: pjfloyd@my-deja.com

In article <HZVOMCPsGPdC-pn2-bPldzdhlHX3j@dhcp2-214.niro.de.ibm.com>,
  istephan@NOSPAM.rodgau.netsurf.de (Ingo Stephany) wrote:

> Hi,
> I'm using a "Creative Labs Encore Kit" which is containing a MPEG-card

> and a DVD-ROM drive on my machine (WARP + W95 (for gaming)).

> Warp is using the DVD-drive as CD-ROM just fine with the WARP
> included ATAPI-CDROM drivers.
> Regards
> Ingo Stephany

That should work fine with ISO9660 CDs. However you won't be
able to read UDF disks (DVD and CD-R) until either IBM releases
support (next year, costs $$$) or someone else writes a
UDF IFS.

Cheers
Paul
--
Paul Floyd
Is atrophy a shiny cup?


Sent via Deja.com http://www.deja.com/
Before you buy.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Deja.com - Before you buy. (1:109/42)

+----------------------------------------------------------------------------+

From: sjaniska@inet.hr                                  16-Dec-99 21:43:22
  To: All                                               16-Dec-99 16:52:16
Subj: Re: MO Disk & HPFS

From: "Sasa Janiska" <sjaniska@inet.hr>

On Wed, 15 Dec 1999 20:42:58 -0500 (EST), Alex Blair wrote:

>I am trying again to get HPFS support for a Fujitsu Dynamo 640 SE drive with
>the n512dasd.flt file as suggested by others. All is well when using the
>Fujitsu driver (modisk.sys) except that it supports only FAT drives.
>

Here is that what works perfectly in my setup (both FAT and HPFS).
...
BASEDEV=XDFLOPPY.FLT
BASEDEV=N512DASD.FLT /v
BASEDEV=OS2DASD.DMD /of /rf
...
BASEDEV=OS2SCSI.DMD
BASEDEV=AHA152X.ADD 
REM (I'm using Fujitsu drive connected to Adaptec 1460 PCMCIA adapter)
...
BASEDEV=PCMCIA.SYS /P
BASEDEV=SS2PCIC2.SYS

>Any help is greatly appreciated.
>
>REM ** SCSI Card **
>BASEDEV=SIGSCSI.ADD
>BASEDEV=OS2SCSI.DMD
Have you tried to change this into 
BASEDEV=OS2SCSI.DMD
BASEDEV=SIGSCSI.ADD ?

I assume you have proper OS2DASD?
SIncerely,
Sasa



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Origin Line 1 Goes Here (1:109/42)

+----------------------------------------------------------------------------+

From: wadsack@ibm.net                                   16-Dec-99 11:52:06
  To: All                                               16-Dec-99 16:52:16
Subj: Re: MO Disk & HPFS

From: "Peter Wadsack" <wadsack@ibm.net>

From the readme that came with Sam Detwiler's newDASD2,

"
------------------------------------
Parameters supported by OS2DASD.DMD
------------------------------------

/RF - "treat Removable media as a Fixed disk"
  This parameter will treat removable media as a fixed disk allowing
   it to be formatted as either FAT or HPFS and allowing removable
   disks to be partitioned.  See application notes above for a
   description of drive letter ordering.

/OF - "treat Optical disks as Fixed Disks"
   This parameter will cause all optical drives found to be treated as
   fixed disks. This will allow the media to be formatted as FAT or
   HPFS. Low level formatting of optical media is not supported at
   this time.  Media formatted previously by OPTICAL.SYS or
   OPTICAL.DMD will not be accessible (as described above in IMPORTANT
   NOTES #2). Media must be FDISK'd in order to be usable.

"

AFAIK, these are still true, despite the current 'no parameters' description.


On 16 Dec 1999 14:10:11 GMT, John Poltorak wrote:

:>  >
:>  >REM /rf Switch for Removeable Media
:>  >REM BASEDEV=OS2DASD.DMD /rf
:>  >
:>  >REM /of Switch for Optical Media
:>  >BASEDEV=OS2DASD.DMD /of /rf
:>  >REM ** I have tried also the /of swith alone **
:>  
:>  Where did you see these switches for OS2DASD.DMD documented?
:>  
:>  According to my command reference (WSeB):-
:>  
:>   'This device driver has no parameters'

Peter

*/------------------------------------------------------
Peter Wadsack <wadsack@ibm.net>
Wadsack Management; Madison WI USA
------------------------------------------------------*/


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: oliver.rick@oor.de                                15-Dec-99 21:56:24
  To: All                                               16-Dec-99 16:52:16
Subj: Re: Optical disk ejects randomly

From: oliver.rick@oor.de (Oliver Rick)

On Wed, 15 Dec 1999 John Poltorak wrote:

> I thought they were for IDE. I'm using all SCSI...

> BTW the 'Lock Disk' option which was suggested, seemed to work for a while,
> but the disk has popped out by itself again.

Do you have enabled 'Removables as fixed' in the hostadapter's setup?
Is the drive jumpered as type 00h (direct access device) or type 07h (optical
device)?
Which driver accesses the optical device (manufacturer, OPTICAL.DMD,
OS2DASD.DMD)?

   /Olli/
--
IBM OS/2 Warp Update Summary:
http://www.warpupdates.de/english/warpupdates.html

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Out of Rosenheim/2 (1:109/42)

+----------------------------------------------------------------------------+

From: lsunley@mb.sympatico.ca                           16-Dec-99 21:25:21
  To: All                                               16-Dec-99 19:47:16
Subj: Re: DVD-ROM and OS/2 ?

From: lsunley@mb.sympatico.ca (Lorne Sunley)

On Thu, 16 Dec 1999 17:10:34, pjfloyd@my-deja.com wrote:

> In article <HZVOMCPsGPdC-pn2-bPldzdhlHX3j@dhcp2-214.niro.de.ibm.com>,
>   istephan@NOSPAM.rodgau.netsurf.de (Ingo Stephany) wrote:
> 
> > Hi,
> > I'm using a "Creative Labs Encore Kit" which is containing a MPEG-card
> 
> > and a DVD-ROM drive on my machine (WARP + W95 (for gaming)).
> 
> > Warp is using the DVD-drive as CD-ROM just fine with the WARP
> > included ATAPI-CDROM drivers.
> > Regards
> > Ingo Stephany
> 
> That should work fine with ISO9660 CDs. However you won't be
> able to read UDF disks (DVD and CD-R) until either IBM releases
> support (next year, costs $$$) or someone else writes a
> UDF IFS.
> 

You will be able to read "some" DVD disks, I can on the
SONY DDS220 (?) I have, but there is no certainty if you
can or not. 

--

Lorne Sunley

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: MBnet Networking Inc. (1:109/42)

+----------------------------------------------------------------------------+

From: Trevor-Hemsley@dial.pipex.com                     16-Dec-99 21:32:27
  To: All                                               17-Dec-99 03:47:21
Subj: Re: Bootmanager and 9GB SCSI-Disk

From: "Trevor Hemsley" <Trevor-Hemsley@dial.pipex.com>

On Thu, 16 Dec 1999 16:29:36 +0100, Peter Druck wrote:

->I'm trying to install the Bootmanager (Warp 4) on an 9GB 
->SCSI-U2W HD. FDISK only shows 8 GB, the remaining 800 MB 
->are unusable.
->I was told that it is a problem with an outdated device 
->driver. So I copied the new aic78u2.add to install-disk #1. 
->Now it does not boot at all from floppy.
->Is there any way to get the bootmanager running (and use 
->all the disk)?

Does it show 8GB == 8032MB which is a BIOS limit or does it show 8GB as
8500MB which is really 9.1Gb in hard disk manufacturer terms. They count
using million million bytes where FDISK and CHKDSK count using 1024 x 1024
x 1024. The latter choice means that 9,100,000,000 bytes shows up around
about 8600MB.


Trevor Hemsley, Brighton, UK
(Trevor-Hemsley@dial.pipex.com or 75704.2477@compuserve.com)



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: UUNET WorldCom server (post doesn't reflect views
(1:109/42)

+----------------------------------------------------------------------------+

From: hunters@sapphire.indstate.edu                     17-Dec-99 03:01:01
  To: All                                               17-Dec-99 03:47:22
Subj: Re: DVD-ROM and OS/2 ?

From: hunters@sapphire.indstate.edu

In article <81pdm7$vde@c4.hrz.uni-giessen.de>,
  reimers@muffin.physik.uni-bremen.de wrote:

> I am considering to acquire a new computer and like to take a DVD-ROM
> drive instead of a CDROM. Does anybody know if there is one out there
> for OS/2 ? ATAPI or SCSI, this does not matter for me. If there were
> only SCSI-DVDs this would be a strong argument for me to buy a
> SCSI-controller, too.

Most all of the DVD-ROM drives will work effectiely as CD-ROM drives.
(ie: reads CDs and CR-R/RW disks, but not DVD or DVD movies) I have an
IDE one at work that works just fine.

One of the only SCSI DVD's I've seen is the Pioneer DVD303, which is
SCSI-2 w/512K cache, and slot-loading, which is *very* cool. They're
US$140.00 at http://www.megahaus.com/ They also have ATAPI units for
about $90 - $100, but I think SCSI and slot-loading are worth the $40!

If you'd like a nice DVD icon for the drive, let me know and I'll email
one to you.

--
-Steven Hunter                *OS/2 Warp 4 * |But on the other hand...|
hunters@sapphire.indstate.edu *AMD K6-2 400* |There's 5 more fingers. |


Sent via Deja.com http://www.deja.com/
Before you buy.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Deja.com - Before you buy. (1:109/42)

+----------------------------------------------------------------------------+

From: pjfloyd@my-deja.com                               17-Dec-99 09:16:16
  To: All                                               17-Dec-99 10:29:26
Subj: Re: DVD-ROM and OS/2 ?

From: pjfloyd@my-deja.com

In article <83c91d$tnq$1@nnrp1.deja.com>,
  hunters@sapphire.indstate.edu wrote:

> Most all of the DVD-ROM drives will work effectiely as CD-ROM drives.
> (ie: reads CDs and CR-R/RW disks, but not DVD or DVD movies) I have an
> IDE one at work that works just fine.

I'm not so sure that a DVD drive will read a CD-RW disk.

> One of the only SCSI DVD's I've seen is the Pioneer DVD303, which is
> SCSI-2 w/512K cache, and slot-loading, which is *very* cool. They're
> US$140.00 at http://www.megahaus.com/ They also have ATAPI units for
> about $90 - $100, but I think SCSI and slot-loading are worth the $40!

When I bought mine I considered both the Pioneer and the
Toshiba SD-M1201. Though the Pioneer's slot loading may look
cool, I have doubts as to whether such mechanical handling is
good for the disks. The Tosh uses a conventional tray. I paid around
1000FFr for mine (US$160 ish).

Salut
Paul
--
Paul Floyd
Is atrophy a shiny cup?


Sent via Deja.com http://www.deja.com/
Before you buy.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Deja.com - Before you buy. (1:109/42)

+----------------------------------------------------------------------------+

From: Peter.Druck@tp2.ruhr-uni-bochum.de                17-Dec-99 14:36:29
  To: Trevor-Hemsley@dial.pipex.com                     17-Dec-99 10:29:26
Subj: Re: Bootmanager and 9GB SCSI-Disk

To: Trevor Hemsley <Trevor-Hemsley@dial.pipex.com>
From: Peter Druck <Peter.Druck@tp2.ruhr-uni-bochum.de>

Trevor,
the added partition sizes are 8023 MB (bootmanager 7, partition 1
1000 MB, partition 2 2004 MB and partition 3 5012). Partition 3
occupies what was left.

Peter

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Institut fuer Theoretische Physik II, Ruhr Uni Bo
(1:109/42)

+----------------------------------------------------------------------------+

From: delete-this.deimos@ms1.url.com.tw                 18-Dec-99 01:01:13
  To: All                                               17-Dec-99 20:07:15
Subj: Re: DVD-ROM and OS/2 ?

From: "Deimos Jang" <delete-this.deimos@ms1.url.com.tw>

On Thu, 16 Dec 1999 17:10:34 GMT, pjfloyd@my-deja.com wrote:

>That should work fine with ISO9660 CDs. However you won't be
>able to read UDF disks (DVD and CD-R) until either IBM releases
>support (next year, costs $$$) or someone else writes a
>UDF IFS.

 Sorry for my poor english.

 Why can't? I put a DVD-ROM (a movie, "The Matrix") in my DVD-ROM then
 type "DIR /S". After several seconds, I know the total space of the DVD-ROM
 is 8,389,879,249 bytes in 7,523 files and 776 dirsis.    :>


--Deimos Jang
  www.Deimos.Jang.com -> ÏœÝù¬“¦§§“ðôÏÏ­A¾uÝüÏ@¶I¶I¦§ OS/2 ÷ˆøT§C§Cð_õõ...
  ftp.ch.hwh.edu.tw -> /OS/OS2/hobbes.nmsu.edu ü“§ë¾Ð¾x’WüÞõûóÆ¦§ Hobbes
                       mirror î÷­]ùCùƒÏ¥õ¢úsÏ@Ý÷­^­C


--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: ISnews (1:109/42)

+----------------------------------------------------------------------------+

From: merlins@ibm.net                                   17-Dec-99 17:17:15
  To: All                                               17-Dec-99 20:07:16
Subj: Re: Bootmanager and 9GB SCSI-Disk

From: Meinolf Sondermann <merlins@ibm.net>

Hello Peter,

Peter Druck wrote:
> 
> Trevor,
> the added partition sizes are 8023 MB (bootmanager 7, partition 1
> 1000 MB, partition 2 2004 MB and partition 3 5012). Partition 3
> occupies what was left.
> 
> Peter

there are two ways to access a SCSI-harddisk:

1.) via the appropoate driver for your SCSI-Card

2.) via BIOS using INT13H .

It seems that your system is using the latter one and is thus
limited by your Mainboard's BIOS .
To advice , what driver to use, you should tell us which 
SCSI-Card you are using. The aic78u2.add will only work with
some Adaptec Cards ( AIC7890-chip I think ).

Bye/2
Meinolf

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Global Network Services - Remote Access Mail & Ne
(1:109/42)

+----------------------------------------------------------------------------+

From: hunters@sapphire.indstate.edu                     17-Dec-99 18:55:23
  To: All                                               17-Dec-99 20:07:16
Subj: Re: DVD-ROM and OS/2 ?

From: hunters@sapphire.indstate.edu

In article <83cv1f$d1k$1@nnrp1.deja.com>,
  pjfloyd@my-deja.com wrote:

> I'm not so sure that a DVD drive will read a CD-RW disk.

It should, it's in the DVD specs... Espcially if it's a "second
generation" DVD drive.

--
-Steven Hunter                *OS/2 Warp 4 * |But on the other hand...|
hunters@sapphire.indstate.edu *AMD K6-2 400* |There's 5 more fingers. |


Sent via Deja.com http://www.deja.com/
Before you buy.

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Deja.com - Before you buy. (1:109/42)

+----------------------------------------------------------------------------+

From: ewilson@usa.net                                   17-Dec-99 13:28:26
  To: All                                               17-Dec-99 20:07:16
Subj: Re: MO Disk & HPFS

From: work <ewilson@usa.net>

I have been successfully using the Fujitsu 640SE drive for quite some
time on OS/2. The disks are partitioned (1 partition) and formatted for
HPFS. I have a mixture or 128, 230, and 540 disks. All working great and
very reliable. So what you are attempting is very possible!

You need to disable by rem'ing out all OEM drivers for this device.  
Only use the drivers from Sam Detwiler's package NEWDASD2. I think these
drivers have now been incorporated into the fixpacks (Driver fixpacks).
Here are the pertinent statements from my config.sys:

BASEDEV=OS2DASD.DMD /rf /of               (these switches came from
                                           Sam's package) 
rem DEVICE=C:\OS2\BOOT\OPTICAL.DMD /V
BASEDEV=OS2SCSI.DMD
BASEDEV=AHA152X.ADD                       (running on PCMCIA card in
                                           thinkpad)  

 

Alex Blair wrote:
> 
> I am trying again to get HPFS support for a Fujitsu Dynamo 640 SE drive with
> the n512dasd.flt file as suggested by others. All is well when using the
> Fujitsu driver (modisk.sys) except that it supports only FAT drives.
> 
> I have tried this on 2 systems but cannot get either to function properly.
> The last attempts on both systems show that a removable device is
virtualized
> at boot time. However, the device is recognized as an ATAPI CD ROM drive,
not
> an MO drive (or is the n512dasd.flt virtualizing the CDROM drive a second
> time?). What might I be doing wrong?
> 
> Here are the pertinent config.sys lines from the home office system in
> (relative) order of appearance in the config.sys file :
> 
> REM ** Optical Drive **
> rem BASEDEV=OS2ASPI.DMD /SHARE
> BASEDEV=OS2ASPI.DMD /ALL
> 
> REM ** For HPFS support on Optical Drives **
> BASEDEV=N512DASD.FLT /v
> 
> REM /rf Switch for Removeable Media
> REM BASEDEV=OS2DASD.DMD /rf
> 
> REM /of Switch for Optical Media
> BASEDEV=OS2DASD.DMD /of /rf
> REM ** I have tried also the /of swith alone **
> 
> REM ** SCSI Card **
> BASEDEV=SIGSCSI.ADD
> BASEDEV=OS2SCSI.DMD
> 
> REM ** Fujitsu 3.5" SCSI MO Disk Device Driver (ver 2.1 US) **
> rem DEVICE=\OS2\MODISK.SYS /R1
> 
> Any help is greatly appreciated.
> 
> Alex Blair
> ablair@ibm.net

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: IBM Global Services North -- Burlington, Vermont,
(1:109/42)

+----------------------------------------------------------------------------+

From: ewilson@usa.net                                   17-Dec-99 13:35:09
  To: All                                               17-Dec-99 20:07:16
Subj: Re: MO Disk & HPFS

From: work <ewilson@usa.net>

Forgot to add. Also in the NEWDASD package were:

BASEDEV=IBMIDECD.FLT
BASEDEV=IBM1S506.ADD


 

work wrote:
> 
> I have been successfully using the Fujitsu 640SE drive for quite some
> time on OS/2. The disks are partitioned (1 partition) and formatted for
> HPFS. I have a mixture or 128, 230, and 540 disks. All working great and
> very reliable. So what you are attempting is very possible!
> 
> You need to disable by rem'ing out all OEM drivers for this device.
> Only use the drivers from Sam Detwiler's package NEWDASD2. I think these
> drivers have now been incorporated into the fixpacks (Driver fixpacks).
> Here are the pertinent statements from my config.sys:
> 
> BASEDEV=OS2DASD.DMD /rf /of               (these switches came from
>                                            Sam's package)
> rem DEVICE=C:\OS2\BOOT\OPTICAL.DMD /V
> BASEDEV=OS2SCSI.DMD
> BASEDEV=AHA152X.ADD                       (running on PCMCIA card in
>                                            thinkpad)
> 
> 
> 
> Alex Blair wrote:
> >
> > I am trying again to get HPFS support for a Fujitsu Dynamo 640 SE drive
with
> > the n512dasd.flt file as suggested by others. All is well when using the
> > Fujitsu driver (modisk.sys) except that it supports only FAT drives.
> >
> > I have tried this on 2 systems but cannot get either to function properly.
> > The last attempts on both systems show that a removable device is
virtualized
> > at boot time. However, the device is recognized as an ATAPI CD ROM drive,
not
> > an MO drive (or is the n512dasd.flt virtualizing the CDROM drive a second
> > time?). What might I be doing wrong?
> >
> > Here are the pertinent config.sys lines from the home office system in
> > (relative) order of appearance in the config.sys file :
> >
> > REM ** Optical Drive **
> > rem BASEDEV=OS2ASPI.DMD /SHARE
> > BASEDEV=OS2ASPI.DMD /ALL
> >
> > REM ** For HPFS support on Optical Drives **
> > BASEDEV=N512DASD.FLT /v
> >
> > REM /rf Switch for Removeable Media
> > REM BASEDEV=OS2DASD.DMD /rf
> >
> > REM /of Switch for Optical Media
> > BASEDEV=OS2DASD.DMD /of /rf
> > REM ** I have tried also the /of swith alone **
> >
> > REM ** SCSI Card **
> > BASEDEV=SIGSCSI.ADD
> > BASEDEV=OS2SCSI.DMD
> >
> > REM ** Fujitsu 3.5" SCSI MO Disk Device Driver (ver 2.1 US) **
> > rem DEVICE=\OS2\MODISK.SYS /R1
> >
> > Any help is greatly appreciated.
> >
> > Alex Blair
> > ablair@ibm.net

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: IBM Global Services North -- Burlington, Vermont,
(1:109/42)

+----------------------------------------------------------------------------+

From: as@sci.fi                                         16-Dec-99 20:14:13
  To: All                                               17-Dec-99 20:07:16
Subj: Re: ExaByte 8200 & tar

From: Anssi Saari <as@sci.fi>

jpolt@bradnet.legend.co.uk (John Poltorak) writes:

> Has anyone managed to use tar (part of GTAK258) with an ExaByte 8200
> tape drive?

Yes. Works fine here. Free backup software for a free tape drive :)

However, I thought tar is not part of GTAK? I at least have downloaded
a separate tar package.

-- 
Anssi Saari - as@sci.fi

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Tampere University of Technology (1:109/42)

+----------------------------------------------------------------------------+

From: Trevor-Hemsley@dial.pipex.com                     17-Dec-99 19:22:06
  To: All                                               17-Dec-99 20:07:16
Subj: Re: Bootmanager and 9GB SCSI-Disk

From: "Trevor Hemsley" <Trevor-Hemsley@dial.pipex.com>

On Fri, 17 Dec 1999 14:36:58 +0100, Peter Druck wrote:

->Trevor,
->the added partition sizes are 8023 MB (bootmanager 7, partition 1
->1000 MB, partition 2 2004 MB and partition 3 5012). Partition 3
->occupies what was left.

I agree with Meinholf that you appear to be accessing the disk via
IBMINT13.I13 instead of the correct driver. However one complication may
be that OS/2 tries desperately to respect the original partitioning scheme
and geometry that was used when the disk was first partitioned. If you did
your initial partitioning from a boot that was using IBMINT13.I13 and
subsequently switched to the correct driver for later boots then the
geometry used by IBMINT13.I13 will be written into the partition table and
OS/2 will try to use it in preference to that reported by the new driver.

The only way around this is to delete all partitions from the disk (with
attendant loss of all data) and then reboot the machine. After the reboot
- which must be using the correct driver for the controller - you can then
repartition as you want.


Trevor Hemsley, Brighton, UK
(Trevor-Hemsley@dial.pipex.com or 75704.2477@compuserve.com)



--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: UUNET WorldCom server (post doesn't reflect views
(1:109/42)

+----------------------------------------------------------------------------+

From: oliver.rick@oor.de                                16-Dec-99 22:33:00
  To: All                                               17-Dec-99 20:07:16
Subj: Re: Optical disk ejects randomly

From: oliver.rick@oor.de (Oliver Rick)

On Wed, 15 Dec 1999 William L. Hartzell wrote:

> At the Transport command level IDE and SCSI are the same. The
> DaniS506.add as well as the IBM1S506.ADD handles SCSI drives.

The driver (device management driver to be exact) you mean is OS2DASD.DMD.

> The pop out problem is caused by the PMShell calling for status on the
> drive everytime you do somethimg with any drive.

Good point! To John: If you don't have it in your CONFIG.SYS, add
AUTOFAIL=YES. HTH!

> I think there was a switch mentioned with Warp 3.0 fixpack 36 readme
> that is applicable to this problem.  This switch was added to 'add'
> device driver to force it to recognize removable media.

You mean the switches /of (optical as fixed) and /rf (removable as fixed)
that were documented in the beta package. I don't think that it has any
influence on the problem ...

   /Olli/
--
IBM OS/2 Warp Update Summary:
http://www.warpupdates.de/english/warpupdates.html

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Out of Rosenheim/2 (1:109/42)

+----------------------------------------------------------------------------+

From: oliver.rick@oor.de                                16-Dec-99 21:02:22
  To: All                                               17-Dec-99 20:07:16
Subj: Re: MO Disk & HPFS

From: oliver.rick@oor.de (Oliver Rick)

On Thu, 16 Dec 1999 John Poltorak wrote:

> Where did you see these switches for OS2DASD.DMD documented?

NEWDASD beta packages, from FixPaks 6/35 on the function of /rf (removable
as fixed) is enabled by default. /of (optical as fixed) is undocumented and
officially not supported, but due to a good soul (Sam Detweiler) from IBM it
went back into the code.

> There is another basedev - OPTICAL.DMD. See if that offers you
> anything...

Support for Superfloppies only (FAT without partition table).

   /Olli/
--
IBM OS/2 Warp Update Summary:
http://www.warpupdates.de/english/warpupdates.html

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Out of Rosenheim/2 (1:109/42)

+----------------------------------------------------------------------------+

From: jpolt@bradnet.legend.co.uk                        17-Dec-99 22:02:08
  To: All                                               17-Dec-99 20:07:16
Subj: Re: ExaByte 8200 & tar

From: jpolt@bradnet.legend.co.uk (John Poltorak)

In <aszovapxbx.fsf@sci.fi>, Anssi Saari <as@sci.fi> writes:
>jpolt@bradnet.legend.co.uk (John Poltorak) writes:
>
>> Has anyone managed to use tar (part of GTAK258) with an ExaByte 8200
>> tape drive?
>
>Yes. Works fine here. Free backup software for a free tape drive :)

It just won't work here... :-(  Maybe it just doesn't like my IBM SCSI
controller,
although PSNS from WSeB works fine, but I would like to be able to share
tapes between OS/2 and AIX.

Some of the 'TAPE' functions work - rew, st, unload. But read and write don't.

>However, I thought tar is not part of GTAK? I at least have downloaded
>a separate tar package.

GTAR contains the tar program, and GTAK has the device drivers for tape
devices.

>
>-- 
>Anssi Saari - as@sci.fi
>

--
John

--- WtrGate+ v0.93.p7 sn 165
 * Origin: Usenet: Legend Internet Ltd (1:109/42)

+----------------------------------------------------------------------------+

+============================================================================+
