Archive for July, 2014

Abandon Ye The Linux Command Line

July 29, 2014

The Linux command line interface is an extremely useful tool.  It expands the overall functionality of the Linux experience by giving users access to programs that otherwise may not have a graphical user interface.

To the lifelong Microsoft Windows or Apple Mac user, however, the command line just looks like this:

The Linux command line as perceived by a Windows user

A complete pile of nonsensical crap!

It’s also the basis for attack FUD (fear, uncertainty and doubt) by fanboys and paid commenters\bloggers\trolls, who routinely post on various websites in an attempt to discredit Linux and dissuade users from considering Linux as a viable alternative to their current operating system.

The average user isn’t going to know to download the source code and compile it to run their apps…  Using linux is the absolute worst thing you can do in this situation.

The preceding FUD is a complete and total lie.  Repeat a lie enough times and people will start to believe it.

I’ve been using Linux since 2008 and have never once had to compile a program or kernel update.  The Linux desktop environments, in all their various forms, are just as point-and-click user-friendly as MS Windows, if not more so.

From a purely marketing standpoint, if you want more people to convert to Linux, you must convince them that they already possess the intuitive computer skills needed to use a Linux-based operating system.

There is no learning curve.  Anyone who can use a Windows or Mac PC will have no difficulty switching to Linux.

There is a bigger learning curve going from the PC environment to an iPhone or Android-based user interface.  But millions of people have adapted.

Continue posting tutorials about the use of the Linux command line.  That information is important.  And whenever possible, include instructions for the GUI version of that same task.  Please don’t fuel the FUD.

We want more people to know that Linux is just as easy to use as Windows or Mac.  Help spread the word.

 

Advertisements

Loading Windows 3.11, 95, ME and XP In VirtualBox

July 28, 2014

Windows 3.11 running in VirtualBox

For many of us, this was our first experience with the Microsoft Windows graphical user interface (GUI).  Windows 3.1x was nothing more than a graphical shell around which DOS operated.

Thanks to VirtualBox, you can relive that nightmare all over again!  Just point your browser to Kirsel’s amazing website and download all the image files you’ll need to install Windows 3.1x in VirtualBox.

If you know nothing about VirtualBox, now would be a good time to learn.  An image file (.img or .ima) can be used as a substitute for physical floppy disks in VB.  You swap image files under the Devices menu at the top of the screen while VB is running.

Before attempting to load Windows 3.1x or Windows 95 in VB, you must disable VT-x/AMD-V and Nested Paging under the System > Accelerations settings tab.

A full tutorial has been created by Glijnos to walk you through the process.

I have all of the images files for DOS 6.22 and Windows 3.11 that were included with my first Windows computer: a Packard Bell Legend series system with a 50MHz Intel CPU, 4MB of RAM built onto the motherboard (upgraded to 36MB by adding two 16MB RAM chips), and a 512MB hard drive.

How cool was that?

Program Manager Windows 3.11 About Screen

Not very.

Why would anyone want a working virtual copy of Windows 3.1x?  Well, perhaps you have a bunch of old software programs lying around and just need to open a document in Microsoft Works 3.0:

Microsoft Works 3.0 in Windows 3.11

Or maybe you just want to see the Berkeley Systems After Dark Loony Tunes screensaver you bought years ago run just one last time:

Looney Tunes After Dark Screensaver

That Pepé Le Pew sure was a scoundrel!

Pepé Le Pew After Dark Screensaver

Or you just want to rekindle old skills you’ve forgotten.

Or you’re like me and you have a bunch of old Windows install discs collecting dust that are just begging for new life.

Windows 95:

Windows 95 running in VirtualBox

Historically significant, Windows 95 set the standard for the desktop GUI.  It was also insanely unstable.  Even in VB, it may still give you fits.

Create a new VB install.  Set the virtue hard drive (.vdi file) to a fixed size of no more than 2GB.  Set RAM to 32 or 64MB.  Set video RAM to 32MB.  Remember to disable VT-x/AMD-V and Nested Paging.

