Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
But my interest has been piqued:

What is a "slipstreamed disc"?

In Windows there is a way to take your original install disk, and create a new install disk that already includes all of the updated files that you want to put on.

So for example, I may have purchased a windows XP (no service pack) install disk, but could now make a disk that when it installs it is already updated to SP3 and such.

I hope I'm making sense.
 
Interesting,
I keep seeing posts about if Apple should recall the 10.6.0 disks or not.
how about a solution for everyone.

offer an updated install disk for $10.00 or something to current SL owners. Then those worried about it can get the newer disk, and Apple can break even on the materials/shipping.

Not to keep harping on the slipstream idea, but if Apple could come up with an Apple Utility to do this, I'd be pretty excited. Not that it's really hard in Windows, but it certainly can be a bit of a bother. If Apple made a nice Utility for it, I think they could win over some more corporate space, especially if folks could add in 3rd party drivers and such. Even if they charged $20.00 for the utility I'd buy it just for home.
 
It's possible. Apple may want to push it out simply to have something in the headlines to go against the Windows 7 launch. Since there are no 'know issues' listed in the seed notes this release could basically be a final release candidate and if no developer reported any show stopping issues they may just push it out on Thursday. Basically these updates can come out at anytime, I believe one or a few for Leopard even came out on the weekend.
Actually, I think releasing .2 alongside Windows 7 could be a bad thing. You would get all the "10.6.2 broke/bricked XYZ!! :mad: " posts along side the "Windows 7 update broke XYZ!! :mad: " posts.
So annoying when people do this. Do you know something, or are you just guessing? Because it could be anywhere between today and a few weeks from now, just guessing.
 
As long as you don't log in as a guest before you update then you will not experience data loss. Therefore there is no need to recall 10.6.0 media.

I would agree with that as long as they put a big warning sticker on the package.
 
I'm hoping they fix the firewire issues. All of my firewire devices are essentially unusable right now, especially 800 devices. I've found that the problem has had a following since before 10.6.1. Has anyone else here had this problem and/or seen any signs that it will be addressed in 10.6.2?

I have two FW800 and one FW400 hard drives daisy chained to the FW800 port on my iMac8,1. I have no issues what-so-ever. I think you need to be looking somewhere other than OS X 10.6 for your problem.
 
I would agree with that as long as they put a big warning sticker on the package.

No such thing is going to happen and you know it. This issue will fade into the bit bucket along with every other squashed bug. New machines will ship with 10.6.2 eventually. Retail discs will be 10.6.2 or higher eventually. But it will be on Apple's schedule and not because of this bug.
 
I think it's pretty reassuring to know that it's fixed! I also heard a rumour somewhere that these days you can distribute your updates as patches that any user can download with a working internet connection....

Which isn't really any good when you upgrade, and during that upgrade you lose your account because of the Guest Account issue wiping everything.

The reason we need the 10.6.0 discs to be scrapped/recalled and the 10.6.2 ones to be out there is so that bug doesn't exist when upgrading. Doesn't matter if 10.6.2 is available for download, it is useless in this scenario. It is the actual disc that needs to have 10.6.2 on it.

Understand?
 
I have two FW800 and one FW400 hard drives daisy chained to the FW800 port on my iMac8,1. I have no issues what-so-ever. I think you need to be looking somewhere other than OS X 10.6 for your problem.

I think you are wrong. My FireWire drive worked fine under 10.5, half an hour later and an update to 10.6 it was not working. There are plenty of people experiencing the same problem, they are not all seeing it with all their equipment, some just see it on certain bits of kit.
 
I think you are wrong. My FireWire drive worked fine under 10.5, half an hour later and an update to 10.6 it was not working. Thee are plenty of people experiencing the same problem. Not everyone is seeing it with all their equipment, some just see it on certain bits of kit.

Would it be a big deal to read your post after you've typed it?

I'm pretty sure FireWire is FireWire and it's plug-n-play so it should work if it works on other people's machines.
 
So annoying when people do this. Do you know something, or are you just guessing?

Guessing. But on the basis that a) the seeds have been coming quite close together, b) they seem to have resolved all of the major issues intended for this update, c) the mouse doc appears to have assumed it would already be out by now, and d) I don't think it will be late this week because if a major problem did show up immediately after release, Apple won't want to be scrambling out another fix over the weekend (although that could mean it will happen Monday as well as Tuesday).
 
I'm not sure if this will help but I'm running an early 2008 MBP with a WD Firewire drive connected to the FireWire 800 port. I've yet to have problems. I'm wndering how old your FireWire drives are?


Dave

Yeah a lot of people are on both sides of the problem. It does help though because it's allowing me to possibly narrow down the issue with every person that replies. The thing is, I have fw800 capable PCs in the house and these drives do work on those machines. In addition, as I said before, Leopard had no problem with my firewire devices. It's just weird, and maybe it has nothing to do with the OS, but I can't see too many other logical deductions, having tried so many things. I can't imagine the WD My Book Studios to be too old, despite my model being just updated by WD. I have heard about certain firewire bridges being incompatible (currently) with 10.6.2, in which case, it would not be the fault of the OS; however, as you said, there are people with drives from the same company with no problems. It's just one big circle. Hopefully I will find the solution soon. If 10.6.2 doesn't change anything, I will have the drive exchanged. If not that, then I will have my mac checked.
 
Considering that apple updated the 10.5.xx install disk line to later revs, I'm sure that they will update 10.6.xx retail disks (moving forward) with 10.6.2.

Aside from that Apple aways recommends:

1) Backups
2) Backups
3) Did we mention the backups?
4) Clean installs
5) Again, clean installs


I've always done a clean install and restored my data. It takes maybe an hour or so longer, but I know that it's clean and no garbage follows.

For kicks, I tried an upgrade with SL, guess what, there was garbage hiding in all kinds of locations (aside from the fact that I was moving from PPC to Intel at the same time).




I'm running 10.6.1 and I'm a former developer.

My view is somewhere between that of wizard and Amdahl.

I see five possible choices for Apple to take:

a) Continue producing and shipping 10.6.0 disks to retailers.

b) Stop producing 10.6.0 disks and start producing and shipping to retailers 10.6.2 disks. Direct the retailers to continue selling the 10.6.0 disks until stocks run out before selling 10.6.2 disks.

c) Stop producing 10.6.0 disks and start producing and shipping to retailers 10.6.2 disks. Direct the retailers to sell 10.6.0 disks only if they are temporarily out of stock of 10.6.2 (or later) disks.

d) Stop producing 10.6.0 disks and start producing and shipping to retailers 10.6.2 disks. Direct the retailers to send back any unsold 10.6.0 disks after they receive the 10.6.2 disks.

e) Immediately direct retailers to send back all their 10.6.0 disks and tell customers to be patient until 10.6.2 disks become available.

In my opinion, options a) and e) are completely unreasonable.
 
Considering that apple updated the 10.5.xx install disk line to later revs, I'm sure that they will update 10.6.xx retail disks (moving forward) with 10.6.2.

Of course, there were 10.5.0 disks. I recall seeing 10.5.4 retail disks. Were there any other 10.5.x retail disks? Which specifically?
 
The bugs I've logged are in fact regression bugs, and they certainly know about them.

Did they reply to your ticket by a "This is a known bug and the developer team is working on it"

or with a "Please provide more information about this bug"?

If it's the first one, that means it'll be fixed sooner or later. If it's the second one, that means they can't reproduce the bug efficiently so it might be about your Mac rather than a bug.
 
I'm guessing Tuesday as well since they didn't seed the OS X Server build yet. Apple always seeds both versions to ADC for testing before they go public.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.