properly shut down. This meant: reboot Windows and let it do the automatic
scandisk. After Windows had finally started the D drive (/dev/hda8) was lost
... a little bit anoying for the data I still wanted to verify, but so what!
The problem I've now is that I can no more cfdisk, fdisk
You may need to change the partition lable. This is independent of the
underlying filesystem. You *should* be able to do this under fdisk ('m'
gives you a menu of options), but I'd back things up just in case.
On Sun, Jul 30, 2000 at 02:55:02AM -0400, Arcady Genkin wrote:
>
Arcady Genkin wrote:
> What alternatives to fdisk are there? I remember I used one once, but
> shoot me if I remember the name. ;^)
cfdisk comes to mind ... it's what I use when possible.
--
Mike Werner KA8YSD | He that is slow to believe anything and
| every
What alternatives to fdisk are there? I remember I used one once, but
shoot me if I remember the name. ;^)
Thanks,
--
Arcady Genkin
Thanks God I'm still an atheist! -- Luis Bunuel
I'm experiencing some problems with fdisk reporting BSD partitions on
a disk with ext2 partitions. I think that I did have a BSD slice on
there at the very beginning, but I don't remember whether it's still
there. It could be hdc2, but I couldn't figure out a way to mount th
:-> "Jay" == Jay Kelly <[EMAIL PROTECTED]> writes:
> I have a question on adding another drive to my potato box. I
> want to format
> it to hold window zip files to run with apache. So how would I format it
> and have apache access it for files?
I'm not sure I understand your q
Hello goup,
I have a question on adding another drive to my potato box. I want to format
it to hold window zip files to run with apache. So how would I format it
and have apache access it for files?
thanks guys
--
If Windows is the answer, then I want the problems back!
Powe
On Jun 02 2000, john smith wrote:
> nope..it still does'nt work. any other ideas?
Install dosfsutils. It contains the tool mkdosfs so that you
can format your partition. It also provides mkfs.vfat and
mkfs.msdos.
Hope this helps, Roger...
--
=-=-=-=-=-=-=-=-=-=-
Title: RE: fdisk/mkfs problem
This command also works
mkfs -t msdos -F 32 /dev/xdxx
were the first x is scsi (s) or ide (h) and the second is the device order ... 1st ide master, then slave, then 2nd ide master... then slave (a,b,c,d)... or scsi ID order, and then the partition number
nope..it still does'nt work. any other ideas?
From: Bolan Meek <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED]
To: john smith <[EMAIL PROTECTED]>
CC: debian-user@lists.debian.org
Subject: Re: fdisk/mkfs problem
Date: Fri, 02 Jun 2000 14:22:38 -0500
MIME-Vers
john smith wrote:
>
> ... mkfs -t FAT32 or mkfs -t Win95 FAT32
Try '-t vfat'.
Hi,
I have created a dos partition via linux's fdisk (FAT32) now I try to write
it I get ioctl() error..telling me that the resource or device is busy and
tells me to reboot and check that the partition is updated. I did that and
it shows in the partition table but now when I try to form
On Mon, May 15, 2000 at 03:04:30PM +0200, Oswald Buddenhagen wrote:
> > I've found that I get best results when I set the disk, in the BIOS,
> > to standard translation, rather than to LBA or Large.
After replacing util-linux v. 2.7.1-3 with v. 2.10.f-5 (and therefore
rep
> I've found that I get best results when I set the disk, in the BIOS,
> to standard translation, rather than to LBA or Large.
>
same for me. that way i get 25000+ cylinders, but it works.
it depends heavily on the disk. i have one from fujitsu.
--
Hi! I'm a .signature virus! Copy me into your
I suggest to use a partition manager (that run under Dos) and I found on
net recently (I haven't really try it, just a look, because my PC is
stable now). It seems to support very large HD.
You can find it at
http://www.uni-bonn.de/~uzsv20/
It has a boot manager too and can create Extend and swa
PS : I should add that I've not an awful lot of experience installing
Debian, since I don't have hardware to experiment with. I've only
installed on three or four different computers. (quite a few times,
but only on those few machines.)
I've found that I get best results when I set the disk, in the BIOS,
to standard translation, rather than to LBA or Large.
--
I am karlheg of deB-ORG. You will be freed.
mailto:[EMAIL PROTECTED] (Karl M. Hegbloom)
Portland, OR USA
Debian GNU Potato Linux 2.2 AMD K6-200(@233) XEmacs-21.2beta
> Maybe it isn't a problem, but fdisk complains about overlapping areas if
> I make a partition check (v):
>
> Warning: partition 10 overlaps partition 11.
> Warning: partition 10 overlaps partition 12.
> Warning: partition 11 overlaps partition 12.
> 578832 unallocated
hich is read as 1024 and is ignored
> anyway. only the starting sector number is relevant.
Maybe it isn't a problem, but fdisk complains about overlapping areas if
I make a partition check (v):
Warning: partition 10 overlaps partition 11.
Warning: partition 10 overlaps partition 12.
Warni
> /dev/sdb111024 1061 1085 200781 82 Linux swap
> /dev/sdb121024 1086 1115 240943+ 83 Linux native
>
> I deleted partition 11 and 12 but after creating a new partition starting
> at cylinder 1061 there is still the wrong bin value of 1024.
>
i don't think,
After partitioning my HD I deleted three partitions and made two new ones.
Now there is an overlapping of one partition although I didn't enter
the begin value (number of cylinders) displayed by fdisk:
---
Disk /dev/sdb
> Hi Kent
Since its a new computer, why not go to your vendor? Should have been some
kind of warranty. Dean
>
>
> This is a brand new computer. Everything was working fine until I
> cfdisked the primary drive. Then the bios can't detect either of my
> drives. The only one detected is
00, ktb
> wrote:
> > > > "Allan M. Wind" wrote:
> > > > >
> > > > > On 2000-02-24 09:40:21, ktb wrote:
> > > > >
> > > > > > I've pulled a real bone head deal it
> seems. I decided to partition the
> &
d still nothing is seen. I just
> > > don't understand how creating a new partition valid in the eyes of
> > > windows or not prevents my bios from detecting that there are HD's
> > > there?
> >
>
> John Pearson wrote:
>
> >
> > It
the eyes of
> > windows or not prevents my bios from detecting that there are HD's
> > there?
>
John Pearson wrote:
>
> It won't. If the BIOS doesn't see your drive then you need to fix
> that before any fdisk or partition-recovery software can work on
>
> > > > > I've pulled a real bone head deal it seems. I decided to partition
> > > > > the
> > > > > HD on my new system so that I could put both Windows 98 and Slink on
> > > > > it. I tried using fdisk under "dos" bu
partition the
> > > > HD on my new system so that I could put both Windows 98 and Slink on
> > > > it. I tried using fdisk under "dos" but it wouldn't let me delete the
> > > > current partition so I used the Slink installation disk and cfdisk to
&
ld put both Windows 98 and Slink on
> > > it. I tried using fdisk under "dos" but it wouldn't let me delete the
> > > current partition so I used the Slink installation disk and cfdisk to
> > > partition my HD. I cut the disk in half and added one partiti
> "ktb" == ktb <[EMAIL PROTECTED]> writes:
ktb> I didn't drop any data but I can't access anything but
ktb> bios/setup at this time. My system basically is telling me
ktb> that no HD exists. How can I restore the partition table?
This might work:
* Create a bootable floppy on
ktb wrote:
>
> "Allan M. Wind" wrote:
> >
> > On 2000-02-24 09:40:21, ktb wrote:
> >
> > > I've pulled a real bone head deal it seems. I decided to patition the
> > > HD on my new system so that I could put both Windows 98 and Slink on
&
"Allan M. Wind" wrote:
>
> On 2000-02-24 09:40:21, ktb wrote:
>
> > I've pulled a real bone head deal it seems. I decided to patition the
> > HD on my new system so that I could put both Windows 98 and Slink on
> > it. I tried using fdisk und
"Allan M. Wind" wrote:
>
> On 2000-02-24 09:40:21, ktb wrote:
>
> > I've pulled a real bone head deal it seems. I decided to patition the
> > HD on my new system so that I could put both Windows 98 and Slink on
> > it. I tried using fdisk und
On 2000-02-24 09:40:21, ktb wrote:
> I've pulled a real bone head deal it seems. I decided to patition the
> HD on my new system so that I could put both Windows 98 and Slink on
> it. I tried using fdisk under "dos" but it wouldn't let me delete the
> curre
I've pulled a real bone head deal it seems. I decided to patition the
HD on my new system so that I could put both Windows 98 and Slink on
it. I tried using fdisk under "dos" but it wouldn't let me delete the
current partition so I used the Slink installation disk and cfdis
Yesterday I discovered that the fdisk in /sbin (potato) is not
statically linked. Neither is cfdisk. I thought that all programs in
/sbin were supposed to be statically linked. Why is this not the case?
This put me in a poor position installing Debian for an old Slackware
user. Neither program
Ciao,
I think there is a problem in util-linux:
there are non more fdisk, cfdisk and sfdisk!
$ dpkg -s util-linux
Package: util-linux
Essential: yes
Status: install ok installed
Priority: required
Section: base
Installed-Size: 908
Maintainer: Vincent Renardias <[EMAIL PROTECTED]>
Version:
EMAIL PROTECTED]>
Subject: Re: cfdisk and fdisk with slink hang writing partition to SCSI
disk...uh-oh
Date: Wed, 27 Oct 1999 14:48:40 -0800
On 27/10/99 Martin Waller wrote:
(I've resorted to installing RH (6.0 or 6.1) which seems to be
coping OK (still indstalling...but got throu
k...', and the machine cycles through resetting the disk, tape and CD
time and time again.
Using fdisk came up with 'Calling IOCTL() tyo re-read partition table' (or
something similar) and again just hung.
It is annoying that debian can't install/partition the SCSI a
Ed Cogburn wrote:
>
> OK, I'm wrong about -u, it does work; I should have looked
> closer. The use of 'fdisk -l', without a device parameter, still
> doesn't work even though the man page says it should.
> According to Tom's examples and the man page, &q
Mirek Kwasniak wrote:
>
> On Tue, Sep 14, 1999 at 12:54:47PM +, Ed Cogburn wrote:
> >
> > I just tried (as root) the three fdisk examples (-l is lowercase
> > L) given above. Only the last one worked: "fdisk -l /dev/hda".
> > The -u does not
Subject: Re: FDISK parameters was Re: undelete for partition tables?
Date: Tue, Sep 14, 1999 at 12:54:47PM +
In reply to:Ed Cogburn
Quoting Ed Cogburn([EMAIL PROTECTED]):
> Tom Pfeifer wrote:
> >
> > Ed Cogburn wrote:
> >
>
>
> I
On Tue, Sep 14, 1999 at 12:54:47PM +, Ed Cogburn wrote:
>
> I just tried (as root) the three fdisk examples (-l is lowercase
> L) given above. Only the last one worked: "fdisk -l /dev/hda".
> The -u does nothing at all. Does anybody else see this behavior,
Tom Pfeifer wrote:
>
> Ed Cogburn wrote:
>
> > > In the future, I would recommend saving the output of either...
> > >
> > > 1) Linux fdisk ==>> fdisk -l > part.txt(this does all drives)
> > > 2) Ranish PM ==>> part -d 1 -p -r &
Ramakrishnan M wrote:
>
> On Tue, 14 Sep 1999, Tom Pfeifer wrote:
>
> > Ranish Partition Manager is a DOS program, but is an excellent
> > partitioning tool. It's source code is available for download from the
> > web site. At one the time the author was planning on porting it over to
>
> Which
On Tue, 14 Sep 1999, Tom Pfeifer wrote:
> Ranish Partition Manager is a DOS program, but is an excellent
> partitioning tool. It's source code is available for download from the
> web site. At one the time the author was planning on porting it over to
Which site?
Ramakrishnan M
World Wide Web:
Ed Cogburn wrote:
> > In the future, I would recommend saving the output of either...
> >
> > 1) Linux fdisk ==>> fdisk -l > part.txt(this does all drives)
> > 2) Ranish PM ==>> part -d 1 -p -r > part.txt (for each drive)
>
> Tom
Tom Pfeifer wrote:
>
> > > Question: Was that possibly a Linux extended partition (type 85) as
> > > opposed to a DOS extnded partition? That would explain why DOS fdisk
> > > could delete it.
> >
> > Yes, originally this computer was set up by me wit
On Mon, 13 Sep 1999, Adrian Thompson wrote:
: Hello,
:
: Linux fdisk doesn't see past 1024 cylindars, I have a 20.4GB HD which
: requires over 2000 cylindars. As well I have win95 on hda1, I want to
: put linux on hda2, however lilo doesn't sit well in a FAT32, or screws
: up
Hello,
Linux fdisk doesn't see past 1024 cylindars, I have a 20.4GB HD which
requires over 2000 cylindars. As well I have win95 on hda1, I want to
put linux on hda2, however lilo doesn't sit well in a FAT32, or screws
up because of the HD size.
Hardware specs: MB =ASUS Fla
-BEGIN PGP SIGNED MESSAGE-
On Fri, 3 Sep 1999, Michael Konrad wrote:
> I always set up my swap partition as a primary partition and I don't
> have that problem. I can never read the blocks right, but it looks like
> the swap partition is more than 128MB. You can set up multiple swap
> par
I always set up my swap partition as a primary partition and I don't
have that problem. I can never read the blocks right, but it looks like
the swap partition is more than 128MB. You can set up multiple swap
partitions but they can not be more than 128MB.
-Michael
Michael Konrad
-BEGIN PGP SIGNED MESSAGE-
On Wed, 25 Aug 1999, Andrei Ivanov wrote:
> >
> >Device Boot Start End Blocks Id System
> >/dev/hda1 *1 4063 2047720+ 83 Linux native
> >/dev/hda2 4064 8127 2048256 83 Linux native
> >
On Thu, 26 Aug, 1999 à 11:49:05AM +1000, Shao Zhang wrote:
> Hi,
> Recenltly, I repartitioned my harddisk. What I did is to delete
> the swap parttion(/dev/hda2), created a 2gig linux
> partition(/dev/hda2), then created a swap partition(/dev/hda3).
>
[...]
>
> Anyway I di
Subject: Re: trouble with fdisk and activate the swap
Date: Wed, Aug 25, 1999 at 08:57:58PM -0500
In reply to:Andrei Ivanov
Quoting Andrei Ivanov([EMAIL PROTECTED]):
> >
> >Device Boot Start End Blocks Id System
> >/dev/hda1 *
>
> Device Boot Start End Blocks Id System
> /dev/hda1 *1 4063 2047720+ 83 Linux native
> /dev/hda2 4064 8127 2048256 83 Linux native
> /dev/hda3 8128 8400 137592 82 Linux swap
Wrong. You created Swa
Hi,
Recenltly, I repartitioned my harddisk. What I did is to delete
the swap parttion(/dev/hda2), created a 2gig linux
partition(/dev/hda2), then created a swap partition(/dev/hda3).
My fdisk output looks like this:
Command (m for help): p
Disk
Dear John:
Thanks for the reply. It would seem indeed that you have had some
unfortunate experiences with windows. I too am in the process of weaning
myself from windows, but as I noted before, there are still too
many programs that have not made the transition to the linux environment.
I
flag with fdisk. The
other day, my computer woke up, while trying to boot into w98, with the
message "error loading keyboard.drv. You must reinstall windows." However,
w98 has the nasty proclivity to demand the entire disk to (re)install it.
My Linux partition is fine, and I can access all
I was putting a new computer together today for a friend. I needed to
partition a brand-new HD, and because I hate MSDOS's fdisk, I figured
I'd use Linux's rescue disk with fdisk.
Anyhow, I created the partitions alright, but can I create the file
system on them? Can I format a
, just bugged out saying that it encountered
a error. I switch virtual console and ran fdisk and tried to add a new
partition. It didnt work, fdisk complained about the logical and physical
offsets, or something, was not the same. And that there were no free
sectors, however when i printed the partition
At 09:56 PM 3/19/99 -0500, Jayson Baird wrote:
>anyone know that obscure fdisk command to clean the master boot record of a
>drive?
>
> thanks
from : http://www.debian.org/Lists-Archives/debian-user-9902/msg01807.html
"fdisk /
anyone know that obscure fdisk command to clean the master boot record of a
drive?
thanks
[EMAIL PROTECTED]
[EMAIL PROTECTED] (Cyillic only)
http://www.concentric.net/~jsbaird
superformat -Da: --dosverify /dev/fd0
> Using Fdisk on a Disk that has a working copy of Win 98 which i wanted to
> put Debian on i get this error:
> Checking Boot sector
> Error: Number of Sectors
> (long) does not match partition info
> 2411873 instead of 3322305
> Please help!
Stephen Lavelle wrote:
>
> Using Fdisk on a Disk that has a working copy of Win 98 which i wanted to
> put Debian on i get this error:
> Checking Boot sector
> Error: Number of Sectors
> (long) does not match partition info
> 2411873 instead of 3322305
> Please help
Using Fdisk on a Disk that has a working copy of Win 98 which i wanted to
put Debian on i get this error:
Checking Boot sector
Error: Number of Sectors
(long) does not match partition info
2411873 instead of 3322305
Please help!
Regards,
Stephen Lavelle
Austanners Wet Blue Pty Ltd.
~ Australian
Using Fdisk on a Disk that has a working copy of Win 98 which i wanted to
put Debian on i get this error:
Checking Boot sector
Error: Number of Sectors
(long) does not match partition info
2411873 instead of 3322305
Please help!
Regards,
Stephen Lavelle
Austanners Wet Blue Pty Ltd.
~ Australian
Olaf Meeuwissen wrote:
>
> More specifically, I would like to specify exactly what cylinders partitions
> are to start and to end on.
Take a look at Ranish Partition Manager. It's a DOS program (open
source), but it can do what you want. The newer version (beta 2.38) can
handle disks over 8.4 GB.
Hi,
I've been playing around with multi-OS installation (Debian/Window$98)
for a bit and was wondering if it is possible to use Linux' `fdisk'
without having Linux installed (yet) since it is more powerful than
the `cfdisk' program the installer uses. More specifically, I w
; got that.. now do i just work from the hda partition in fdisk, destroy it
> > and rebuild?
> >
> > fdisk is not the most obvious program!
>
> uh-huh WARNING: back up everything first - doing this will wipe the
> contents of the hda partion at least. I do not want to be
On Thu, 3 Sep 1998, David Parmet wrote:
> On Thu, 3 Sep 1998, M.C. Vernon wrote:
>
> > You haven't put the free space into a partition.
>
> got that.. now do i just work from the hda partition in fdisk, destroy it
> and rebuild?
>
> fdisk is not the most
On Thu, 3 Sep 1998, M.C. Vernon wrote:
> You haven't put the free space into a partition.
got that.. now do i just work from the hda partition in fdisk, destroy it
and rebuild?
fdisk is not the most obvious program!
debian-user@lists.debian.org
Date: Thursday, September 03, 1998 7:20 AM
Subject: fdisk
>
>
>i'm trying to eliminate one partition (accidentally i made two swap
>partitions.. i'm a newbie). ran fdisk, edited fstab so far so good.
>rebooted ok. so far so good.
>
>i type
i'm trying to eliminate one partition (accidentally i made two swap
partitions.. i'm a newbie). ran fdisk, edited fstab so far so good.
rebooted ok. so far so good.
i typed df and the freed up space (25 megs) still doesn't show up.
any suggestions in fdisk? basicall
On Wed, 2 Sep 1998, David Parmet wrote:
> i'm trying to eliminate one partition (accidentally i made two swap
> partitions.. i'm a newbie). ran fdisk, edited fstab so far so good.
> rebooted ok. so far so good.
>
> i typed df and the freed up space (25 megs) still do
David Parmet wrote:
>
> i'm trying to eliminate one partition (accidentally i made two swap
> partitions.. i'm a newbie). ran fdisk, edited fstab so far so good.
> rebooted ok. so far so good.
>
> i typed df and the freed up space (25 megs) still doesn't show
i'm trying to eliminate one partition (accidentally i made two swap
partitions.. i'm a newbie). ran fdisk, edited fstab so far so good.
rebooted ok. so far so good.
i typed df and the freed up space (25 megs) still doesn't show up.
any suggestions in fdisk? basicall
Got this figured out, sort of. I don't know why, but fdisk seems to
act differently for the fujitsu drives as compared to Western Digital,
Samsung, Seagate and O'Connor drives I have or have had. I always just
accepted defaults for the first cylinder when creating new partition
l the
partitions and set up LILO, but LILO setup failed with:
Device 0X0300: Invalid partition table, 3rd entry
3D address: 1/0/78 (73710)
linear address: 55/11/21 (20592)
fdisk reported the first four partitions not ending on cylinder boundaries.
Also, the beginning, startin
You're right. I used Win95's OSR2 fdisk tool. Now since my last message I
have found a tool, partinfo, which is made by Power Quest,
the guys that do Partition Magic. When I ran this tool on my partition
table it told me this:
C:WIN95FAT16B Pri,Boot 509.8 0 0 63
jonas wrote,
>This is exactly what OpenDOS did with my Linux system too. I fixed the
>problem by using Linux fdisk. I noted all the start and end cylinders of
>all partitions, then I removed them all and recreated them at their proper
>places. No information on the partitions were
OpenDOS did with my Linux system too. I fixed the
problem by using Linux fdisk. I noted all the start and end cylinders of
all partitions, then I removed them all and recreated them at their proper
places. No information on the partitions were lost in the process, but
don't take my word for it
Asher Haig wrote,
> Dosemu actually looks for mounted dos parititions that have the files on
> them that make it bootable, I believe, rather than the bootable partition
> flag.
I want to say that I tried mounting and that it didn't work, but I'm not sure.
Either way, it's done :(
> As for t
Richard E. Hawkins Esq., [EMAIL PROTECTED] on 3/21/98 1:23 PM
>
>now only dos could boot. tried switching back, but the partition table
>seems
>to have shifted , to hda2, 3, and 4.
>
>I can boot off a diskette, and briefly had lilo booting to linux. I changed
>fstab and lilo.config to reflect
play with dosemu again.
It only wants to look at bootable partitions, so i used fdisk (linux) to
toggle hda1 to bootable. I didn't toggle hda2 while I was at it. dosemu
happily set itself up.
reboot, and it's to dos. i don't htink lilo ever shoed, but maybe it did.
hmm, this
Fdisk reports that the physical and logical number of cylinders on a
partition are different:
Disk /dev/hda: 128 heads, 63 sectors, 620 cylinders
Units = cylinders of 8064 * 512 bytes
Device Boot BeginStart End Blocks Id System
/dev/hda111 172 693472
utilized by the ext2 file
system for inodes, superblocks, accounting data, etc. My /dev/hda8
contains 974736 blocks according to fdisk, but, when formatted and
mounted, df reports its size as 943438 blocks.
--
_
|_) _ |_ Robert D. Hilliard<[EMAIL PROTECTED]>
|_) (_) |_)
ent. How can I access this space again, without
> competely formatting the entire HDD?
I don't know how you determined that a half gigabyte was "lost", but
you can look at your linux partition table with "fdisk -l" (as root,
man fdisk). THis will show the beginning and endi
>If you are going to use linux with that drive then you must use NORMAL
>mode. I noticed that number of heads affect how much DOS FDISK says size
>to be use. This drive have only 9 heads and lots of cylinders, so 1024
>cylinders mean only 283 MB room for DOS. My another drive have 1
Helmut Leinfellner writes:
> > Did you create the DOS partitions in Linux or in DOS? If you did
> >it from Linux, you should delete the partition and recreate it using
> >DOS's fdisk. In general, partitions should be created using tools
> >from the OS that wil
At 14:56 27.02.98 -0500, you wrote:
>HELMUT LEINFELLNER writes:
>> DOS fdisk gives:
>>
>> 1 PRI DOS YESHUA 1000 FAT16 100%
>> 2 EXT DOS1000 100%
>> 3 Non-DOS 6423%
>> 4 Non-DOS2047 100%
>>
>&
HELMUT LEINFELLNER writes:
> DOS fdisk gives:
>
> 1 PRI DOS YESHUA 1000 FAT16 100%
> 2 EXT DOS1000 100%
> 3 Non-DOS 6423%
> 4 Non-DOS2047 100%
>
> Partition 3 + 4 are Linux swap and Linux native, respectively.
> DOS fdisk
ly run both Win95 and Linux
> : > : on different partitions. The key to this was to put the DOS partitions
> : > : FIRST.
> : > : The only thing still to solve right now is this:
> : > : DOS fdisk gives:
> : > :
> : > : 1 PRI DOS YESHUA 1000 FAT16 100%
> : > : 2
is was to put the DOS partitions
: > : FIRST.
: > : The only thing still to solve right now is this:
: > : DOS fdisk gives:
: > :
: > : 1 PRI DOS YESHUA 1000 FAT16 100%
: > : 2 EXT DOS1000 100%
: > : 3 Non-DOS 6423%
: > : 4 Non-DOS2047
ng still to solve right now is this:
> : DOS fdisk gives:
> :
> : 1 PRI DOS YESHUA 1000 FAT16 100%
> : 2 EXT DOS1000 100%
> : 3 Non-DOS 6423%
> : 4 Non-DOS2047 100%
> :
> : Partition 3 + 4 are Linux swap and Linux native, res
ng still to solve right now is this:
> : DOS fdisk gives:
> :
> : 1 PRI DOS YESHUA 1000 FAT16 100%
> : 2 EXT DOS1000 100%
> : 3 Non-DOS 6423%
> : 4 Non-DOS2047 100%
> :
> : Partition 3 + 4 are Linux swap and Linux native, res
On Fri, 27 Feb 1998, HELMUT LEINFELLNER wrote:
: Hi !
:
: Just wanted to let you know that I can finally run both Win95 and Linux
: on different partitions. The key to this was to put the DOS partitions
: FIRST.
: The only thing still to solve right now is this:
: DOS fdisk gives:
:
: 1 PRI DOS
Hi !
Just wanted to let you know that I can finally run both Win95 and Linux
on different partitions. The key to this was to put the DOS partitions
FIRST.
The only thing still to solve right now is this:
DOS fdisk gives:
1 PRI DOS YESHUA 1000 FAT16 100%
2 EXT DOS1000 100%
3 Non-DOS
You probably have an old BIOS. Old bios is known not to recognize HD over
528M, unless special measures, such as LBA, are incoperated.
Besides, I think that DOS would not recognize a partition that is over 2.1G.
I use Linux with a HD that the BIOS sees as LBA.
Does all this BIOS/DOS problems are
s should be OK for linux, despite the warning. As I
understand it, fdisk gets values for the begin column from the bios,
but the other columns are calculated by fdisk. The bios figures are
wrong when they refer to cylinders above 1024. The verify results are
based on the bios data, and always
t 82MB and another have 15 heads and
show something over hundres MB, but not what it supposed to be...
> I already did as you suggested and cleared the partition table, rewrote it,
> but the effect was the same.
> DOS FDISK doesn't even recognize the size of the whole disk (4.3 G
201 - 300 of 347 matches
Mail list logo
