OnMac.net: Windows XP on Intel Macs

Go Back   OnMac.net Forums > Alternative OSes on Apple Hardware > XOM - The open source solution > Troubleshooting
 
 
  #41  
Old 19th March 2006, 02:06 AM
jerbare jerbare is offline
The Quiet Type
 
Join Date: Mar 2006
Posts: 16
Default

iMac 20" (250GB) - and I am at a standstill after the installation partition/format/filecopy section due to what I am guessing is a 'non-standard' partition layout...

My disk is partitioned in to four slices: EFI, Mac OS X, Windows and Linux.

I am using rEFIt to keep an eye on xom.efi's console output.

For some reason the mbrUpdate routine in xom.efi keeps replacing the wrong partition information. Even if I manually fdisk the drive and set the Windows partition to either 0x0B (FAT32) or 0x07 (NTFS) it still seems to write it as MSDOS.

After the first install cycle (file copy, restart), I see 'Disk Error Press any key to restart' in the framebuffer output. I am guessing it has to do with the MBR partition ID's not being right, and/or the format (FAT32 vs NTFS)...

Are these known issues? Are they correctable? I would very much like to 'disable' the mbrUpdate routing in xom.efi if I could since it irreversably changes the MBR to something I do not want. It makes it a huge pain to have to boot in to the Mac OS X Installer and 'dd' my proper legacy MBR over.

Last edited by jerbare : 19th March 2006 at 02:17 AM.
  #42  
Old 19th March 2006, 02:12 AM
torifile torifile is offline
The Quiet Type
 
Join Date: Mar 2006
Posts: 12
Default

I think I must have done something wrong somewhere along the way. I've formatted my drive into 3 parts: XP, OSX and a swap space (not "swap" in the usual sense, just a place I was planning on using to move files back and forth between my OSes). I formatted the XP partition as MSDOS. When I got to the first blue screen, I didn't get anything about a file format to use. Only an option to install. I went ahead and installed and I thought things were going well, but after it went to reboot, I got "disc error". Windows is installed (or at least taking space) on that drive because I can see the files on it through OS X. Any ideas?

This is a 20" iMac, 250gig hard drive. XP Partition (first, MSDOS): 40 gigs, OS X (second, HFS+) 187 gigs, Swap (third MSDOS) 5 gigs.
  #43  
Old 19th March 2006, 02:26 AM
jerbare jerbare is offline
The Quiet Type
 
Join Date: Mar 2006
Posts: 16
Default

Quote:
Originally Posted by torifile
I went ahead and installed and I thought things were going well, but after it went to reboot, I got "disc error". Windows is installed (or at least taking space) on that drive because I can see the files on it through OS X. Any ideas?

This is a 20" iMac, 250gig hard drive. XP Partition (first, MSDOS): 40 gigs, OS X (second, HFS+) 187 gigs, Swap (third MSDOS) 5 gigs.
Exact same problem I am seeing (and as I posted above).

My guess is that it has to do with:
1. Partition Ordering (Mac/HFS before Windows/FAT|NTFS), or
2. Partition Number (More than just Mac/Win)...

Or possibly a combination of both...
  #44  
Old 19th March 2006, 04:39 AM
Steve1496's Avatar
Steve1496 Steve1496 is offline
Super Moderator
 
Join Date: Feb 2006
Location: Braintree, MA
Posts: 271
Default

20" iMac users looking for a bluetooth solution:
Try using hid2hci.exe 06ac 1000 instead.
  #45  
Old 19th March 2006, 11:04 AM
xjmaas xjmaas is offline
The Quiet Type
 
Join Date: Mar 2006
Posts: 9
Default Working...

Finally I got it working, some directions in the thread I mentioned earlier helped me....

Xander
  #46  
Old 19th March 2006, 11:05 AM
nwSimon nwSimon is offline
The Quiet Type
 
Join Date: Mar 2006
Posts: 13
Default

Hi Steve

Just wanted to confirm I got bluetooth working on the 20", after I modded my bth.inf file with the following:

In the manufacturer section, add:

Apple=Apple, NT.5.1

In the Devices section, add:

[Apple.NT.5.1]
Apple Bluetooth Radio= BthUsb, USB\Vid_05ac&Pid_8206

Then I ran from the command prompt your command: hid2hci.exe 06ac 1000

Nothing appeared to happen so I ran hid2hci.exe 05ac 1000

Then Windows detected everything and it's working perfectly!

Thanks
  #47  
Old 19th March 2006, 03:42 PM
torifile torifile is offline
The Quiet Type
 
Join Date: Mar 2006
Posts: 12
Default

Quote:
Originally Posted by jerbare
Exact same problem I am seeing (and as I posted above).

My guess is that it has to do with:
1. Partition Ordering (Mac/HFS before Windows/FAT|NTFS), or
2. Partition Number (More than just Mac/Win)...

Or possibly a combination of both...
I'm certain that it's not #1 because I made sure to put the windows partition first. The symptom of this problem is that the windows installer doesn't ask what format you want for that partition. I don't think it has anything to do with the mbr, honestly.

I created a qemu drive from this installation and I got the same error upon boot up. Whatever format is on the drive isn't working. What if I repartition and give that drive a format that windows will HAVE to format, like HFS or UNIX? I'll give it a try.
  #48  
Old 19th March 2006, 04:13 PM
ampmhoodlum ampmhoodlum is offline
Should be dual-booting by now.
 
Join Date: Mar 2006
Posts: 40
Default

Got the bluetooth working. yay
  #49  
Old 19th March 2006, 04:31 PM
Steve1496's Avatar
Steve1496 Steve1496 is offline
Super Moderator
 
Join Date: Feb 2006
Location: Braintree, MA
Posts: 271
Default

http://wiki.onmac.net/index.php/Wind...ITH_DRIVERS%21


Who's brave enough to try it? It could fix the problem with video, as video drivers are hardcoded to the registry, and this would make those drivers ATI's catalyst.

Now, when you download, you'll get some ridiculous download message about 130 people before you (of course after you've finished guessing a million times what the code says).
  #50  
Old 19th March 2006, 05:11 PM
compufix compufix is offline
Dual-boot Guru
 
Join Date: Mar 2006
Location: Philadelphia
Posts: 110
Default

I will try it as soon as I get a d/l slot. I am 121 waiting.

I also have BT working on teh 20" using the wildcomm drivers from anycom. Modifying the number 8205 in the directions to 8206.

FOr some reason I also have an unrecognized device with the same ID but 8300. If I try to activate that one, It works but I now get a bluetooth device with an error.

Now that I have the process down...the whole F4, F7 thing, re-install will be a breeze. Let me at it.
 


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:49 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.