Yes I have. I haven't been able to get them to work well....well enough to play. T On Sun, 2004-01-25 at 06:35, Sean Rima wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 25 Jan 2004, Tom Nielsen stated:

...

I went to boot into Windows to play my favorite game....Rainbow Six (the only thing Windows is good for anymore) and when I clicked on

I have no experience of dual booting but I use Quake3 with WIne okay, have you tried this path :)

Sean

- -- GPG Key Id 120A02FB ICQ: 679813 Jabber: tcobone@jabber.org TCOB1.net hosting service now availble -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: This key has an expiry date

iD8DBQFAE9QxXjH8pRIKAvsRAi1LAKCId/7VBoEqqF2o6x0GJ9zG4uOmZgCgy9M+ a8CkphJnMRQLeRmoJaqkGrI= =3iA1 -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25 Jan 2004, Tom Nielsen stated:

Yes I have. I haven't been able to get them to work well....well enough to play.

I haven't played games but do run some MS apps under Wine and have never noticed any major problems, except Quake of course :) Sean - -- GPG Key Id 120A02FB ICQ: 679813 Jabber: tcobone@jabber.org TCOB1.net hosting service now availble -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: This key has an expiry date iD8DBQFAGjmIXjH8pRIKAvsRAoxTAJ4x9HfujUuiNiqpPIxqkfJyHzakYgCeJVaL qEzDAw1ncoVHbrq57wIqSHc= =oQ4I -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 25 January 2004 16:35, Sean Rima wrote:

On 25 Jan 2004, Tom Nielsen stated:

...

I went to boot into Windows to play my favorite game....Rainbow Six (the only thing Windows is good for anymore) and when I clicked on

I have no experience of dual booting but I use Quake3 with WIne okay, have you tried this path :)

Sean

-- GPG Key Id 120A02FB ICQ: 679813 Jabber: tcobone@jabber.org TCOB1.net hosting service now availble

Try the following, before the line with chainloader : map (0x81) (0x80) map (0x80) (0x81) Robert -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQFAE/J1w/Waz1gl18cRAg9nAJ9LcO0TBsEUlJn/x0PGGHaXw71p7wCeM1xJ Q/MQhaDMB/KUJ2RLpdBdNIE= =vCpF -----END PGP SIGNATURE-----

On Sunday 25 January 2004 22.56, Tom Nielsen wrote:

Nope....didn't work.

Can you boot to linux? If you can, what does "fdisk -l /dev/hda" say?

On Sunday 25 January 2004 23.12, Tom Nielsen wrote:

On Sun, 2004-01-25 at 13:58, Anders Johansson wrote:

...

On Sunday 25 January 2004 22.56, Tom Nielsen wrote:

...

Nope....didn't work.

Can you boot to linux? If you can, what does "fdisk -l /dev/hda" say?

Ya, I've got no problems booting into linux. fdisk:

Device Boot Start End Blocks Id System /dev/hda1 1 19765 9961528+ c Win95 FAT32 (LBA) /dev/hda2 19766 20781 512064 82 Linux swap /dev/hda3 20782 41587 10486224 83 Linux /dev/hda4 * 41588 79656 19186776 83 Linux

Ah, I bet you were thinking I didn't have windows installed....did you? I thought that too for a second.

Can you mount hda1 properly from linux? Did you try Hartmut's suggestion to reinstall grub to the master boot record?

On Sunday 25 January 2004 23.20, Tom Nielsen wrote:

...

Did you try Hartmut's suggestion to reinstall grub to the master boot record?

No....I'm scared to. Should I reboot with the rescue CD in or can I do it now while I'm in?

you can do it while logged in

* Tom Nielsen [01-25-04 17:30]:

I'm looking at my boot loader config in yast2. I selected Propose New Config. Nothing changed. I noticed that Activate Boot Loader Partition has NO next to it. Also Replace Code in MBR is Leave Untouched, and Add Saved MBR to Boot Loader Menu is at NO.

I'm going to go ahead and select Propose New Config and save it. But should I change any of the above lines to get it to stick?

If you don't replace the code in the mbr, how are you going to change how it boots? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

On Sunday 25 January 2004 23.30, Tom Nielsen wrote:

I'm looking at my boot loader config in yast2. I selected Propose New Config. Nothing changed. I noticed that Activate Boot Loader Partition has NO next to it. Also Replace Code in MBR is Leave Untouched, and Add Saved MBR to Boot Loader Menu is at NO.

