-> For the time being ATAPI is the least of your problems. You said
-> some where that you have a ram based setup. Can't you make a Linux
-> boot floppy and fdisk from that? I mean of course after you have
-> moved the H/D to the /dev/hda position.

Interesting idea but the motherboard BIOS won't see over 32 Gig.
I already have a Tom's rootboot disk made up.
In any case the Knoppix release already gives me that capability
from ram drive but no longer sees the drive after the Windows 
installation attempt.

-> -> If it can see only 8gig then
-> -> so be it. Give the entire disk over to Windows after you have destroyed
-> -> all partitions. Then split it in half using "fips"
and Linux the rest.

-> WC> Yeah, had I run FIPS even in it's -t option I could use restorrb
-> WC> and rewrite the MBR.

-> Oh well we all make mistakes. That is some times how we have to learn.

-> -> When or if it works then move it to /dev/hde and see if it will boot.

-> -> By the way did it boot when you installed Linux the first time?

On the previous drive a 6.4 Gig everything went fine, dual boot
Linux - Win 98.
It's that one lousy Gig over 64 that caused Windows defective fdisk to
scramble the drive.

-> WC> Oh absolutely, Linux saw the drive perfectly and fdisk -l
-> WC> listed all partitions as I'd allocated them.
-> WC> Then came Windows :-(

-> You probably would have been better off with a direct lightning 
-> strike. :)

Feels about like that.

-> -> If that works then you can fdisk using Linux to get the larger size.

-> WC> I don't think anything will work now as neither Linux fdisk -l
-> WC> or fdisk /dev/hde works failing to see a hard drive.
-> WC> This after Windows installation attempt.

-> Just thinking something won't work doesn't mean it won't. After
-> all what ever you try now can hardly do much more damage.

-> -> If you want to make the Linux partition larger then it shouldn't
-> -> be a
-> -> problem. You should also be able to use some space for another
-> -> Windows
-> -> partition. Don't forget once you have grabbed the lower portion of the
-> -> disk (notional 1024) cylinders you can do as you please with the rest.

-> WC> Nope, no more Windows for me thank you.

-> I always have a small Win on my machines encase Linux has trouble with
-> new hardware. If the manufacturer is being a pain in the arse and not
-> releasing information, you can at least find out what the interrupt and
-> io addresses are. Also my bank uses MS Java. :(

My bank uses software compatible with Mozilla running in this 
ramdisk Linux.

-> I think you must put that disk IDE 0 master even though you must be
-> getting fed up with the whole thing by now. 
   
I am fed up and will wait until next month to purchase a BIOS'ed I/O 
card that supports ATAPI without drivers.

I've little stamina in my present state of health and have to 
work on the computer laying down turning it as neccessary
on the wheeled cart on which it sits. 

-> If you do then let me know
-> what you can see. What have got to lose? Maybe if that doesn't work
-> we throw our hats into the Linux echo and see what we get.

Well I'm not going to make the trip to Comp USA for an I/O 
card alone to only find it doesn't work, instead I'll buy the card
AND a hard drive.

I'll see about the 65 Gig drive after that.
--- Platinum Xpress/Win/WINServer v3.0pr5