🚀 go-pugleaf

On Thu, 11 May 2000 21:01:34 +0000,
Paul Richards (Pauldoo) <pauldoo@dunvegan1.demon.co.uk> wrote:
> I've came across a weird problem with MS f(uck)disk in that it hangs on
> loading.

I seem to remember not being able to get MS fdisk to work. This
seemed simply to be due to the fact that I had partitions it didn't
like the types of (ie. Linux ext2 & swap).

I usually end up partitioning under linux, then doing a 'format c:'
from my Win95 boot floppy before I install Windows. (I have a 1GB
partition that is used for occasional useful things such as
filesystem experiments, and from time to time has Win95 installed).


Andrew
-- 
Andrew McDonald
andrew@mcdonald.org.uk
http://www.mcdonald.org.uk/andrew/
OpenPGP DSA/ElG 1024/2048  3EDE 0FBC 6138 DCA0 FC8E C508 FCBB A9C8 F2DE ED36

Hi

i am not sure why you are posting promblems to do with M$ products here but i to did have
problems with MS fdisk the symtoms were

no visable drives in the logical partion and when i tried to delete the logical
partion it says there was a drive in the logical partion so i could not delete it
hum like to see an explanation for that ;)

the linux fdisk worked fine like it always does

cya
	James

On Thu, 11 May 2000 21:01:34 +0000, Paul Richards (Pauldoo) <pauldoo@dunvegan1.demon.co.uk> wrote:
>Hi,
>I've came across a weird problem with MS f(uck)disk in that it hangs on
>loading.
>
>I get the prompt about enabling large disk support and I press "y".  The
>screen goes blank and the IDE light goes on and the thing hangs.  OFC
>linux fdisk sees everything as just fine:
>
>Disk /dev/hda: 255 heads, 63 sectors, 1869 cylinders
>Units = cylinders of 16065 * 512 bytes
>
>   Device Boot    Start       End    Blocks   Id  System
>/dev/hda1   *         1       830   6666943+  83  Linux
>/dev/hda2           831      1023   1550272+   b  Win95 FAT32
>/dev/hda3          1024      1869   6795495    5  Extended
>/dev/hda5          1024      1853   6666943+  83  Linux
>/dev/hda6          1854      1869    128488+  82  Linux swap
>
>I'll spend more time tommorrow investigating possible sources of the
>problem but for now does anyone see anything obvious?
>
>The MS bootloader is in the MBR and lilo on hda1 if that matters...
>
>Here is my only guess:
>hda2 was partitioned and formated by linux (fdisk, mkdosfs) instead of
>by (ms fdisk, format)  -  I don't think this can be true though because
>the Win98 boot disk can see "C:" just fine.
>
>
>MS fdisk not loading isn't really a problem because I think I could
>install W98 on there anyway but I'd like to pinpoint the problem in case
>something bad happens because of it...
>
>TIA,
>-- 
>Paul Richards (Pauldoo) - http://www.pauldoo.co.uk


-- 
---------------------------------------------
Check Out: http://www.users.zetnet.co.uk/james/
E-Mail: mistral@stevenson.zetnet.co.uk
 11:50pm  up 7 days, 10:04,  8 users,  load average: 2.16, 1.59, 1.49

This was written by "Paul Richards (Pauldoo)" in uk.comp.os.linux...
|> Disk /dev/hda: 255 heads, 63 sectors, 1869 cylinders
|> Units = cylinders of 16065 * 512 bytes
|> 
|>    Device Boot    Start       End    Blocks   Id  System
|> /dev/hda1   *         1       830   6666943+  83  Linux
|> /dev/hda2           831      1023   1550272+   b  Win95 FAT32
|> /dev/hda3          1024      1869   6795495    5  Extended
|> /dev/hda5          1024      1853   6666943+  83  Linux
|> /dev/hda6          1854      1869    128488+  82  Linux swap
|> 
|> I'll spend more time tommorrow investigating possible sources of the
|> problem but for now does anyone see anything obvious?

	IME MS-DOS (and thus Windows) typically has trouble finding DOS
partitions if there are any non-DOS partitions earlier in the partition
table, and gets horribly confused.
	Reorder things so that all your DOS partitions come first, then