I'm going to go ahead and select Propose New Config and save it. But should I change any of the above lines to get it to stick?

Did you try the method Hartmut suggested?

On Sun, 2004-01-25 at 14:30, Tom Nielsen wrote:

I'm going to go ahead and select Propose New Config and save it. But should I change any of the above lines to get it to stick?

Just rebooted after Proposing a New Config. Couldn't get into Windows. I highlighted windows, hit enter, got a blank screen, then back to grub boot options. The one thing that did change though is that I no longer have my graphical boot screen. It's now basic white text on a black background. How do I get the graphical boot screen back? Tom

On Sun, 2004-01-25 at 15:06, Mike Grello wrote:

On Sunday 25 January 2004 05:50 pm, Tom Nielsen wrote:

...

On Sun, 2004-01-25 at 14:30, Tom Nielsen wrote: Tom,

I work in computer support. so don't take offense. From the time it worked to the time it didn't; what did you change, besides nothing? ;-)

No offense taken. I support windows machines at my office and think the same thing. I don't recall making any changes. I also don't recall booting into windows since I installed 9.0. On 8.2 I did it all the time. So I'm not really sure if it ever worked since I don't recall ever using it. Tom

Ok. Two more things to try/check:

1. Try using Lilo as boot loader instead of grub. YOu can use YaST2 to change this.

==> http://portal.suse.com/sdb/en/2002/12/fhassel_grub_lilo.html

2. Make sure the Windows boot code is fine by reinstalling it (the boot code, not windows)

==> http://portal.suse.com/sdb/en/2002/09/fhassel_deinstall_grub.html

(once checked you can reinstall grub or lilo)

Hartmut, I'll give it a shot when I get home tonight. Thanks! -- Tom Nielsen Neuro Logic Systems 805.389.5435 x18 www.neuro-logic.com

On Sun, 2004-01-25 at 14:18, Patrick Shanahan wrote:

* Tom Nielsen [01-25-04 17:12]:

...

Ah, I bet you were thinking I didn't have windows installed....did you? I thought that too for a second.

That would be a good thing.

Boot from your windoz recovery disk, do a scandisk of 'c' drive. If it appears ok, do 'fdisk /mbr' try to boot windoz

"recovery disk" what's that??? Oh ya. I had one of those once. No idea what happened to it. :-)

if it works, boot from the SUSE install disk, recovery reinstall the grub loader boot linux

if it doesn't work (windoz), smile and have a beer. You are better off.

"Better off"???? No Rainbow Six or Delta Force???? That's a fate worse that death! I tried both on my new playstation2 and can't stand them. PC is sooooooo much better. Tom

On Sunday 25 January 2004 15:35, Sean Rima wrote:

I have no experience of dual booting but I use Quake3 with WIne okay, have you tried this path :)

What on earth are you doing running Quake 3 with Wine?

On Sun, 2004-01-25 at 06:49, Hartmut Meyer wrote:

Hi,

Am Sonntag, 25. Januar 2004 08:15 schrieb Tom Nielsen:

...

I went to boot into Windows to play my favorite game....Rainbow Six (the only thing Windows is good for anymore) and when I clicked on Windows, all that happened was that the screen went black for a second and came back up to my grub boot options. I hit windows again and the same thing happened.

So, I went back to into Suse and checked my boot configuration. I see windows at: Windows other (hd0,0) (/dev/hda1) Everything looks correct. I think. Upon looking at my sections management for windows I see: Section Name Windows Section Type Other -------- root (hd0,0) chainloader +1

I think that's correct. Anyone have any thoughts?

Does that match your setup? Have you changed anything (e.g. added or moved a hard disk)?

If your setup is unchanged and booting Windows via grub has worked before you could simpy reinstall grub into the MBR:

grub < /etc/grub.conf

I haven't tried since I got 9.0. Should I still run that command? Tom

Hi, Am Sonntag, 25. Januar 2004 18:31 schrieb Hartmut Meyer:

Hi,

Am Sonntag, 25. Januar 2004 16:59 schrieb Tom Nielsen:

...

On Sun, 2004-01-25 at 06:49, Hartmut Meyer wrote:

...

If your setup is unchanged and booting Windows via grub has worked before you could simpy reinstall grub into the MBR:

