Yokemate of Keyboards
Posts: 2795 from 2006/3/21
From: Northern Calif...
osco,
Quote:
@Dave: Would you open a shell and type the "battery" command?
Curious to see your output?
Not sure why you want this info osco, but the resulting message is this:
12V / 4Ah battery found. Current battery level is 98 %.
Update on my experience using MorphOS3.0:
Since I suffer from insomnia, I did not sleep last night after I installed MorphOS3.0 on my model 5.9 17" G4 PowerBook w/1gb RAM & 120gb hard drive, display set at 1680x1050. Before I report more about MorphOS3.0 running on this PowerBook I have to explain that when running MacOSX 10.5.8 on this computer I would occasionally experience kernel panics, or sometimes an unknown lockup, which I had hoped was being caused by an unmatched pair of RAM dimms, when I had 1.5gb of RAM installed in it, but the problems still happened occasionally after I removed the 512mb dimm and went back to only 1gb of RAM, so the memory apparently is not the problem. I was hoping that I would not experience any of these mysterious lockups while running MorphOS3.0, but have already had a couple of them today.
After I installed MorphOS3.0, I first edited the install script for the Pack Ultimate, so it would accept being installed on a system with MorphOS3.0, instead of MorphOS2.7. I then downloaded and installed the latest version of Grunch and used it to update any of the software that the Pack Ultimate installed, as a lot of it was not the most current versions available. Grunch is great for this purpose.
I then noticed that the MorphOS SDK did not get installed fully, or correctly (don't know if it was supposed to be included with MorphOS3.0, or if it was the Pack Ultimate that had tried to install the SDK, but in any case, I also noticed that Grunch does not allow the user to adjust the location for the SDK to be installed and that because the partial installation of the SDK was not in the place that Grunch expected it to be, Grunch was not able to Un-install the SDK, so that I could attempt to install it again. Since there was an assign or two for the SDK within the Startup-Sequence, I could not delete all of the SDK until I first disabled the assign statements in the Startup-Sequence temporarily.
I then edited the Grunch database entry for the MorphOS SDK, so I could choose where it would be installed, but I must have missed something, because I still could not enter a directory location inside of Grunch for the installation of the SDK and just installed it where ever it was going to go, but then found that within the installation script I was able to choose the location and it appears that the SDK is not installed fully, but I have not tested it yet. After the installation, I re-enabled the SDK assign statements in the Startup-Sequence and have been testing MorphOS3.0 for hours last night and today.
MorphOS - The best Next Gen Amiga choice.