Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
COBOL and batch processing, may have weighed them down and denied them any technological leaps beyond an exercise in miniaturization. BYTE Magazine, Oct 1986
Yes, I'm actually replying to your sig.

I don't know what Byte was expecting of the IIgs; but there were several technological advances in the IIgs over the ][, ][+, //c and //e, to wit:

1. 80 column video (yes, the //e had 80 columns, but...)

2. Colored Text

3. MUCH enhanced Graphics modes

3. 1 MB RAM (with rev. 3 board)

4. 2.8 MHz 16-bit CPU

5. 32 voice Sampling Synthesizer (Ensoniq "Q-Chip")

6. ADB Mouse and Keyboard port

7. 2 RS-422/232 Serial Ports (with AppleTalk compatibility!)

8. Disk ][ Port

9. DB-9 Joystick Port

10. Composite Video AND Apple Video Output

11. GS/OS

https://en.wikipedia.org/wiki/Apple_IIGS


But, if you want to see a //e as an "exercise in Miniaturization", look at the Apple //e CARD for the Mac LC (and selected Performa models). Now THAT's an exercise in miniaturization!!!

https://en.wikipedia.org/wiki/Apple_IIe_Card
[doublepost=1480962577][/doublepost]
Yes, everything works correctly in both operating systems. For the record, the speakers don't become damaged silently, there's a very loud clicking/popping that happens randomly while booted into Windows when running with the affected speaker driver. You can literally hear the speaker tearing.
[doublepost=1480960797][/doublepost]

I don't believe we lost anything with the updated driver. The issue was a rogue driver bug that would cause a strange popping tone. Driver has been fixed, thus no rogue popping tone. To repeat, the speakers are not blown due to listening to things too loudly - they are blown due to a rogue sound the driver would cause, even when no other sounds were playing.

Cool! Thanks for the clarification!

I figured the "popping" sound was caused by over-excursion of the speakers, due to overpowering. Glad to see it was more like your typical "popping" from bad CODECs, etc.
[doublepost=1480962750][/doublepost]
View attachment 675597
Oh Apple.....this is getting quite comical.
You wanna see the number of recall notices on my 2009 Chev. HHR?
[doublepost=1480963140][/doublepost]
Sorry folks, this is a hardware problem - design flaw in the speakers. At this scale (small size, power) there should be no possible condition where the speakers are physically damaged due to any audio signal, even if the tiny little amplifiers are driven into 100% distortion. The "updated driver" is nothing more than a work-around. Time for another repair program Apple.
Sorry, hater.

It is a SOFTWARE issue, not a "Design Flaw".

The "popping sound" is now gone with the driver update, WITHOUT losing any of the volume output or frequency response.

If you Google "Popping Sound" in Audio Forums, it is a common I/O driver issue with many and varied A/D/A software/hardware. Causes are too technical to go into here; but it was not a "Design Problem" at Apple.

Now, how it slipped through Testing is another matter...
[doublepost=1480963502][/doublepost]
Or the iTunes update that wiped external drives if there was a space in the name because Apple didn't \ escape the string properly.
...Or how you had to go clear back to Snow Leopard and a 2001 version of iTunes to find other examples of a serious bug that made it out the door at Apple?

That's actually a pretty good track record.
[doublepost=1480964079][/doublepost]
Replacing the entire computer to fix a couple of speakers? Me thinks it is something that gets blown on the motherboard. Maybe the bad Windows driver causes a high DC offset that blows an under rated output capacitor?
Wrong.

It is just more CONVENIENT for the CUSTOMER to walk out in 10 minutes with a brand-new laptop than to have to wait for someone to tear-apart the machine, replace the blown speakers, reassemble the machine, update the driver, and test.

Nothing on the logic board (tower computers have Mother Boards, since peripheral cards plug into them. Laptops have Logic Boards, because everything (or nearly so) is integrated onto one PCB) got "blown".
 
I am glad that folks are getting a replacement and fixes came rather promptly, but someone needs to talk to Mr. Cook about more rigorous Quality Control before products are released.
Ya know, it probably didn't come out in the 30 second-test that was warranted to make sure the driver was "working".

Happens. Give it a rest.
[doublepost=1480964591][/doublepost]
Apple is the one bundling the drivers with BootCamp.

It's Apple's job to test the drivers to see if they work properly.
And no doubt they did.

However, they probably didn't do an EXTENDED test. There's a LOT of things on that Test Script, and the boss is breathing down your neck to get it completed. So, the tester(s) no doubt verified that the driver spat sound out, and that it wasn't distorted or otherwise nasty, and as long as the "Pop" didn't happen in that minute or so, on to the next test!
[doublepost=1480964664][/doublepost]
I know how I laughed at Dell when they warned people that VLC could damage their speakers, how crappy their QA was.

Now its Apple...
Difference is, Apple is DOING something about it.
[doublepost=1480964883][/doublepost]
I strongly disagree.

Obviously, I like macOS otherwise I wouldn't be using it.

That said, I find Windows (at least the more recent versions) to be quite decent.
Where can I find the Windows version you are using? I use Windows every day at work, and I wouldn't call ANY version "Quite Decent".
[doublepost=1480965245][/doublepost]
Hi, I get that this is an issue when using BootCamp, but does this mean that this issue could exist if I run windows via virtualisation software such as Fusion or Parallels?
No. That has already been discussed.
[doublepost=1480967180][/doublepost]
How about Apple updates Boot Camp to provide read/write NTS drivers.
How about MS FINALLY releases the Write/Formatting Specs for NTFS?

See section 2.3 in this PDF:

http://dubeyko.com/development/FileSystems/NTFS/ntfsdoc.pdf

And oh, OS X actually DOES have SOME Write capability for NTFS, but it isn't enabled by default:

http://www.techrepublic.com/article/pro-tip-enable-ntfs-write-support-natively-for-os-x/

And there are 3rd Party Solutions:

http://www.techrepublic.com/blog/ap...solutions-for-writing-to-ntfs-drives-in-os-x/
 
Ya know, it probably didn't come out in the 30 second-test that was warranted to make sure the driver was "working".

Happens. Give it a rest.

Nope. Until they seriously up their QC I won't give it a rest; especially as this bug cost some folks their speakers.

I am fine with the occasional lemon, but for the last three years hardware and software have been particularly bad. They had a long time to develop these machines, I expect them to test the blazes out of their product before they release.

Oh wait...
 
Nope. Until they seriously up their QC I won't give it a rest; especially as this bug cost some folks their speakers.

I am fine with the occasional lemon, but for the last three years hardware and software have been particularly bad. They had a long time to develop these machines, I expect them to test the blazes out of their product before they release.

Oh wait...
It has cost "some folks" exactly NOTHING.

1. Driver bug causes blown speaker.

2. Customer returns unit to Apple.

3. Apple replaces at no charge to Customer.

I am at a loss: What "Cost" (other than time and inconvenience) has the Customer incurred?
 
It has cost "some folks" exactly NOTHING.

1. Driver bug causes blown speaker.

2. Customer returns unit to Apple.

3. Apple replaces at no charge to Customer.

I am at a loss: What "Cost" (other than time and inconvenience) has the Customer incurred?

In my case, the store I visited was in a different state with lower tax, so I saved $100 once the transaction was reprocessed (they had a config that matched my BTO model in stock, but not as a service replacement) and I was able to keep the pricey second power brick and cable from the replacement for my troubles.

Net $200 to me for this problem, and all it took was an hour at the Apple Store. I restored from Time Machine backup while I drove home with the notebook in the back seat, and then had Windows back on there within 30 minutes of getting home. Not bad.
 
Last edited:
It has cost "some folks" exactly NOTHING.

1. Driver bug causes blown speaker.

2. Customer returns unit to Apple.

3. Apple replaces at no charge to Customer.

I am at a loss: What "Cost" (other than time and inconvenience) has the Customer incurred?

Wow. Really?

Additional Cost: Time lost on doing work: if this machine is their livelihood they have to scramble until Apple replaces it. Count in gas etc. no matter where they have to drive to.

At any rate, nothing else needs to be said.
 
Wow. Really?

Additional Cost: Time lost on doing work: if this machine is their livelihood they have to scramble until Apple replaces it. Count in gas etc. no matter where they have to drive to.

At any rate, nothing else needs to be said.


It's not a big deal. It was a fairly obscure bug fixed within the first week or so of deliveries. Apple was prompt with the replacement, but to be honest I actually had no idea my speakers were blown as I'm always using an external set of Audioengine A2s or headphones. I read the article and had recalled a strange feedback noise a few days prior while in Windows, and lo and behold my right speaker was blown.

If Apple didn't have my model in stock, I was just going to tell them I'd be back in a couple weeks. It's not a bricked laptop, it's distorted sound quality from built in speakers. In no way does it hinder your ability to do work, and you can get it replaced on your own time.
 
Wow. Really?

Additional Cost: Time lost on doing work: if this machine is their livelihood they have to scramble until Apple replaces it. Count in gas etc. no matter where they have to drive to.

At any rate, nothing else needs to be said.

Quite high on entitlement, not?

Even Boeings and Airbuses fail, okay? It is just a laptop and you are in a country where laws are that way that you are quite protected. On top of that, it is just warranty period still. Quit whining just because you spent some thousand dollars on it. When it is in warranty, what is the problem? Gas? Really? Come to India and then we will talk about cost of gas. ;)

