Support and General Use > Hardware

Gigabeat F60 System Error 00000003

<< < (2/3) > >>

GodEater:
Good god sorry - I must have been completely asleep when I posted that.

No you're right - there is no fdisk command in XP. I was thinking of chkdsk for some reason.

The fdisk equivalent in XP is "Disk Administrator". Right click on the "My Computer" icon on your desktop, choose "Manage", and then launch Disk Administrator from there (with your Gigabeat attached). You should be able to use that to work out if there's still a partition on your player.

scharkalvin:
And I was thinking Linux of course.

Nate!:
Whew, I know I've been out of the systems game for a while, but I thought I was going crazy.  I remembered the util, just couldn't find it.

So in looking at disk manager, there is one partition that appears to be "Healthy" and Fat32.

scharkalvin:
Gigabeats have but one partition, takes up the whole disk.
You might have a corrupt boot sector (first sector of the only partition)
or a bad MBR (assuming that the gigabeat boot loader actually uses either of these bootstrap records.  Most disk based system use one or both of these).

NOTE: MBR (master boot record) is the first sector on the disk and is the first 446 bytes of the sector.  The remainder of this sector is the partition table (which lists the starting sector and length in sectors of each of up to 4 partitions.  Disks that have more than 4 partitions usually assign one of the first 4 partitions as an extended partition table).  

Nate!:
Is there any way in a windows xp world to identify if either of the suggested issues are the case and are there fixes?

Navigation

[0] Message Index

[#] Next page

[*] Previous page