Although I am starting to get used to the completely different approach of the Mac OS X, and actually starting to think it’s faultless, I still have a need for a Windows based operating system. Mainly for development works but also to run some of the apps which don’t yet have Mac equivalents.
VM Gets the IE8 treatment
The download is available to the public from IE8’s homepage, the download comes in at 13.3MB, but as with all IE installs, this simply downloads more files from the net prior to installation.
The download finished quite quickly, however with most installs thesedays requires a reboot before it takes effect.
Over the next few hours, I will be using IE8 as my default browser whilst I work on an offline website I am building for someone. I will post back any rantsravesreviews as and when I come across them.
For now – enjoy the future of one of the worlds most commonly used browsers!
Install .deb files in SuSe
If you find yourself downloading an application packaged in a .deb file, but you want to install it in SuSe you may be able to use Alien
1. In a new terminal window type su hit retutn and type root password
2. Download and Install alien using zypper: zypper in alien
3. Run: alien -r filename.deb, you should then find a .rpm file in the same location as the .deb which you can open with the application installer..
Get local IP Address in SuSe
If (like me) you have migrated from Windows to Linux, you may have noticed you no longer have the IPConfig command available to get network card details.
Linux sports an alternative to ipconfig, which is called ifconfig.
You have to run ifconfig as an admin user, so in a terminal window type:
– You will be prompted to enter the admin accounts password
– You should now be presented with a list of all the network card configuration details for your PC.
SuSe 11.1 – Fatal Server Error: No Screens Found – FIXED
Recently my SuSe 11.1 install stopped booting, after further investigation I found the following error in the log files: Fatal Server Error: No Screens Found after some hunting around the net, and many failed tests. I finally managed to resolve the issue..
If you are suffering from the same problem, try:
Log in as rootType “sax2 -m 0=vesa”
This should load the vesa driver.
Now reboot and you should find you will at least get your GUI back.Once logged back on, you may then want to adjust your display driver etc.