And time lost? Come on. Failures are part of everything and everybody. Machines fail, humans fail. You cannot buy something that does not fail.
 
Quite high on entitlement, not?

Even Boeings and Airbuses fail, okay? It is just a laptop and you are in a country where laws are that way that you are quite protected. On top of that, it is just warranty period still. Quit whining just because you spent some thousand dollars on it. When it is in warranty, what is the problem? Gas? Really? Come to India and then we will talk about cost of gas. ;)

And time lost? Come on. Failures are part of everything and everybody. Machines fail, humans fail. You cannot buy something that does not fail.

:rolleyes:

I know quite well about lemons (two iMacs before my third 2010 were lemons and my 6 / 6s iPhones were all lemons), but the amount of issues on these machines are ridiculous and could be avoided. Including that 3rd 2010 iMac I had almost 14 years of flawless tech from Apple, so that is what I expect when I pay for their product. Since Mavericks, this has not been the case.

I am fine with lemons because that happens; I am not fine with a slew of issues that prove what I have already experienced, the QC is in the toilet.

As far as time, perfect example. I had to cancel two appointments this past Friday because a new Apple floor person screwed up my activation of an iPhone 7+ so royally I was at the store for almost four hours. Two hours, yeah no problem, but almost four: over improper training. And it took the fourth person who helped me to apologize.
Now imagine if that was work hours. I wasn't about to leave without knowing to how fix a brand new phone. :rolleyes:

