Re: Seagate ST340824A and (un)clipping max LBA: 2.2.19+ide04092001 patch

2001-04-30 Thread Alexander Stavitsky
On Sat, Apr 28, 2001 at 12:22:07AM +0200, [EMAIL PROTECTED] wrote: > No. Maybe someone can tell us about its origin, but in your case > of course this just works because 0xa intersects 0x306b. You might > comment out this entire test. If I comment out the entire test, it would try to unclip

Re: Seagate ST340824A and (un)clipping max LBA: 2.2.19+ide04092001 patch

2001-04-30 Thread Alexander Stavitsky
On Sat, Apr 28, 2001 at 12:22:07AM +0200, [EMAIL PROTECTED] wrote: No. Maybe someone can tell us about its origin, but in your case of course this just works because 0xa intersects 0x306b. You might comment out this entire test. If I comment out the entire test, it would try to unclip the

Seagate ST340824A and (un)clipping max LBA: 2.2.19+ide04092001 patch

2001-04-27 Thread Alexander Stavitsky
Disk capacity unclipping routines in ide.2.2.19.04092001.patch do not unclip Seagate ST340824A. I have to use the jumper on the drive to make system boot. I tried "setmax" program and it is able to unclip the capacity, kernel however does not. I digged a little and I think the problem is that

Seagate ST340824A and (un)clipping max LBA: 2.2.19+ide04092001 patch

2001-04-27 Thread Alexander Stavitsky
Disk capacity unclipping routines in ide.2.2.19.04092001.patch do not unclip Seagate ST340824A. I have to use the jumper on the drive to make system boot. I tried setmax program and it is able to unclip the capacity, kernel however does not. I digged a little and I think the problem is that