Skip to main content

Leopard OS-X Virtual Machine

Recently, I was playing around with installing Leopard on my Dell, and I thought I'd try to get it running in a Virtual Machine.   So, I popped in the Kalyway 10.5.2 DVD, and installed it without too much trouble, actually.  I thought I'd record the settings that I used, as getting the Kalyway installs working is highly hardware dependent.  My machine is a quad-core 64-bit HP p6310y machine with an AMD Athlon II X4630 processor, with 8GB of RAM.  

I looked at the below guide, but the only thing that I used from it was the BIOS settings, which was a smart idea I thought.  The rest I did from memory and via trial and error.  

http://pcwizcomputer.com/index.php?option=com_content&task=view&id=36&Itemid=45

First, I set up my VM to be an 'Other' OS (there's no Hackintosh OS), and increased the size of the RAM (Other defaults to 256MB ) to over 512MB.  If you have too little RAM, the install will simply hang.  

I removed the sound and floppy from my VM, as I didn't need that.  Then I booted into the Kalyway 10.5.2 DVD, and hit F2 immediately to enter the BIOS.  I used the setup instructions in the above URL to nuke the serial ports, parallel port, and floppy from the BIOS, hoping it would boot quicker.  Then I hit F10 to save the BIOS settings and boot into the DVD.  

When Kalyway booted into the setup, I went into Utilities->Disk Editor, and selected the Partition tab, and partitioned my disk (Volume Scheme is 1 Partition) to be a JFS disk, and selected the "Options" button under the disk to change the bootloader to MBR.  I then partitioned my disk.



Next, I selected Continue->accepted the EULA, and selected CUSTOMIZE.   I used the default (sleep) kernel, and unchecked everything to make it clean.  As I had an AMD processor, I checked the AMD Patch 1 and the Boot_with_legacy_flag.  That is what I considered the bare minimum to test the machine.  Later on, after I knew that this worked, I went back and messed with the Network settings, but first I wanted to try out the OS, as minimal as possible.  



Note, Mobo_Chipsets will cause a booting loop for me, so I unselected these. 

Next, I selected Continue, and I SKIPPED the disk check (this adds an hour or two).   When I came back a few hours later, my Leopard was ready to be set up.  

That was it.   Next, I reinstalled it again with the Network Drivers to try to get Ethernet working.... but I couldn't get this to work, even with all the Network Drivers (except wireless) loaded.  Thus, I have a working Leopard, but without any Ethernet.    It's mostly useless.  

Comments

Popular posts from this blog

HP c6180 Printer and Vista

Hp c6180 driver issues with Vista Home Premium My wife has a Vista Home Premium laptop, and the HP C6180 Photosmart printer keeps disappearing from her available printers.  The only way I've found to fix the problem is to reinstall all the HP software. When I do this, I have to download the (large..507M software from HP, or reinstall the printer (ONLY the printer, not the scanner) with the installation disk, as the drivers are not discovered with a "Windows Update" setting.  My guess is that is because HP doesn't like people to install only the printer driver, which would be easy, but they want folks to install all their crapware as well, so they are withholding the drivers from the on-line Microsoft printer database.  So keep your installation CD!  I've also found that unless I install everything on the CD or in the Full Version download (HP Customer Participation Program, HP Imaging Device functions, HP OCR SW, HP All-In-one SW, HP Photosmart Essential, HP

atftpd vs tftpd-hpa

Recently I was trying to tftp files from a Windows computer to a Kali box.   One version of Windows worked, but another didn't.    After much troubleshooting, here were my symptoms: I could tftp a file from-to any Kali box from-to another Kali box I could NOT tftp files to a specific Windows 7 box from any Kali box I could NOT tftp files to a Chrooted-Ubuntu-Chromebook box from a Kali box After MUCH troubleshooting, going through every setting in atftpd, it seemed like it literally was a client OS problem.  Different clients simply would not download files---unacceptable. Thus, I switched to tftpd-hpa.   To install: apt-get install tftpd-hpa files go to/come from /srv/tftp, but it needs to be a tftp user. Thus, I needed to: chroot -R /srv/tftp Also, if you want to be able to put files ON the tftp server (from a client), you need to modify /etc/default/tftpd-hpa: change "TFTP_OPTIONS="--secure"  to "TFTP_OPTIONS="--secure --create" I al

Security Onion on the Antsle

My Setup of Security Onion on the Antsle: Recently my IDS box, an Intel Atom D2500 Fanless Mini-ITX PC, D2500CCE, died.  Truth be told, I think it came from the factory in a bad state, as I originally thought I had a bad graphics driver, but I then noticed that, after much troubleshooting, it wasn't a driver issue at all.  The box just sometimes wouldn't boot up correctly with video.  It seems heat related, something like not enough thermal paste on the CPU, as after it is powered off for a while it is more likely to boot than when it is warm.  Along with that issue, this box maxed out at 4GB of RAM (only has 2 memory slots, each of which will only take a 2GB card max) and had a single processor, so it was under powered for Security Onion. So, I decided to quit limping along on P.O.S. boxes, and buy a little more heavyweight box for my networked IDS.   Security Onion requires a minimum of 8GB of RAM, and 4 cores per their specs page https://github.com/secur