VST Expansion Bay HD intermittently seen by osx.3 (kanga)

Kanga 160 ram/ 40 gig / VST expansion bay HD (no OS) / OSX.3/9.1
Expansion bay will disapear & be unusable from osx desktop.
Once disapeared, Apple hd utility cannot remount either.
Other times it is usable from the desktop for a long time then disapears...
reboot fixes it until it disappears.
Expansion bay checks out aok under 9.1/norton...
What's up?

BVD,
All I can suggest is the same procedure that seems to work on the later model black G3s, and that is to download and perform a deep cache cleaning. The freeware OnyX or Yasu will do the job nicely.
http://www.versiontracker.com/dyn/moreinfo/macosx/21674
http://www.titanium.free.fr/pgs/english.html

Similar Messages

VST expansion bay Zip drive fails in my Wallstreet

Would really appreciate some help solving this problem.
G3 Wallstreet is: 266MHz, 256 MB RAM, 4 GB HD, 14" screen.
OS is 9.2.2
This PB functions well with wireless and all apps including DVD player. Apple floppy drive works just fine in the right bay.
However, I cannot get the VST zip drive to work. Have tried both the original VST CD that came with the zip disk drive and a file downloaded from Version Tracker (labeled IomegaWare English 8.6 - 9.X). Both seem to load correctly and put a file in the Control Strip, Control Panels and Extensions. Yet, when I insert the zip drive the PB locks up except that I can move the cursor (cannot open files or open menus).
Suggestions appreciated.
BTW, I also cannot install Acrobat Reader vs. 5. Starts to download the needed files and then hangs.

Hi,
Tnx for your response to my request for help.
Unable to find the extension "Findit".
I am using the Iomega software downloaded from VersionTracker, not the files on the VST CD which came with the drive.
Followed your suggestion regarding only a single Iomega extension. So dumped Iomega firewire support, Iomega USB support and Iomega active disk engine. Retained the extension Iomega driver (84k file). Seemed logical.
Kept Iomega drive options control panel and the control strip file. Did restart.
RESULT: when VST drive inserted into the right bay totally froze PB until removed. When removed all is normal.
Next, removed all remaining Iomega files. Restart PB with VST drive inserted.
Able to use mouse to open folders and menus. But of course the VST drive is unable to load any zip disks. It is just a space filler.
Next reloaded all the Iomega files with the zip drive inserted into the right bay. BINGO! It worked normally and I was able to read zip disks.
But when I removed and reinserted the VST zip drive it returned to previous behavior and I was locked out of doing anything except just being able to move the cursor. And the Powerbook won't boot with the zip drive in the bay.
In fact it won't boot with the drive out unless I remove all power. Does this suggest the problem is not an extension conflict since no extension were loaded. Yet extensions must be a problem since when I removed all the Iomega files there was no problem booting.
Your thoughts appreciated.
Let's hold off on Acrobat Reader until the VST issue solved.
Robert
Mini 1.5 GHz/SD/GB RAM/Green House speakers Mac OS X (10.4.5)

Expansion bay problem

After installing Panther on my G3 Powerbook, the VST CD drive in my expansion bay - which had been operating perfectly prior to OSX - would seldom recognize CDs, though the VST Zip drive operated as usual. After updating to OS 10.3.5, neither the CD or Zip drives would recognize their media. This seem suspiciously like a driver (software) problem rather than a hardware failure. I don't think VST still supports this equipment, so I hope someone out there has some ideas.
Thanks for your input.
G3 Powerbook Mac OS X (10.3.5) Expansion bay has ZIP and CD drives

elsid14,
There have been a few complaints about media bay drives having problems with various versions of OSX. I have read that the VST Zip100 works fine at least up through 10.3.9; however I cannot recall anything on the VST CD-ROM.
However, problems that users were having usually were corrected by flushing all of the caches; I use the freeware Yasu and there are others like OnyX. There are many functions that OnyX can perform...just stay with the cache cleaning. You want version 1.5.3 for 10.3.x.
http://www.versiontracker.com/dyn/moreinfo/macosx/20070

5770 and 5870 in Mac Pro 2009 - noisy PCIe expansion bay fan