If you have a full Windows 95 install disk (OEM disks or full commercial release), load DOS 6.22 just as you did for Windows 3.1x.  Add the  cdrom.img files to the completed install.  Now you can reboot your virtual install and use your Windows 95 disc to install the OS.

Windows ME:

Windows ME running in VirtualBox

One of the most hated operating systems in Microsoft’s history, Windows ME still gives users headaches when trying to do a VB install.  But I found a way around that problem.  Install Windows 95 first and then upgrade.

Here we go again!  Create a new VB install.  Set the virtue hard drive (.vdi file) to a fixed size of 8GB.  Set RAM to no more than 512MB.  Keep the video RAM at 32MB.  Remember to disable VT-x/AMD-V and Nested Paging.

Load DOS 6.22 just as you did before for Windows 3.1x.  Add the  cdrom.img files.  Now you can reboot your virtual install and use your Windows 95 disc to install the OS.  Once installed and booted, insert your Windows ME disc (full, OEM or upgrade) and follow the onscreen instructions.

When Windows ME finishes installing and completes a first boot, shut it down and enable VT-x/AMD-V and Nested Paging.  This will speed up ME in VB.

When you loaded Windows 95 in this install, it created a virtual hard drive of only 2GB, but our .vdi file is 8GB in size.  How do we get those 6GB back?  With Linux!

Download the 32-bit version ISO image file of GParted.  Or use your favorite Linux distribution Live Boot Disc that contains the GParted program.  Boot your Windows ME VB install into Linux and use GParted to format the unallocated portion of the virtual hard drive to FAT32.  You can name the drive if you wish.

Remove the Linux disc or image file from VB and boot back into Windows ME.

Windows ME My Computer Screen

Your install now has two hard drives!  A 2GB C: drive and a 6GB D: drive are both accessible from within the virtual environment.  Thank you, Linux.

Desktop themes from Windows ME

Installing Guest Additions:

Forget it.

None of these operating systems are compatible with the VB guest additions.  However, you might manage to get part of the guest additions to load in Windows ME before you get an error message.  This will at least load the mouse integration drivers and allow you to automatically “capture” the pointer when hovering over the ME window.

You will have no USB access, no shared folders and no fullscreen integration.  Other than that, it works great.

Internet access may be possible in Windows ME by using the Internet Connection Wizard’s third option and connecting through the local area network (LAN).  Use ClamWin Free Antivirus and the Sygate Personal Firewall to help protect the guest OS.

 

Video Drivers:

The best video drivers for Windows 95\98 and ME can be found at the VBEMP 9x Project.

Right-click on My Computer > Properties > Device Manager > [+] Display adapters and select the entry under that heading.  Click the Properties button at the bottom of the box.  Click the Drivers tab and then Update Driver… to install these drivers.

I didn’t say it was easy.  But it does work.  Once installed, you can set your screen resolution from 320 x 200 256 colour up to 1600 x 1200 True Colour (32-bit).  Do not use the fullscreen integration feature of VB.

There are three sets of drivers folders provided by the VBEMP 9x Project.  Each folder is marked to the corresponding amount of video RAM you allowed in the VB settings.  If you set the video RAM to 32MB, use the folder labelled 32MB.

Printers:

Printers in Windows ME

It can be done.  Like any guest OS in VirtualBox, you must add the printer argument to the system through the VB USB settings.  The guest OS must have USB support and recognize that a printer is connected.  The printer must have the appropriate print drivers to install in the guest OS.

The HP Deskjet 5940 originally included Windows ME drivers and software.  Hewlett-Packard also offers additional drives on their website.  Other manufacturers may also offer drivers for older operating systems.

A Few Tips and Tricks:

The easiest way I found to import files into the VB installs is to use AcetoneISO.  This Linux only program can be used to convert a folder and its contents to an ISO image.  The image can then be mounted in VB and accessed by any Windows install as a physical CD\DVD.

Alternatively, you can always burn the files to a blank CD\DVD.

