Well I'm all backed up and it's got "about a minute" left on the upgrade installation. Will need to boot into single user mode before I let it full boot the first time as some tit forgot to remove something that needs removing (no, not unsanity stuff). I did run Disk Utility before the upgrade and it did state volume header needed repair as well as an incorrect number of hard links.
I let it do it's thing which took about 10 mins. I have a feeling some of the delay on first boot might be down to this going on, hence me running DU first.

 

And we're back! There was a 2 min wait on a blue screen on second boot (first boot after install I went straight into single user to remove a few bits), but it came up and I logged in with no problems. Safari seems as snappy as it did in the dev seeds, which is a good thing.

I had held off the beta of Safari 3, even though I knew that some sites Safari 2 did not work with now worked with 3, I thought I'd wait for the final version.

I'm going to run mail in a moment to check out the new features, then I'm going to have a sniff at the bootcamp package as I need to extract the drivers from there as I have been told that when you boot into bc it'll ask you to insert your dvd, which I can't as I don't have 10.5 on DVD.

Looks good so far. I'll be upgrading a few other machines later on, and will try and get server installed as well.

 

Ok, Boot Camp 2.0. With the beta releases I'd been a tad sneaky and rather than burn a CD with the drivers, I'd extract the file from the Boot Camp Assistant package and whack that folder into an area that XP could see, then just run the setup app.

I did the same with 2.0 and found it was still installing 1.4beta drivers and the Boot Camp control panel in XP still reported 1.4 beta.

This is rather poor, you would have thought they could update the disk image file in BCA. I guess that as the correct procedure is to whack in the 10.5 DVD once you have Windows running, that they thought there was no need to update the image in the package. One could argue that they should have removed it then.

As it stands it made for an interesting little experience as I don't have a physical DVD of 10.5, I only have a .dmg file, so I had to convert it to ISO (fire up Disk Utility, use the convert option and select "CD/DVD master" as the type and once it's converted, change the extensions from .cdr to .iso), boot into XP, change the MacDrive settings to show windows files on dual format disks (default is to show Mac files), then use PowerISO to mount the iso file, at which point I could finally run the 2.0 updater.

Oh and iChat Screen Sharing. Well, I still cannot get it to work. Seems to always disconnect the session before starting it. The screen sharing app itself does work, so I know the machines should be capable of doing it, so I'm wondering why it cannot. I've not yet looked at console and system logs, but will do in a little while, as there has to be some reason for it. It will probably turn out to be something I've got set incorrectly on one of the machines

 

Anybody want to swap a Medium T-Shirt for a large?


Had a little play with Leopard in the Apple Store.

Stacks look useful
Spaces looks very useful.
It feels fast (although it would do on Apple Store hardware I suppose)


Read a few comments that it's very slow on the Macbook! Any Comments?

 

Running it on my Macbook and its much faster than Tiger.

 

There will be an initial slowness when you are first logged in as Spotlight will be indexing you disks, so I'm going to take a guess this might be what the person has seen.

 

Cheers

What spec are your running.

I would be installing on original Core Duo/1.83/1gb

 

It was from Macrumours.

More than just a Spotlight thing apparantly.

Think I'll risk it

 

Ok, bonehead here Go iChat Screen Sharing working. Looks like the problem is quite possibly down to the subnet mask. Machine A was using a static IP and subnet of 255.255.255.248, machine B was using DHCP (from my Airport base station) and whose subnet was 255.255.255.0.

Once I'd changed Machine B to use Machine A's subnet it worked. Have to say I'm not overly impressed. I cannot see a way to select which, out of multiple screens of a client I can view, it's all or nothing.

The subnet thing is somewhat worrying as I thought one of the ideas of the feature was to allow an easy method of troubleshooting problems with your friends, and how many of them will be on the same subnet, hell, we used to have two subnets in our small office, so that would break things.

Odd thing is that the screen sharing app itself does not have the problem, so it's a specific restriction of iChat. Perhaps it's to limit it's usefullness so as not to reduce sales of ARD?

 

Safari 3 is unsupported by Natwest's online banking

 

Marcus - When installing, how many minutes did it sit at "About a minute" mines sitting here now and has been for about 10-15....

 

Probably about 5 - 10, which was somewhat laughable to say the least.

 

Yep, mine sat there for ever too, was starting to think i'd have to do a manual restart

 

I did do a manual restart, rebooted, allowed it to 'verify' the DVD, reformatted, reinstalled and it worked...

Glad to see iChat screen sharing works as well as iChat voice has been recently when two machines with completely fresh installs try to connect for the first time. Pants.

 

Ok, iChat screen sharing. I tried it with two people, one over here in Canada, the other in the UK and it worked, so my theory about subnet doesn't hold water

I still have issues with my two machines doing it though, must be some network setting somewhere, but I'm not overly bothered as the screen sharing app itself works, and that's good enough for my internal use.