I replaced the Geforce GT120 by the ATI radeon 5770 in my Mac Pro Quad 2.66 Nehalem. I had severe trouble with the speed of the fan of the PCI-e expansion bay: 2000 RPM and really noisy. After 30-60 minutes it slowed down and became silent, but upon reboot the noise and the high speed were there again.
I have sent the 5770 back to Apple. I am considering to try the 5870, but I am afraid I will be in trouble again.
With the GT 120, the fan speed is only 800 RPM and the Mac is silent. The ATI Radeon cards require one or two power cables connecting to the logic board.
Could that be the cause of the problems or was the 5770 a bad card? Or is it the logic board. I ran the Apple Hardware Test. everything was OK.
I checked it with Techtool Pro and there were no problems found.
Any help would be much appreciated. I have zapped the PRAM and reset the SMC without result.
Kind regards and thanks of reading.

If it is any consolation I have the same machine and installed the Radeon 5770 and have intermittent high expansion bay fan speeds (1400-2400rpm). I just checked this board today because it seems more noisy today than in a while and the ambient air is listed as 78 degrees F. The card has it's own fan and exhaust slots in the back of the card and the air from them is warm but not what I would consider hot. I had had two video cards and a eSATA card installed and never had a problem. Now with just this card and the eSATA it exists. I'm betting if I call Apple about it they will tell me it's only listed on their site as compatible with the 2010 Mac Pros, so, for now I will live with it.

DVD Drive Module on Pismo sticks out of expansion bay. Any way to fix?

I just picked up a Pismo the other day and found a DVD drive for it on ebay, which works perfectly, but the drive sticks out of the expansion bay a little unless I put some pressure on the bottom or the top of the computer. Of course, when I release pressure, the drive pops out a little again. Should i be worried about this at all, or is it just cosmetic? Is this a common problem? Any help would be appreciated. Thanks.

soul,
It sounds like the little plastic tab on the release mechanism inside the frame is worn and is not holding the drive as far in the bay as it should, or the recess on the optical drive may be worn. If you remove the optical drive, you will see a small rectangular recess on the edge of the drive that engages a small tab on the lever. Look into the empty bay with a flashlight and you will see the tab and how the mechanism works.
Here is a picture of the recess (top picture) on the drive:
http://www.ifixit.com/Guide/Mac/PowerBook-G3-Pismo/Optical-Drive/6/22/Page-1/Opt ical-Drive
You cannot replace the levers, if necessary, without considerable disassembly of the 'book. Possibly you can improvise a thin spacer for the recess on the drive.

Expansion bay fan too fast/loud

My dual 2.7 G5 has recently developed a problem with the expansion bay fan. As soon as the boot process has reached a certain point the fan goes to about 90% speed and stays there.
Resetting PRAM, SMU, repairing permissions, updating the system (10.4.8 all updates installed), nothing helped.
TechTool Deluxe shows no problem.
Hardwaremonitor 4.0 shows 89-90% fan speed for the PCI Expansion bay. But there is only the graphics board installed and I did not change anything about the configuration since I bought the machine. Hardwaremonitor shows about 58000 for the power use in the expansion bay (whatever unit it may use here...). Is that a normal figure?
Everything else is just fine, but as soon as the system starts running it decides to drive the fan to that uncomfortable speed while a few weeks ago the whole Mac was barely making any noise at all.