If they weren't high on hubris right now, I'd be less critical of their hype bs but the fact of the matter is, the last three years have been awful for Apple hardware and software.
 
  • Like
Reactions: macintoshmac
Also, "Microsoft gave its approval" means "Microsoft has checked the driver doesn't crash your computer and stuff works as intended", not "the hardware can't be brought to fail".

I'm sorry, but no, you cannot blame Microsoft for this.

I believe you've missed the point about Microsoft's responsibility that I was trying to make. I'll try to be clearer.

First, for the avoidance of doubt, allow me to repeat that Apple have the primary responsibility for testing their own drivers and hardware. If Apple's hardware breaks because of a driver Apple shipped, no customer is going to let Apple off the hook. Indeed, Apple need to test as if the entire responsibility for testing lies with them, and presumably they do. This much should be obvious.

As someone who earned his living doing software and hardware quality assurance for many years, testing everything from networking protocols to device drivers for genetic sequencers, and even running a few QA departments, I know perfectly well that Microsoft probably never tested the Boot Camp audio driver at all.

As far as I can tell, the "Windows Hardware Quality Labs" don't even exist. WHQL certification appears to be a self-certifying process: Microsoft allow third parties who say that they've followed the specified testing regime to submit their own drivers and hardware to Microsoft to receive the "Windows Hardware Quality Labs" certification (along with the digital signature that allows drivers to be installed in Windows without warnings or restarting in Test Mode).

The very name "Windows Hardware Quality Labs" is more marketing gimmick than engineering reality. Its explicitly stated purpose is to give customers confidence in "high-quality, end-to-end hardware experiences." Now you and I (along with many MacRumors readers) have a lot more expertise and experience than most end-users, and we know to take WHQL certification for what it's worth.

The point is that by certifying third-party hardware and drivers, Microsoft are using their name and reputation to give the average user a degree of assurance that may not be warranted, in order to boost the Windows economy. Microsoft profit from this consumer confidence, so I believe it is only right that Microsoft share some accountability for telling users that third-party hardware and drivers have been certified by their "Windows Hardware Quality Labs."
 
Last edited:
Guys i just want to know if its safe to run win 10 bootcamp now? Are there any precautions i need to take? I have the mbp 15 bto using it for 10 days or so i want to run bootcamp to be able to play some indie games here and there but the speakers issue has really put me off and the lon.tv guy said that the issue is fixed however he isn't going to install bootcamp on his replacement laptop again
 
Just wanted to update....I installed bootcamp last night and it worked no blown speakers or anything of that sort .... Its safe
 
I am loving it...running bootcamp off T3

7815a41c28a0f23dcb63d0779efbc82e.jpg
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.