Oh, one thing to remember when doing the iChat Screen Share, it will allow you to hear and talk to the person you are sharing with. I didn't initially know this and it was a bit odd. Just freaked out my co-worker in the UK by testing the iChat SS feature. He didn't know it did voice, so was a bit perplexed when he could hear me

 

This is one of, if not the MAIN reason I/we bought Leopard, I work with a designer and Timbuktu was OK but this new iChat fits the bill... Just needs to be more reliable that the 10.4 iChat...

 

If you didnt take that oppotunity to call him a gimp or fart loudly, then it was a wasted session

 

His comment of "What the **** is that!" was, I thought, adequate

 

I picked up an English language version here in Japan, all good apart from the loss of my Tiger stripe desktop background, back again thanks to Google.

 

Reminds me, the R2D2 iChat background effect isn't in the GM release, but I *think* it's in the dev seeds, so I might have a poke about for it.

 

still finding a few apps that have not been updated for leopard
but I am sure they will be in the next week or so

FoneLink is one of them

 

SharePoints is another one that doesn't work with 10.5 I think I know why though (netinfo node name has changed between 10.4 and 10.5, and so it cannot connect to the netinfo server and/or find the SharePoints dsrecord) I've posted details on the SP forum as to what I've seen in the logs and why I think it's not working, so hopefully there will be a fix soon.

I *know* there is file sharing in 10.5, but it's a bit all or nothing, as in, you cannot specify, through the GUI, wether a share is only accessible via SMB. If you enable SMB sharing, all existing shares are then shared for SMB.

Another app that isn't working is PureFTPManager, but it said that's being worked on.

I'm also shaking my head at the people who are still moaning about Classic and how you cannot use OS 9 apps at all under 10.5, wether you're PPC or Intel. The only exception I make is for developers who have to maintain OS 9 apps and thus need to run a dev environment via classic. End users have no need to use Classic. Either upgrade the apps you are using to OS X versions, or if there are no OS X versions of the app, find a similar one, or pay a developer to write you a shiny new OS X version of the app.

 

Markus
The file-sharing is an issue as far as corporates, as before we had the choice to connect using AFP (which had its own wealth of issues) or SMB, but put up with the crap that is called long file naming problems and bloody unix files appearing instead of linked files.

and mate, your comment about classic is spot on, aprt from one major bugbear .........and yes you guessed it. Exchange and the abortion that is Entourage. So many of my clients have to have classic running purely to use Outlook 2001 seems crazy know, but the rumours coming from redmond seem to indicate that the latest and greatest version of 2008 still havent addressed the fundamental problem which is mail synching and in particular a true MAPI client. but whoopee do, we get Out of office..blimey I am so glad I waited nearly 4 years for that

 

Am curious about the issues when connecting via AFP. Would this be to a 2000/2003 sever? If so then I'd guess you're still running SFM (Services for Macintosh) in which case, I feel your pain, it's 'orrible. It does not support AFP3 (long file names, DHX, and other nice things). What you want is a copy of GroupLogic's ExtremeZ-IP. It's an alternative to SFM and it does support AF3, and a whole host of other nice things.

Ok, I'll grant another exception with regards to Exchange, as I know people have issues with it.

 

I'm itching to get into Leopard, but stand an icebergs chance in Hell of it working on my ancient G3 PB Still, trying to convince the missuse that I need a shine new iMac Was gonna get a 24" 2.8, but am now thinking of getting a 20" 2.4 and a Mini as a media device into the plasma Was at a mates yesterday and he was running one and it was superb, even from a CS 1.44, let alone a C2D 2.0 which is the minimum spec I'd look at. Only concern now is that Apple are planning an all singing media device to replace ATV and the mini

 

For a bit of a giggle I'm going to try installing 10.5 on my G3 iMac. I don't know the exact spec, but it's well below the requirements Apple sets out. I've put the iMac into Target disk mode and have connected it to my iBook, and I'm running the installer from there.

Now, I doubt the G3 will boot, as there is an explicit G3 check, which is to look for the following value "hw.vectorunit" which will return 0 (zero) for G3's. This checks for Altivect or SSE, which G3's don't need and I'm guessing the core of 10.5 uses this extensively.

I'll report back on my findings.

 

For those of you that have upgraded, it might be worth checking this...

BBC NEWS | Technology | Leopard upgrade hits Mac firewall

 

Ok, the G3 iMac will not run 10.5. It's been sitting at the grey apple logo with the spinning icon for well over three hours (I had let it sit for 30 mins prior to this, upon which I rebooted it). It will happily boot from the other OS versions on the partition.

As for the firewall thing. I've not actually looked at the firewall in 10.5 yet as I tend not to run one and if I do it's Flying Buttress as it's more configurable than Apple's offering, or at least that was the case with 10.4, 10.5 may be different.

 

With regards to the installer hack, have a peek at this hint on macosxhints.

 

'Mikko Hypponen, chief research officer at F-Secure, said: "Year after year, Macs continue to have these potential security problems.
"However, in practice they just don't seem to become real-world problems," he added. "The old wisdom still stands: if you want to avoid viruses and worms, get a Mac." '