grub < /etc/grub.conf

I haven't tried since I got 9.0. Should I still run that command?

Like I said: *if* your setup is unchanged and booting Windows via grub has worked before ...

Yes.

And maybe I should have added in the first place: there is nothing to worry about - even if you would end up with a non-working bootloader configuration you could always use the SUSE install CD/DVD to boot into the installed system and then use YaST2 to create a new working grub or lilo boot config. Greetings from Bremen hartmut

I had this same problem except that it was SuSE that kept looping back to the GRUB screen. Never did figure out how to fix it. I just reinstalled. So far everything is working great (knock on wood). If you figure it out, I definatly want to know how you fixed it. Russ Hartmut Meyer wrote:

Hi,

Am Sonntag, 25. Januar 2004 08:15 schrieb Tom Nielsen:

...

I went to boot into Windows to play my favorite game....Rainbow Six (the only thing Windows is good for anymore) and when I clicked on Windows, all that happened was that the screen went black for a second and came back up to my grub boot options. I hit windows again and the same thing happened.

So, I went back to into Suse and checked my boot configuration. I see windows at: Windows other (hd0,0) (/dev/hda1) Everything looks correct. I think. Upon looking at my sections management for windows I see: Section Name Windows Section Type Other -------- root (hd0,0) chainloader +1

I think that's correct. Anyone have any thoughts?

Does that match your setup? Have you changed anything (e.g. added or moved a hard disk)?

If your setup is unchanged and booting Windows via grub has worked before you could simpy reinstall grub into the MBR:

grub < /etc/grub.conf

Greetings from Bremen hartmut

Hi Tom, Here is a copy of my menu below. I have 2 HD's. I tried several different configurations and the more I tinkered then the problem of the loop boot would surface. I currently have it set up this way: 160 gig 100 XP 30 FAT32 30 FAT32 80 gig 1 Linux swap 79 SuSE The Loop boot problem popped up with this exact setup. I simply reinstalled SuSE and it works great now. Russ # Modified by YaST2. Last modification on Sun Jan 25 14:02:59 2004 color white/blue black/light-gray default 1 timeout 8 gfxmenu (hd1,4)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title SuSE kernel (hd1,4)/boot/vmlinuz root=/dev/hdb5 vga=0x317 splash=silent desktop hdd=ide-scsi hddlun=0 showopts initrd (hd1,4)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title WindowsXP root (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy root (fd0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe kernel (hd1,4)/boot/vmlinuz root=/dev/hdb5 showopts ide=nodma apm=off acpi=off vga=normal nosmp noapic maxcpus=0 3 initrd (hd1,4)/boot/initrd ###Don't change this comment - YaST2 identifier: Original name: Memory Test### title Memory Test kernel (hd1,4)/boot/memtest.bin Tom Nielsen wrote:

On Sun, 2004-01-25 at 08:11, Russ wrote:

...

I had this same problem except that it was SuSE that kept looping back to the GRUB screen. Never did figure out how to fix it. I just reinstalled. So far everything is working great (knock on wood). If you figure it out, I definatly want to know how you fixed it.

Russ

Hartmut Meyer wrote:

...

Hi,

Am Sonntag, 25. Januar 2004 08:15 schrieb Tom Nielsen:

...

I went to boot into Windows to play my favorite game....Rainbow Six (the only thing Windows is good for anymore) and when I clicked on Windows, all that happened was that the screen went black for a second and came back up to my grub boot options. I hit windows again and the same thing happened.

So, I went back to into Suse and checked my boot configuration. I see windows at: Windows other (hd0,0) (/dev/hda1) Everything looks correct. I think. Upon looking at my sections management for windows I see: Section Name Windows Section Type Other -------- root (hd0,0) chainloader +1

I think that's correct. Anyone have any thoughts?

Does that match your setup? Have you changed anything (e.g. added or moved a hard disk)?

If your setup is unchanged and booting Windows via grub has worked before you could simpy reinstall grub into the MBR:

grub < /etc/grub.conf

Greetings from Bremen hartmut

What does your windows boot option say in grub??

Tom

* Tom Nielsen [01-25-04 17:14]:

On Sun, 2004-01-25 at 14:10, Russ wrote:

...

Hi Tom, ... Ah, nuts! Same as mine.

and please, guys, trim your quotes. All the repeating is not necessary and boring. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org