your non-DOS partitions, that might help. Usually I give DOS the first
three primary partitions on a hard drive, and then put all my non-DOS
partitions in the extended/ logical partition(s). An example from my
system;

-----
Disk /dev/hda: 255 heads, 63 sectors, 1247 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       261   2096451    6  FAT16
/dev/hda3           415       621   1662727+   6  FAT16
/dev/hda4           622      1247   5028345    5  Extended
/dev/hda5           622       673    417658+  83  Linux
/dev/hda6           674       881   1670728+  83  Linux
/dev/hda7           882       959    626503+  83  Linux
/dev/hda8           960       985    208813+  83  Linux
/dev/hda9           986      1011    208813+  83  Linux
/dev/hda10         1012      1115    835348+  83  Linux
/dev/hda11         1116      1247   1060258+  83  Linux

Disk /dev/hdb: 255 heads, 63 sectors, 524 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdb1   *         1       130   1044193+   6  FAT16
/dev/hdb2           131       195    522112+   6  FAT16
/dev/hdb3           196       260    522112+   6  FAT16
/dev/hdb4           261       524   2120580    5  Extended
/dev/hdb5           261       276    128488+  82  Linux swap
/dev/hdb6           277       524   1992028+  83  Linux

Disk /dev/hdd: 64 heads, 63 sectors, 528 cylinders
Units = cylinders of 4032 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdd1   *         1       130    262048+   6  FAT16
/dev/hdd2           131       195    131040    6  FAT16
/dev/hdd3           196       260    131040    6  FAT16
/dev/hdd4           261       528    540288    5  Extended
-----

	Yes, I know hda is a bit screwed up, that's because I'm
rearranging it :-) .

		dunc
-- 
 _| _ _  _  ___  _  ___  "Willow, you're alive?"  -Buffy
(_| \_/ / \ \_  /-\ \ /  "Aren't I usually?"     -Willow

This was written by James Stevenson in uk.comp.os.linux...
|> no visable drives in the logical partion and when i tried to delete the logical
|> partion it says there was a drive in the logical partion so i could not delete it
|> hum like to see an explanation for that ;)

	MS' fdisk program is really badly written. It can't show you
non-DOS partitions, but it knows they're there. Sometimes. Sort of. And it
doesn't like creating more than one primary partition. And it has some
funny ideas about flagging/ defining/ calculating partition sizes. And so
on...

|> the linux fdisk worked fine like it always does

	Of course it would. It was written by people who care more about
creating quality, versatile, interoperable tools rather than doing just
enough to earn their paycheck and sell some product.

		dunc

PS. You may want to fix your line length/ wrapping. This xterm is eighty
	columns wide, yours seems to be around eighty-five columns wide...
-- 
 _| _ _  _  ___  _  ___  "Willow, you're alive?"  -Buffy
(_| \_/ / \ \_  /-\ \ /  "Aren't I usually?"     -Willow

duncan corps wrote:
> 
> This was written by James Stevenson in uk.comp.os.linux...
> |> no visable drives in the logical partion and when i tried to delete the logical
> |> partion it says there was a drive in the logical partion so i could not delete it
> |> hum like to see an explanation for that ;)
> 
>         MS' fdisk program is really badly written. It can't show you
> non-DOS partitions, but it knows they're there. Sometimes. Sort of. And it
> doesn't like creating more than one primary partition. And it has some
> funny ideas about flagging/ defining/ calculating partition sizes. And so
> on...

That reminds me of a time when I used ms fdisk to make the fat partition
and it acutally overlapped my linux partition..  I never noticed until I
had formated both partitions several times wondering where all the
errors came from...  :)
-- 
Paul Richards (Pauldoo) - http://www.pauldoo.co.uk

On Thu, 11 May 2000, Andrew McDonald wrote:

> On Thu, 11 May 2000 21:01:34 +0000,
> Paul Richards (Pauldoo) <pauldoo@dunvegan1.demon.co.uk> wrote:
> > I've came across a weird problem with MS f(uck)disk in that it hangs on
> > loading.

