Michael C. wrote:

> On Sat, 10 Jan 2004 18:36:28 -0600,
> Steve <samckain@southslope.net> wrote:
>> Lenard wrote:
>>
>> > On Sat, 10 Jan 2004 16:53:46 -0600, Steve typed:
>> >
>> >> Michael C. wrote:
>> >
>> > <snip>
>> >
>> >> Here are the results to fdisk -l /dev/hda:
>> >>
>> >> Device Boot Start End Blocks ID System
>> >
>> >> /dev/hda1 * 1 1704 13687348+ 44
>> >
>> > I hate to tell you this but you have no Windows Me installed, the
>> > partition above is a GoBack partition (ID 44).
>> >
>> > From; http://www.win.tue.nl/~aeb/partition...n_types-1.html
>> >
>> > 44 GoBack partition
>> >
>> > GoBack is a utility that records changes made to the disk, allowing
>> > you to view or go back to some earlier state. It takes over disk
>> > I/O like a Disk Manager would, and stores its logs in its own
>> > partition.
>> >
>> > http://www.symantec.com/goback/
>> >
>> >
>> So WinME is history. I still have access to the files on the Windows
>> drive and can even run some via WINE. It does sound though that
>> formating the partition with windows on it is the only alternative???
>
> If you can still access the windows data from the disk now, I'm
> confused. If you have a non standard setup you've got to
> speak up.

As far as I know I have a standard setup. My newness to Linux may have
caused most of my problems. I don't know why I can access the WinME files
and run some via WINE.

>
> Doing a quick search, it appears GoBack and Linux don't play well
> together. I'd suggest disabling it and unistalling it, remove all
> partitions via fdisk, creating a primary partition only as large as
> needed for Windows, install Windows, then install Linux in the free
> space, letting it set up the multiboot for you.
>
> If you require the use of GoBack, I'd recommend looking into a good back
> up procedure.
>
> Good luck,
>
> Michael C.

If I understand correctly, the only solution left is start over???

Thanks
Steve

Should I use the Linux fdisk or DOS fdisk?

linuxquestion@yahoo.com wrote:

> That's what I understood. My posting addressed how to do that.
> At least it worked on my system.
>
>
> Steve <samckain@southslope.net> wrote in message
> news:<btpnj3$eeq$1@news.netins.net>...
>> Windows ME was the inital install and I would like to get the dual boot
>> to work, ie use GRUB to boot to linux or Windows. Currently GRUB boots to
>> Linux no problem, but windows won't come up, just causes the system to
>> hang.
>>
>> Steve
>>
>> linuxquestion@yahoo.com wrote:
>>
>> > Go to groups.google.com advanced search and lookup my post:
>> >
>> > Dual booting XP, Linux with Grub, on Dell
>> >
>> > This might help.
>> >
>> > Also, I always have two hard drives in my machines. The Windows
>> > stays where it was. Linux goes onto the second hard drive.
>> >
>> > Was Windows the initial installation? And you want to get back
>> > to windows? If so, you can, with your install CD, or emergency floppy,
>> >
>> > fdisk /mbr
>> >
>> > This will overwrite the master boot record. You will be able to get
>> > back to Windows, but will have no more Linux.
>> >
>> > Good luck. Please let us know your solution.
>> >
>> >
>> >
>> > Steve <samckain@southslope.net> wrote in message
>> > news:<btl727$no1$1@news.netins.net>...
>> >> Hello,
>> >>
>> >> I recently installed SuSE 9.0 Professional as what I thought
>> >> would be a
>> >> dual boot system with Windows ME being the other operating system.
>> >> GRUB is used as the loader. SuSE works fine, the problem is Windows.
>> >> If windows is selected the system just hangs. I got the following
>> >> information using fdisk
>> >>
>> >> Partition Status Type Mbytes
>> >> 1 A Non-DOS 13367
>> >> 2 Non-DOS 502
>> >> 3 Non-DOS 5726
>> >>
>> >> I'm guessing that NON-DOS is the reason Windows won't run. Is there a
>> >> way to restore the access to windows or is a complete re-format the
>> >> only option?
>> >>
>> >> Thanks in Advance
>> >> Newbie Steve

Steve wrote:

>>> >> Here are the results to fdisk -l /dev/hda:
>>> >>
>>> >> Device Boot Start End Blocks ID System
>>> >
>>> >> /dev/hda1 * 1 1704 13687348+ 44

> If I understand correctly, the only solution left is start over???

Could you have inadvertently changed the partition type
while running Linux fdisk?
You could at least try changing it to the correct type (with Linux fdisk).
The types can be listed if you start "fdisk /dev/hda" or whatever.

--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

On Sun, 11 Jan 2004 10:43:48 -0600,
Steve <samckain@southslope.net> wrote:
> Should I use the Linux fdisk or DOS fdisk?

While I'm not saying that is the only route, but if you can afford to
start over that's easiest.

Use Dos fdisk.exe, Do NOT partition the whole drive.

Create a Primary partition for windows only as big as you need, and if
you want additional partitions for Dos/Windows, create an extended
partition that spans the remainder of the disk, then create logical
partitions for Dos/Windows keeping in mind you want to leave free space
in the extended partion.

Partition the remaining space (unpartitioned space) using /sbin/fdisk
in Linux, after installing Windows first.

There're other ways, but this is the simplest. If you don't know
EXACTLY what they do, I'd avoid tools that create their own partitions
and modify them unless they specifically say they are compatible with
non-MS systems (unless you are using a windows only machine.)

Michael C.
--
mcsuper5@usol.com http://mcsuper5.freeshell.org/
Registered Linux User #303915 http://counter.li.org/

Hi,

Based on all of the wonderful help and ideas I got with my problem, I
decided to just format out the drive and start over. Everything installed
fine and seems to be working great. My final conclusion is I must have
botched the initial install somehow, creating this problem. Again, thanks to
all that tried to help me with this problem.

Steve
"Michael C." <mcsuper5@usol.com> wrote in message
news:slrnc062li.7oe.mcsuper5@jaguar.softshoppe.com ...
> On Sun, 11 Jan 2004 10:43:48 -0600,
> Steve <samckain@southslope.net> wrote:
> > Should I use the Linux fdisk or DOS fdisk?
>
> While I'm not saying that is the only route, but if you can afford to
> start over that's easiest.
>
> Use Dos fdisk.exe, Do NOT partition the whole drive.
>
> Create a Primary partition for windows only as big as you need, and if
> you want additional partitions for Dos/Windows, create an extended
> partition that spans the remainder of the disk, then create logical
> partitions for Dos/Windows keeping in mind you want to leave free space
> in the extended partion.
>
> Partition the remaining space (unpartitioned space) using /sbin/fdisk
> in Linux, after installing Windows first.
>
> There're other ways, but this is the simplest. If you don't know
> EXACTLY what they do, I'd avoid tools that create their own partitions
> and modify them unless they specifically say they are compatible with
> non-MS systems (unless you are using a windows only machine.)
>
> Michael C.
> --
> mcsuper5@usol.com http://mcsuper5.freeshell.org/
> Registered Linux User #303915 http://counter.li.org/
>
>