Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Apple Inc. -- Ignore unavailable to you. Want to Upgrade?

To: Dylan who wrote (6622)	12/4/1997 9:36:00 PM
From: Eric Yang	Respond to of 213173

>>G3 printer bug fixed<< ZDnet has an article describing the cause of the printer problem. www5.zdnet.com First case of this happened back in Sept. When Frontier crashed on the 9600/350. It turned out that the programmer had used a short integer (16-bit) to count cycles for determining timing variables. The 350 ran so fast that the 16 bit integer wasn't big enough to hold the number of cycles the 9600/350 can go through and thus causing a overflow. A "long" 32-bit integer should have been used instead. dev.workbook.com The ethernet connection bug noted by Apple a couple days ago is also caused by a timing problem. Apparently the ethernet driver completes the self diagnostics too quickly before the link speed with the hub has a chance to be established. til.info.apple.com These timing problem bugs are just some unfortunate side-effects as new Macs approach ludicrous speed. Eric