Talking about fdisk and windows, I have a problem too :)
I have an 8.6 gig hard drive, 7gig is taken up by my ext2 usr and root
partitions, a bit of swap, and then theres some free that I wanted to
stick windows on so I could play unreal tournament better (linux version
is dodgy with mouse/keyboard input :( - anyone know how to fix that? :) )
Anyway.. there 980meg free for windows, thats enough for what I want..
but.. if I run the MS fdisk it says something like
"hmm, 8.6gig hard drive, 7.4gig used.. that means there um.. 2gig free,
shall I make tha available to windows for you?"
stupid fdisk.. so instead of using that I used linux fdisk, made a windows
partition and installed windows
windows scandisk has decided my drive is set up wrong, and in that DOS
type bit before windows boots i was getting "Sector not found" errors
which i just ignored cuz it was a dos/windows error. but now that ive
installed a bit more on the drive (theres about 50meg free) i cant boot
windows anymore because its files are on the parts of the drive which are
"bad"

I know that the drive is fine, I know that the windows partition isnt
overwriting any others, and it was (and is) definaely formatted as
980meg..so does anyone know whats going on or shall I just delete it and
go back to having an MS free machine again


[BTW - im sorry this is a bit long AND more about windows than anything
else when this is a linux mailing list]
--
Adam
 af7567@bris.ac.uk
 adamf@one2one.net
 adamf@snika.uklinux.net

In article <391B1FAE.EBFE514C@dunvegan1.demon.co.uk>, Paul Richards
(Pauldoo) <pauldoo@dunvegan1.demon.co.uk> writes
>Hi,
>I've came across a weird problem with MS f(uck)disk in that it hangs on
>loading.

You don't say which version... mind you, you mention 98 later on.
>
>I get the prompt about enabling large disk support and I press "y".  The
>screen goes blank and the IDE light goes on and the thing hangs.  OFC
>linux fdisk sees everything as just fine:
>
>Disk /dev/hda: 255 heads, 63 sectors, 1869 cylinders
>Units = cylinders of 16065 * 512 bytes