Backup your .vdi file.

If this is your first introduction to VirtualBox, there are some excellent tutorials to help you get started.

Early Windows install disks were not boot disks.  If you are loading Windows 95\98\ME from scratch, you must use the fdisk command from a running boot disk to create partitions on the virtual drive and then format the drive (typically Fat 16 for 95 and Fat 32 for 98\ME) (format c:) before loading the OS.  DOS 6.22 automatically formats before it installs.

Installing old operating systems in VB is a fun way to learn more about the history of operating systems and how they worked.

It can also be useful for playing older Windows-based games that no longer run on newer Microsoft platforms.

The most useful out-of-date OS is still Windows XP:

Windows XP running in VirtualBox

Windows XP has full integration with the guest additions software in VB.  You can backup and port the .vdi file to other computers.  Although Microsoft no longer supports XP, there are still plenty of compatible software packages available from other vendors.

Old Version provides free downloads of older software programs.

For more information about old operating systems, check out the History of Operating Systems.

VirtualBox is a fun tool for exploring operating systems both old and new.  Now, go put those old discs to good use!

VirtualBox Installs of Windows

 

Nuke It From Space

July 2, 2014

"I say we take off and nuke the entire site from orbit. It's the only way to be sure."

I say we take off and nuke the entire site from orbit. It’s the only way to be sure.
— Ellen Ripley (Aliens, 1986)

When it comes to computer viruses there is only one way to be certain that the infection has been removed from your machine.  Wipe the hard drive clean and reinstall the operating system.

Antivirus software is only effect if it blocks a virus from being loaded onto your computer.  Once a virus is installed, it often times rewrites or replaces key system files.  Undoing such alteration requires a clean install of the OS.

There are plenty of so-called “computer techies” who will be happy take your hard-earned cash, run a free antivirus program over your computer, and then claim to have “eradicated” the virus.  These fly-by-night business owners, many working out of their parents’ basement or shoddy little apartment, are doing their clients a tremendous disservice by removing the symptoms but not necessarily the cause.

Anyone can run a free antivirus program or Malwarebytes on their computer and do exactly the same thing at no cost to themselves.  The computer will in most cases appear to function correctly.  But remnants of the virus may remain making your computer susceptible to future infection.  Or worse still, it could be executing code in the background without your knowledge or consent.

The problem, however, is that most major Microsoft Windows computer manufacturers have stopped including restore disks with their new systems.  Many have replaced these disks with “restore” software housed in a small partition on the back end of the hard drive, which does not reformat the main Windows partition.  It simply overwrites some Windows files in an attempts to repair the operating system, but may leave a virus still lurking on your computer.

Some manufacturers like Acer, Lenovo, Hewlett-Packard, and Dell do offer full restore DVD-ROM disks.  Customers must request these disks immediately after purchasing a new computer.  These disks may only be available during the initial warranty period.  Expect to pay about $20 (US).

Alternatively, you can create a Windows system image from your current Windows installation.  However, this restore image is useless if your system has already been compromised by a virus.  You would be restoring the virus along with the operating system.

Other alternatives include downloading all relative hardware drivers for your particular make and model of computer from the manufacturer’s website, and then purchase either a full or OEM version of Windows from a reputable seller like Newegg, TigerDirect, or Buy Cheap Software.

Those who have chosen to build their own systems are exempt since they already own a required copy of Windows.  Linux users are likewise exempt since full Linux install disks are readily available free of charge.  Not that Linux users need to worry about viruses.

Instructions for performing a clean install of Windows can be found at numerous sites on the Internet.  The keyword to search for is “clean” install.

Every computer owner must possess the ability to install their respective operating system from scratch.  All hard drives eventually fail!  It’s not a question of if, it’s a matter of when.

Backup your data!  To be forewarned is to be forearmed.

Don’t be a victim of the local-yokel computer repair scammer.  Save your money.  Empower yourself and learn to be your own tech support.  As Francis Bacon once said:  Nam et ipsa scientia potestas est (Knowledge itself is power).