Hi Guido, and a Warm Welcome to the Power Mac G5 Forum!
Assuming that you have made a visual (and aural (!)) check that it is definitely the fan at the front of the G5, in a combined housing with the puny internal speaker, that is making all the noise -
The units for "Slot combined" (as it's called on this venerable G5 DP2 running HM v. 4.1) are mentioned in the HM Help FAQ
"Why do the power sensors of the Power Mac G5 slots not carry a unit?
At this time we don't have enough data about these sensors. For this reason it is unknown in which unit the readings have to be interpreted. The readings could, for example, be interpreted as milliwatts. The sensors Slot 12V, Slot 3.3V and Slot 5V show the power load drawn by PCI cards for the respective voltages. The sensor Slot combined also includes the current power load by the SATA hard disks."
The "Slot combined" on this G5 DP2 with an X800XT is reading 23563.0; note that, according to the quote above, this also includes power to the hard drives.
This "PCI Slot Fan" is currently showing 35%.
For comparison, there are some fairly, er, not-very-recent, HM readings here
http://macosg.com/group/viewtopic.php?t=1314&start=0
As you have already run TechTool
https://support.apple.com/techtooldeluxe/main?id=dl
You could try the Apple Hardware Test
http://www.thexlab.com/faqs/aht.html
Sometimes re-installing the combo updater fixes this type of problem
http://www.apple.com/support/downloads/macosx1048comboupdateppc.html
Other than that, you could try calling AppleCare.
However, investigations are ongoing...

Pismo, OSC 10.3.9, VST Media Bay superdrive sees but won't mount 1.4mb flop

This worked a while back, likely earlier version of X, just tried it and it sees but won't mount or format a floppy that works fine in a Mac Mini (10.4.11 with a Teac external floppy drive)
About to travel, would rather take the Pismo with the VST drive in the 2nd bay --anyone recognize this problem?
Here's what the Profile sees:
Name :
S,1 0 S
I
4 0 H l,p y
Type : Disk
Disk Identifier : disk1
Media Name : M L Media
Media Type : Generic
Connection Bus : ATAPI
Connection ID : Device 0
Device Tree : mac-io/media-bay@34/ata-3@20000/@0:0
Writable : Yes
Ejectable : Yes
Mac OS 9 Drivers Installed : No
Location : Internal
Total Capacity : 1.4 MB (1,464,832 Bytes)
Disk Number : 1
Partition Number : 0

Ok, using Yasu to flush all the caches, nothing else, and rebooting
-- did work for the VST ZIP module, which works, mounts a ZIP disk ok.
-- did not work for the HS-120 VST floppy module, but it's different.
Before it did not detect a floppy, just showed up on System Profiler as the drive being present.
Now, Disk Utility did detect a floppy as soon as I inserted one (as unreadable, though it's a Mac-formatted HD floppy; OSX (10.3.9) offered to format it). I tried letting it be formatted, it made all the right noises, but nothing changed. "Mount" is not an option. Tried DOS, no difference.
Well, one working VST module out of two isn't half bad in this case; I can stand traveling with an external USB floppy, they're small enough, and it's very handy to be able to use the VST ZIP where hauling around an old ZIP drive would be, in today's terms, just too much. But for a few extra backups, it's good to have.
Thanks! And I'll check back between trips in case anyone has other suggestions over time.

IPod touch: Seen by XP, not seen on OSX.

Strange one.
1st Gen ipod Touch with latest software(think its 3.3), latest version of itunes.
Its seen and works perfect with Windows XP.
I plug it into my Mac Book Pro, running Lion and its not seen. nothing happens wihen i plug it in.
I have reset, restored and wiped the ipod from the device itself and its still not seen.
I also tried it on a Win 7 machine and its NOT seen either.
Is this something crazy to do with 32bit architecture. Its seen on Win XP which is 32 but not by 64bit Lion and Win 7.
Any suggestions?

Have a Look Here
Device Not Recognised
For PC
http://support.apple.com/kb/TS1538
For Mac
http://support.apple.com/kb/ts1591

HP desktop m9077c - access to expansion bay to add a hard drive

Hello friends,
I am trying to add a new hard drive in to the open hard drive bay . I am struggling to get access to the bay. Can some body mail me or give me pointersto info on how to open this desk top? I was able to open ip the side panel and found the power/data connectors for my SATA drive!
Is there a way to remove the front panel - which may give better access?
thanks for any help!
-malone
Message Edited by malone on 11-05-2009 10:01 AM

Here is the Service Manual:
Manual
There can only be one ordinary 2.5 inch hard drive and it is a bear to get to. Trying to do so will void the warranty. You have to remove the top cover. This series of video clips is even better than the Manual to show you what all is involved:
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&dlc=en&docname=c04339451&lc=en&jumpid=reg_r1002_us...
The "second" hard drive is an M.2 mSATA drive and it is even harder to get to. It is on the motherboard so the motherboard has to be removed to access the slot.
See pages 71-72 and page 66.
You do not need a caddy or anything to install the M.2 mSATA drive. It plugs in the slot and is held down with a single screw.
They look something like this....the three "prongs" are critical but they come in different lengths:
The M.2 mSATA mSSDs are the fastest type of storage on the market. The new "trash can" Mac Pro uses them. They tend to run a trifle on the pricey side and are not yet widely available but getting better.
If this is "the Answer" please click "Accept as Solution" to help others find it.

Ever seen stub.osx process

A process I have not noticed before is using much of my processor power, about 60%. Wouldn't mind if I knew what it was doing.
Any one know what the stub.osx process does?
It's parent is WindowServer (75), whose parent is launchd (1) whose parent is kernel task (0)
Below is a sample if that helps anyone tell me what it is doing.
Thanks
2007-09-04 13:25:02.736 sample[2255] Waiting 20 msecs for System framework to be loaded...
2007-09-04 13:25:02.759 sample[2255] Waiting 40 msecs for System framework to be loaded...
2007-09-04 13:25:02.868 sample[2255] Waiting 80 msecs for System framework to be loaded...
2007-09-04 13:25:02.956 sample[2255] Waiting 160 msecs for System framework to be loaded...
2007-09-04 13:25:03.133 sample[2255] Waiting 320 msecs for System framework to be loaded...
2007-09-04 13:25:03.454 sample[2255] Waiting 640 msecs for System framework to be loaded...
2007-09-04 13:25:04.095 sample[2255] Waiting 1280 msecs for System framework to be loaded...
2007-09-04 13:25:05.375 sample[2255] Waiting 2560 msecs for System framework to be loaded...
2007-09-04 13:25:07.936 sample[2255] * Process unreadable: 1
Analysis of sampling pid 1027 every 10.000000 milliseconds
Call graph:
90 Thread_0f03
90 start
90 _start
90 main
90 CCFM_LaunchApplication
90 0xf5d4c
49 0x70aa8c
49 0x70af0c
40 0x772650
40 FindWindow
40 0x2304818
40 FindWindowCommon(Point, OpaqueWindowPtr**, short*)
24 MBarHit
23 0x2304acc
23 0x22b1908
23 0x3491e5c
23 CPSGetProcessesInFrontToBackOrder
19 _CGSGetProcessesInFrontToBackOrder
19 0x110e348
19 0x110e348
4 0x1125778
4 0x110e348
4 0x110e348
1 0x2304ab0
1 0x22b2928
1 0x22b2928
15 0x23199bc
15 CGSFindWindowAndOwner
15 0x2ebdfa0
15 0x110e348
15 0x110e348
1 0x339f8f0
1 0x339f924
1 std::set_unexpected(void (*)())
1 std::set_unexpected(void (*)())
9 0x772638
9 0x77307c
9 0x70afa0
9 0x705c34
9 0x706eec
7 0x4b1bf48
7 0x4b76b80
5 0x4b6ff94
3 0x4b1ac54
3 0x4b75ef8
1 0x4b78f84
1 0x4b791f0
1 0x4b79dd4
1 0x4b79f64
1 0x4b555ec
1 0x4bec7e4
1 0x4bfa5ec
1 0x4bfa694
1 0x4bfa694
1 0x4b78fb0
1 0x4be3a10
1 0x4c1a4ec
1 0x4c1ab48
1 0x4c1aba4
1 0x763084
1 Microseconds
1 AbsoluteToNanoseconds
1 AbsoluteToNanoseconds
1 0x4b790f4
1 0x763098
1 WideDivide
1 WideWideDivide
1 __moddi3
1 __moddi3
1 0x4b1abe0
1 0x4be78e4
1 0x4ba5b84
1 0x7c18b4
1 0x7c18b4
1 0x4b1ac30
1 0x4beb76c
1 0x4bff4e0
1 0x4bff4e0
1 0x4b1ab74
1 0x4b1ab74
1 0x4b6ff8c
1 0x4b6ff8c
2 0x4b1bf68
1 0x4b1ac30
1 0x4beb76c
1 0x4bff4d8
1 0x4bff684
1 0x4ba3dc8
1 0x4ba3828
1 0x4ba3b28
1 0x763098
1 WideDivide
1 WideWideDivide
1 __divdi3
1 __divdi3
1 0x4b1ac54
1 0x4b75ef8
1 0x4b78f14
1 0x4be3db8
1 0x4c1a4ec
1 0x4c1a8f8
1 0x4c1c348
1 0x4c18374
1 0x4bfab28
1 0x4bfab28
41 0x70aa84
41 0x70acb8
41 WaitNextEvent
41 0x236d238
41 GetNextEventMatchingMask
40 0x2288b20
19 0x167d4ac
10 0x167da0c
9 0x167d6b8
9 0x167ba5c
9 0x16696dc
9 0x1173994
9 dladdr
5 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
5 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
2 ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const
2 ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const
2 dladdr
1 0x167d698
1 0x165fc40
1 isStrongMemory
1 isStrongMemory
6 0x167da1c
5 0x167d6b8
5 0x167ba5c
5 0x16696dc
5 0x1173994
5 dladdr
4 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
4 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
1 dladdr
1 0x167d7b4
1 0x165df74
1 0x1661230
1 0x1661230
2 0x167da2c
2 0x167e3f8
2 0x167ba5c
2 0x16696dc
2 0x1173994
2 dladdr
2 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
2 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
1 0x167dba8
1 0x110e348
1 0x110e348
15 0x167d494
8 0x167d710
8 0x167801c
8 0x16696dc
8 0x1173994
8 dladdr
6 dladdr
1 ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const
1 ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const
1 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
1 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
7 0x167d6b8
7 0x167ba5c
7 0x16696dc
7 0x1173994
7 dladdr
5 dladdr
2 ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const
2 ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const
5 0x167d4c0
5 0x167d6b8
5 0x167ba5c
5 0x16696dc
5 0x1173994
5 dladdr
4 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
4 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
1 ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const
1 ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const
1 0x167e034
1 0x167e034
1 0x23296a4
1 CGSGetNextEventRecord
1 CGSGetNextEventRecord
90 Thread_1003
90 0x112ed08
90 AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*)
90 0x168c90c
90 0x167d4ac
90 0x167dba8
90 0x110e348
90 0x110e348
90 Thread_1103
90 0x112ed08
90 0x2b053dc
90 HALRunLoop::OwnThread(void*)
90 0x167d4ac
90 0x167dba8
90 0x110e348
90 0x110e348
90 Thread_1203
90 0x112ed08
90 ReadSchedulerThreadEntryPoint
90 TSWaitOnSemaphoreCommon
90 0x1157388
90 0x1157388
Total number in stack (recursive counted multiple, when >=5):
6 0x110e348
6 0x1173994
6 0x16696dc
6 dladdr
5 0x167ba5c
5 ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const
Sort by top of stack, same collapsed (when >= 5):
0x110e348 219
0x1157388 90
ImageLoaderMachO::getIndexedExportedSymbol(unsigned) const 16
dladdr 14
ImageLoaderMachO::getExportedSymbolAddress(ImageLoader::Symbol const*) const 6
Sample analysis of process 1027 written to file /dev/stdout
Sampling process 1027 each 10 msecs 100 times
Message was edited by: James Mol

Yep, you are right. If I could find something like that I would have used it. So I had to work with what I had available from activity monitor.
It did stop when I quit a demo disk I was using. Looks like it was a Director MX2004 file/app.It was not the name of the program I was running, but it was a part of the program. Guess I should have check around sooner. Sorry to have bothered you all.
If I could remove the post I would.

Pismo freezes when optical drive is in expansion bay

I have a PowerBook G3 Pismo/2000/Firewire with OS 10.4.11 installed. Suddenly, it won't boot up with the Optical Drive in the bay. It boots fine without the drive.
With the drive, the grey screen comes up and the Apple logo appears. The rotating circle never appears and it just freezes.
If I boot with the drive out, and then insert the drive the computer freezes and is totally unresponsive.
Has anyone experienced this problem or have any suggestions. I was going to run the Hardware Test disc, but since the Optical Drive cannot be used that is a problem.

esqjd,
I am glad you had the use of another Pismo for testing; my analysis was obviously wrong, and I thank you for replying with additional info.
Regarding your HD: I did not mean to suggest it was the source of the problem, only that a bad HD can cause similar problems.
First, I should have suggested you reset the PRAM to cover all bases:
http://docs.info.apple.com/article.html?artnum=2238
If the PRAM reset does not help, I would run another test: Shut off the Pismo and install the optical drive > open the tray by pushing an opened paperclip into the little hole next to the button > place a bootable CD or DVD in the tray and close > power on while pressing the 'option' key > if the Startup Manager appears, select the CD or DVD > select the 'continue' arrow > see if it will continue to boot.
http://docs.info.apple.com/article.html?artnum=106178
The purpose of this procedure is to test for a hardware or software problem. Starting to the Startup Manager all occurs in firmware until you select the CD or DVD, then the software begins to load. If your Pismo will perform normally and boot to the optical drive, then you probably have a software problem on the HD.
If you reach the Startup Manager but the CD or DVD will not boot, double-check the optical drive on the other Pismo by following the same procedure.

HP 2311x monitor not seen by OSX unless the monitor is off/has no power

I have hooked my Macbook pro up to TV's in the past without issue, I'm now trying to hook it to my HP 2311x monitor. When the monitor goes to sleep, or I unplug the power the Mac screen will flicker like it does when I first hook up HDMI and then I have my mirroring options and it sees the monitor, when I power on the monitor it then is unable to see it and I lose those options. Any suggestions as to what I can do?

So - I am having an issues with the same monitor. I spend 2+ hours on the phone with Apple care. They had me do all sorts of resets and stuff. While this isn't really helpful - they had no real response. They suggested I but a thunderbolt cable and see if that worked. Alternatively, they noted that HP might need to update their firmware for OS Mavericks and I might just have to wait for that. So... just FYI. Hope you manage to resolve it better than I have been able to.

VST Zip disks do not mount in OS10

I have just upgraded my Powerbook G3 firewire to OS 10.2.8. I have a VST Zip 100 expansion bay drive for my zip disks, but I am having to boot into Classic 9.2.2 for the zip disks to mount to the desktop. Is there a driver available so they will mount in OS 10?
DawnMerr

DawnMerr,
From what I have read, OSX has native support for the VST Zip100...no additional drivers needed. I would try this first: Shut down your powerbook, insert the VST drive if not installed, power up and try the drive; a few users have reported it is not hot-swappable.
However, it should work as it does in 9.x, and some have found success by performing a flush of the caches. Download the freeware utility 'Yasu' here:
http://www.macupdate.com/info.php/id/13416
Go halfway down the page and find the link for Version 1.0.3 for 10.2 and later. Once you have launched Yasu, select the boxes to run OSX's built-in daily, weekly, and monthly CRON (maintenance) scripts and also those for the System, User, and Font caches. If you have not done recently, you can also check the box to Repair Disk Permissions. Running all of the above will take a little time and the first restart will be slower than usual. Uncheck any other box. If the computer does not restart automatically when done, be sure to do so...this is most important.

Lombard 333 Making Screaming Sound When Aftermarket Battery Is Moved In Bay

I recently posted in "Using..." and eventually determined that this problem has to do with the (aftermarket) battery I am using:
Whenever I would disconnect my ac adapter, wake the unit from sleep, or even go to power it up, I would hear a sort of "screaming" sound coming from it and the powerbook would shut down.
This started occuring just within the last two or three weeks or so, and it was a very off/on problem. After the unit would shut down, I would reset the PRAM and start it back up, and usually it would work fine. I repaired permissions because I had recently installed a Security Update.
Eventually, I was using the powerbook and went to move it slightly on the desk (while it was running), and I accidentally nudged the battery while it was in the (left) bay, causing the screaming noise to happen again. I moved the battery around in the bay and the screaming was intermittent. Unfortunately, I purchased this battery online and still need to send it back for a refund/exchange, and the battery that came with the unit when I bought it is dead, so I have no way of testing this "the aftermarket battery is crap theory," and I was just wondering if there was anything else I could do in the meantime? I believe I tried the battery in both expansion bays and the same thing happened.
What if I receive another battery and I have the same problem? I assume the worst case scenario would be that I would have to replace some hardware, but the battery seems to be recognized and charge just fine and I haven't had any other problems with it since I got it just over a month ago.
Any thoughts on this?
Any input would be greatly appreciated.
Thanks.
recon_element @ yahoo.com

Woke the PB up after it had been asleep for a day or so... it screamed when I woke it up, the UI got funny, and then it was ok... I had the PC card in.
Booted from OS 9.2.2 disc, unplugged the adapter, had no problem.
Booted back into OSX, unplugged the adapter, no problem.
I was doing some work on my wireless LAN settings, and then decided to unplug the adapter so I could move around... it didn't make the scream sound, but it shut off. Restarted. The year in Date & Time went to 1969, but then were corrected automatically when the PB found the wireless network.
I just unplugged the adapter again and nothing happened.
What's the deal? Very wierd...

Getting multiple intermittent calls for VOP_OPEN() and VOP_CLOSE() from kernel when copying files to my VFS

When I try to copy a file to my mounted VFS, I get multiple VOP_OPEN() and VOP_CLOSE() commands intermittently. This behavior was not seen on OSX versions earlier to Mavericks. I used VOP_CLOSE() as event to trigger code to Check-in command to my server, as a result now I am getting multiple check-in requests from my kernel extension module which finally fail.
How do I work around this issue on Mavericks?

Hi Ncat,
I might have had similar problems with yours. Finder stuck at 'Not Responding' while I boot my Macbook Pro with external HDD plugged in, my macbook heats up considerably maybe because it keeps trying to access the external disk. And Finder can only proceed after I unplugged my external hard disk.
So what I did was:
I rebooted my macbook into recovery mode (by holding cmd+R before / during the booting chime
I used the Disk Utility from there (instead of from normal booting)
Then I proceed to with 'Repair Permissions' and 'Repair Disk' for each and every partition of the external harddisk, and also my internal hard disk.
Rebooted after everything's done, and now it seems to work.
I hope that it will work for you

VST Expansion Bay HD intermittently seen by osx.3 (kanga)

Similar Messages

Maybe you are looking for