Ie, 8Gb disk. Again with 98 shouldn't cause a problem.
>
>   Device Boot    Start       End    Blocks   Id  System
>/dev/hda1   *         1       830   6666943+  83  Linux
>/dev/hda2           831      1023   1550272+   b  Win95 FAT32
>/dev/hda3          1024      1869   6795495    5  Extended
>/dev/hda5          1024      1853   6666943+  83  Linux
>/dev/hda6          1854      1869    128488+  82  Linux swap
>
>I'll spend more time tommorrow investigating possible sources of the
>problem but for now does anyone see anything obvious?
>
>The MS bootloader is in the MBR and lilo on hda1 if that matters...
>
A quick discussion of grief I've suffered at the hand of (various)
fdisks ... Used IBM's OS/2 version which put a number ~150 into a signed
byte :-( As a result it refused to modify the partition table any
further, DOS fdisk died on startup, and of several linuxen, the only
fdisk that would actually DO anything was Slack. Of course, now I know
how to use dd to recover from a totally trashed partition table (I
didn't then).

Tried to triple install NT, 95 and linux on a 13Gb. If I created the
partitions with linux fdisk, doze promptly crapped all over it. Ended up
creating the first partition with Doze, at which point linux realised
what Doze had done, and was quite happy being compatible.

As for partitions, on my system...

MBR        lilo
/dev/hda1  NTFS (NT4) (active partition)
/dev/hda2  FAT32 (95)
/dev/hda3  ext2 (linux)
/dev/hda4  extended ...

So I've got it quite happy with multiple primary partitions, and the
first partition is non-FAT... Note that the NT partition *MUST*MUST* be
active. Doze has loads of funny rules about what will and won't work -
and because they interact so much, everyone appears to have a different
set apply to their particular setup :-(

At work, I wanted 98 and W2K to each have their own primary partition...
Install 98 first of course, and then what does W2K do? Creates and
extended partition and shoves itself in there. So the 98 drive is C: and
there's bu**er all I can do about it :-( Totally unofficial ... but if I
get a new hard disk (quite possible) I'll put linux on it and get it the
way I want :-)
-- 
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
Witches are curious by definition and inquisitive by nature. She moved in. "Let 
me through. I'm a nosey person.", she said, employing both elbows.
Maskerade : (c) 1995 Terry Pratchett

On Fri, 12 May 2000 16:06:15 GMT, afx567@bris.ac.uk <afx567@bris.ac.uk> wrote:
>On Thu, 11 May 2000, Andrew McDonald wrote:
>
>> On Thu, 11 May 2000 21:01:34 +0000,
>> Paul Richards (Pauldoo) <pauldoo@dunvegan1.demon.co.uk> wrote:
>> > I've came across a weird problem with MS f(uck)disk in that it hangs on
>> > loading.
>
>Talking about fdisk and windows, I have a problem too :)
>I have an 8.6 gig hard drive, 7gig is taken up by my ext2 usr and root
>partitions, a bit of swap, and then theres some free that I wanted to
>stick windows on so I could play unreal tournament better (linux version
>is dodgy with mouse/keyboard input :( - anyone know how to fix that? :) )
>Anyway.. there 980meg free for windows, thats enough for what I want..
>but.. if I run the MS fdisk it says something like
>"hmm, 8.6gig hard drive, 7.4gig used.. that means there um.. 2gig free,
>shall I make tha available to windows for you?"
>stupid fdisk.. so instead of using that I used linux fdisk, made a windows
>partition and installed windows
>windows scandisk has decided my drive is set up wrong, and in that DOS
>type bit before windows boots i was getting "Sector not found" errors
>which i just ignored cuz it was a dos/windows error. but now that ive
>installed a bit more on the drive (theres about 50meg free) i cant boot
>windows anymore because its files are on the parts of the drive which are
>"bad"

Probably because DOS, like LILO, can't seem to access cylinders above 1024.
Once booted into proper 32-bit Windows, it can see them OK.

At least, that was my explanation for why a Windows package that required a
couple of VXDs from my E: partition failed during boot, when it used to work
from an E: partition on a smaller (<1024 cyls) drive. Once I copied the
package to C: and fixed up the registry, all was well.

And they say Linux is hard to install? At least there are plenty of warnings
in docs and newsgroups about LILO's 1024 cylinder limit... which is fixed in
lilo-21.4.3, BTW...

>I know that the drive is fine, I know that the windows partition isnt
>overwriting any others, and it was (and is) definaely formatted as
>980meg..so does anyone know whats going on or shall I just delete it and
>go back to having an MS free machine again
>
>
>[BTW - im sorry this is a bit long AND more about windows than anything
>else when this is a linux mailing list]
>--
>Adam

Best Regards,
Alex.
-- 
Alex Butcher   Using Linux since '95 - because windows are too easy to break.
Berkshire, UK  URLBLAST:slashdot.org:www.freshmeat.net:www.deja.com:lwn.net:
PGP:0x33489FD3 www.tomshardware.com:www.stardiv.de:www.gimp.org:www.google.com

Alex Butcher wrote:
[snip]
> And they say Linux is hard to install? At least there are plenty of warnings
> in docs and newsgroups about LILO's 1024 cylinder limit... which is fixed in
> lilo-21.4.3, BTW...
[snip]

Remember it only works if your mobo supports it...
-- 
Paul Richards (Pauldoo) - http://www.pauldoo.co.uk

On Thu, 25 May 2000 12:04:55 +0000, Paul Richards (Pauldoo)
  <pauldoo@dunvegan1.demon.co.uk> wrote:
>Alex Butcher wrote:
>[snip]
>> And they say Linux is hard to install? At least there are plenty of warnings
>> in docs and newsgroups about LILO's 1024 cylinder limit... which is fixed in
>> lilo-21.4.3, BTW...
>[snip]
>
>Remember it only works if your mobo supports it...

This is true - you need a post-1998 BIOS to support the enhanced packet
calls it requires.

>-- 
>Paul Richards (Pauldoo) - http://www.pauldoo.co.uk

Best Regards,
Alex.
-- 
Alex Butcher   Using Linux since '95 - because windows are too easy to break.
Berkshire, UK  URLBLAST:slashdot.org:www.freshmeat.net:www.deja.com:lwn.net:
PGP:0x33489FD3 www.tomshardware.com:www.stardiv.de:www.gimp.org:www.google.com