Jump to content

stevemar

stevemar

Member Since 06 Nov 2008
Offline Last Active Dec 21 2008 12:38 PM
-----

Posts I've Made

In Topic: M-Audio Firewire Solo issues

21 November 2008 - 07:38 AM

Its been a couple of months :D

I ve been doing a lot of searching on this. It seems as though there is no solution to the firebox not being detected by ones onboard 1394 port. Is this confirmed?

I am running a retail 10.5.4 leopard & interestingly, when i plug my firebox onto the onboard VIA firewire port ( VT6308P - P5E mobo), the light turns blue as though its happy as larry. In system preferences --> network however, there is no green orb.

I ve got another 3 port firewire PCI card which is recognised in network, but returns the same "not connected' message.

What is the expected source of this problem?

In Topic: DAW - based on GA-EP45 incl. hardware list

20 November 2008 - 02:36 AM

retail=working

=D

In Topic: DAW - based on GA-EP45 incl. hardware list

19 November 2008 - 08:47 AM

Well i most definately agree with Peach. I want to be running my logic with minimal problems. So...

I went out and bought the retail 10.5.4 Leopard today.

I changed the bios settings so that MacHD was the first hard drive to boot off & followed the guide exactly until I came to the famous 'b0 error'. After sucessfully completing both options at the osx86 site:

http://wiki.osx86pro...ex.php/B0_error

i have come to a black screen with a paging white "-" symbol.

Anyone came accross this before?

There is no more b0 error but it is as if the computer cant find the right trigger files on the HD to load MacHD. I say this because after about 34 minutes its still stuck at that black screen with the on/off "-".

Retail Leopard wont install onto MBR

In Topic: DAW - based on GA-EP45 incl. hardware list

18 November 2008 - 01:53 PM

Thanks peach. Its all making more sense now.

i did not boot to MacHD. Usually i hit F8 and then see what i can boot too - this didnt show the Mac HD partition but i havent tried F12 yet....

I ve been looking at installing the kaly 10.5.2 from the LeoX install by using osxinstall.mpkg. I found the file in the kaly cd under /volumes/kaly ...etc/system/installation/packages

The result was a problem with UUIDs and as a result i installed smbiosresolver.kext. Then upon executing osxinstall.mpkg from the kaly cd, i noticed that it wouldnt let me select the destination MacHD. Instead the installer would skip that step and tell me it was installing it to leoX.

Now i checked out this post and realised that i can edit the osxinstall.mpkg file:
http://forum.insanel...o...16505&st=20

But thats for an iso file (the kaly dvd is read only) which is all good if i burn another dvd i guess. Im not sure whether there is another way to be able to choose my install destination when executing osxinstall.mpkg from LeoX.

If there isnt, ill run the kaly cd from boot and install it to MacHD and then try this F12 thing to boot into MacHD.

In Topic: DAW - based on GA-EP45 incl. hardware list

18 November 2008 - 08:04 AM

if you follow the guide 100% there shouldnt be any issues. ... shouldnt be any problem to install also kaly this way - this problem appears only if you didnt select the right destination to install to(to MacHD in this case).


I had to reset to install kalyway 10.5.2. The install was sucessful and upon restart i booted into my LeoX install. However, after running the osx86tools fdisk and efi instructions, and then reseting, there was no option to boot into MacHD. In fact, i couldnt see the MacHD install at startup . When i am running off LeoX i can clearly see the HD and all relevant installed files for OSX).

One thing i noticed after executing fdisk is that in osx86 tools it says

chmod 775 /Users/Steve/Desktop/OSX86Tools.app/Contents/Resources/FDISKEFI.app/Contents/Resources/fdisk
echo 'f 2\nu\nw\ny\nq\n'| /Users/Steve/Desktop/OSX86Tools.app/Contents/Resources/FDISKEFI.app/Contents/Resources/fdisk -e /dev/disk1
Enter 'help' for information
fdisk: 1> Partition 2 marked active.
fdisk:*1> Machine code updated.
fdisk:*1> Writing MBR at offset 0.
fdisk: 1> Invalid command 'y'. Try 'help'.
fdisk: 1>
[/i]
FDISK completed."[/i]

Should this command be copied and entered into terminal manually with replacing the y for its appropriate value.. ?
© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy