You are not logged in.
This was originally posted over in the CrunchBang forums and I've decided to create a copy here. Although the following instructions reference Windows 7 Pro, I have used the same procedures to create a Windows 8 Home VM using VirtualBox v5.0.12 under BunsenLabs Hydrogen 64-bit. I will attempt to keep this how-to updated as time, personal inclination, and forum member interest permits.
You will need a Windows 7 Pro installation/re-installation/recovery CD or ISO file to install Windows 7 Pro. If your CD/DVD drive is not an internal component of your computer, then you will have to rip the CD to an ISO format or obtain an ISO file from the Internet. If you obtain an ISO file from the Internet, you will need a product activation key at some point to continue using Windows 7 Pro.
If your copy of Windows 7 Pro came with your computer or you use your activation key for an ISO file obtained from the Internet, you may be required to contact Microsoft to obtain a new product activation key.
===============================================================================
01 - STEP 01 - Dynamic Kernel Module Support (DKMS)
First, we need to install the Dynamic Kernel Module Support (DKMS) package. From the command line:
sudo apt-get update
sudo apt-get install dkms
-- or --
sudo aptitude update
sudo aptitude -P install dkms
DKMS helps with maintaining the VirtualBox kernel module, vboxdrv, when the kernel is updated.
01 - STEP 02 - Obtaining VirtualBox
Next, download VirtualBox for Linux hosts from the official site; www.virtualbox.org/wiki/Downloads. The version in the repos is usually a few versions behind. While you're at the VirtualBox site, also consider downloading the VirtualBox Extension Pack. The extension pack provides support for USB 2.0 devices, VirtualBox RDP (Remote Desktop Protocol) and PXE boot for Intel devices.
After downloading, make sure to compare the MD5 or SHA256 checksums (SHA256 is better) of the downloads with the checksums on the VirtualBox site. Checksum matches are good assurance that the files haven't been tampered with and that they downloaded correctly. gtkhash is a nice GUI tool for comparing checksums and it's available from the repos.
01- STEP 03 - Install VirtualBox
Now we're going to install the VirtualBox program. Drop to the command line in the folder containing the downloads from 01 - STEP 02 - Obtaining VirtualBox and perform one of the following commands:
sudo gdebi <VirtualBox-filename>.deb
-- or --
sudo dpkg -i <VirtualBox-filename>.deb
If you do not have gdebi, it can be installed from the repos.
Note: Installing VirtualBox automatically creates the appropriate settings so that when you perform an apt-get dist-upgrade or aptitude full-upgrade, VirtualBox will be updated if applicable.
01 - STEP 04 - Add Yourself to vboxusers Group
We need to add our username to the vboxusers group. From the command line:
sudo usermod -a -G vboxusers <username>
Adding yourself to the vboxusers group will allow you to use USB devices connected to the host system from VirtualBox guests.
================================================================================
02 - STEP 01 - Location for Virtual Hard Disk and Snapshot Files
If you have a shared data partition, you may want to store your VirtualBox virtual machine files there. If so, add the following folders to a desired location:
Virtualbox_VMs
Under the Virtualbox_VMs folder, add the following folder:
Win7-Pro-xxx
where xxx is something unique in case you want to have more than one Windows 7 Pro virtual machine.
Under the Win7-Pro-xxx folder, add the following folder:
Snapshots
Otherwise, the virtual machine files will be stored under the VirtualBox VMs folder under your home folder.
02 - STEP 02 - Virtual Machine Creation
Start the VirtualBox program and in the VirtualBox Manager window either click the New icon, or from the menu bar, select Machine - New.
02 - STEP 03 - Name and Operating System
In the Create Virtual Machine window, enter a name for your virtual machine, the Type field should be Microsoft Windows, and select the appropriate version of Windows 7 (32-bit or 64-bit). Click the Next button.
If you created folders in 02 - STEP 01 - Location for Virtual Hard Disk and Snapshot Files, then the name you provide in the Create Virtual Machine window should be the same as the folder under Virtualbox_VMs.
02 - STEP 04 - Memory Allocation for the Virtual Machine
Select the amount of RAM that you want to be dedicated to the virtual machine. Click the Next button.
You will be limited by the total amount of RAM for your computer. In general, you do not want to dedicate too much more than fifty percent of your total RAM. 2GB is probably the bare minimum for a Windows 7 installation. I am running Windows 7 Home under VirtualBox with 2GB of RAM and it runs, although it can be sluggish at times.
02 - STEP 05 - Virtual Hard Drive Creation
The Create a virtual hard drive radio button should be selected. Click the Create button.
You may opt to create a virtual hard drive later, but I will not be covering the procedures for that scenario. You should be able to figure out the procedures based on this how-to and by looking through the settings for your virtual machine.
02 - STEP 06 - Virtual Hard Drive Type
The default hard drive file type, VDI (VirtualBox disk image), should be fine unless you plan to use the virtual hard drive with other virtualization software. Click the Next button.
02 - STEP 07 - How the Virtual Hard Drive Is Stored
Elect to have the virtual hard drive dynamically allocated or a fixed size. A dynamic allocation takes up less hard drive disk space initially, but can be slower to work with. Click the Next button.
02 - STEP 08 - Virtual Hard Drive Location and Size
Enter the name of the virtual hard drive, determine where it will be located, and what size it will be. Click the Create button.
If you created folders in 02 - STEP 01 - Location for Virtual Hard Disk and Snapshot Files, then click the folder icon to the right of the virtual hard drive name field and select the folder that you created under the Virtualbox_VMs folder. The default location for the virtual hard drive file is in the VirtualBox VMs folder under your home folder. In my experience, the Windows 7 Pro install plus updates and service packs took up about 20-22GB of hard drive space. You will also need room for programs.
Now we have an empty Windows 7 Pro virtual machine, also known as a guest. The VirtualBox Manager window should look something similar to the following:
================================================================================
Before we proceed to the installation of Windows 7 Pro, you may wish to tweak some of the settings for the virtual machine that has been created. The following steps require the virtual machine being selected in the left panel of the VirtualBox Manager window.
03 - STEP 01 - General Settings
Click the Settings icon, or from the menu bar select Machine - Settings, from the VirtualBox Manager window.
With General selected in the left navigation panel, click the Advanced tab on the right.
If you created a Snapshots folder under the Virtualbox_VMs folder on a shared data partition (02 - STEP 01 - Location for Virtual Disk and Snapshot Files), then click the drop down to the right of the Snapshot Folder field, select Other, and then select the Snapshots folder that you created.
Click OK to save your changes.
03 - STEP 02 - System Settings
a. Click the Settings icon, or from the menu bar select Machine - Settings, from the VirtualBox Manager window.
b. Click System in the left navigation panel. Under the Motherboard tab, deselect Floppy in the boot order list and move it below the CD/DVD and Hard Disk entries.
c. If the CPU for your computer is multi-core, you may select additional CPUs to be used by the guest system (Windows 7 Pro) under the Processor tab if desired. Use the Processor(s) slider or the Processor(s) selector button to make any desired change.
d. Click the OK button to save your changes.
03 - STEP 03 - Display Settings
Click the Settings icon, or from the menu bar select Machine - Settings, from the VirtualBox Manager window.
Click Display in the left navigation panel. If you would like to dedicate more video memory for your virtual machine, make the desired selection using the Video Memory slider or the Video Memory selector button. Click OK to save your changes.
================================================================================
The following steps require the virtual machine being selected in the left panel in the VirtualBox Manager window.
04 - STEP 01 - Select the CD/DVD Drive or ISO File
If you have a Windows 7 Pro installation/re-installation/recovery CD, place it in your CD/DVD drive. Note: If your CD/DVD drive is of the external USB variety, you'll have to rip it to ISO format on your hard drive. Until you install Windows 7 Pro and then install VirtualBox Guest Additions, you cannot access any USB devices connected to the host system from the virtual machine.
Click the Settings icon, or from the menu bar select Machine - Settings, in the VirtualBox Manager window.
Select Storage in the left navigation panel.
Click the CD icon under Controller: IDE in the Storage Tree pane.
Now click the CD icon to the right of the selected CD/DVD Drive field under the Attributes section and select the CD/DVD drive containing the applicable Windows 7 Pro disc, or select the ISO file stored on your hard disk. Once you have made the appropriate selection, the Information section should be populated with information about the CD/DVD or ISO file.
Click the OK button to save the changes.
04 - STEP 02 - Start the Windows 7 Pro Installation
Click the Start icon or select Machine - Start from the menu bar in the VirtualBox Manager window. The Windows 7 Pro installation should begin.
04 - STEP 03 - Run Windows Update to Install Service Packs and Updates
After the last reboot during the installation of Windows 7 Pro, run Windows Update to install updates and service packs.
================================================================================
VirtualBox Guest Additions can only be installed once you have installed Windows 7 Pro in the virtual machine. VirtualBox Guest Additions offers the following features:
mouse pointer integration
shared folders
better video support to include resizing the virtual machine window
seamless windows
generic host/guest communication channels
time synchronization
shared clipboard
automated logons (credentials passing)
Note that when you upgrade VirtualBox to a newer version, you'll also need to upgrade VirtualBox Guest Additions. You may be prompted to upgrade Guest Additions when you startup VirtualBox after the upgrade or you can perform a manual installation.
05 - STEP 01 - Attaching the Guest Additions ISO
From the VirtualBox Manager window with the appropriate virtual machine selected, click the Settings icon, or from the menu bar select Machine - Settings. Select Storage in the left navigation panel.
Click the CD icon under Controller: IDE in the Storage Tree pane.
Now click the CD icon to the right of the selected CD/DVD Drive field under the Attributes section.
Select the VBoxGuestAdditions.iso file under /usr/share/virtualbox.
Click the OK button.
05 - STEP 02 - Install Guest Additions
With your virtual machine selected in the VirtualBox Manager window, click the Start icon or select Machine - Start from the menu bar in the VirtualBox Manager window. If autoplay is enabled in Windows 7 Pro, the VirtualBox Guest Additions installation routine should begin after logging in. Otherwise, using Windows Explorer or a similar program, access the CD/DVD drive and double-click the VBoxWindowsAdditions.exe file to begin the installation routine.
A reboot of your Windows 7 Pro virtual machine will be required upon completion of the VirtualBox Guest Additions installation.
After the installation of VirtualBox Guest Additions in your virtual machine, consider configuring your virtual machine to take advantage of some of the VirtualBox Guest Additions features. The following configurations are all performed under the virtual machine settings.
05 - STEP 03 - Shared Clipboard
If you would like to cut or copy and paste between your Linux host and the Windows 7 Pro virtual machine, then you need to enable the shared clipboard option in your virtual machine settings. With General selected in the left navigation pane of the Machine Settings window, click the Advanced tab and select Bidirectional for the Shared Clipboard type.
05 - STEP 04 - Shared Folders
If you would like to share a folder on your Linux host with the Windows 7 Pro virtual machine, then you need to add the applicable folder.
Select Shared Folders in the left navigation pane of the Machine Settings window.
Click the folder icon with a plus sign on the right.
In the Add Share window, click the drop down for the Folder Path field, select Other, and then navigate to and select the folder on the Linux host that you wish to share.
Check the Read Only checkbox if you want the shared folder to be read only.
If you want the shared folder to be auto-mounted each time you start your Windows 7 Pro virtual machine, then check the Auto-mount checkbox.
Click the OK button to save your changes.
Shared folders can be created and managed while the Windows 7 Pro virtual machine is running as well. From the menu bar In the virtual machine window, select Devices - Shared Folder Settings.
================================================================================
Like VirtualBox Guest Additions, VirtualBox Extension Packs can only be installed once you have installed Windows 7 Pro in the virtual machine. Currently, VirtualBox offers only one extension pack which is downloadable from the VirtualBox site. The current VirtualBox Extension Pack offers the following features:
support for USB 2.0 devices
VirtualBox RDP (Remote Desktop Protocol)
PXE boot for Intel cards
Currently, the VirtualBox Extension Pack supports all platforms; i.e. Linux, Windows, OS X, etc.
Note that when you upgrade VirtualBox to a newer version, you'll also need to upgrade the VirtualBox Extension Pack. You may be prompted to download the newer version of VirtualBox Extension Pack when you startup VirtualBox after the upgrade. You can also manually download the new version from the VirtualBox site. I just make it a habit to go to the VirtualBox site and download the new extension pack whenever VirtualBox is upgraded.
06 - STEP 01 - Download VirtualBox Extension Pack
Download the VirtualBox Extension Pack that corresponds to the current version of VirtualBox that you are using; www.virtualbox.org/wiki/Downloads. For example, if you are running VirtualBox v4.3.14, then you need to download VirtualBox Extension Pack v4.3.14 (file name has been simplified for the purposes of this how-to).
06 - STEP 02 - Add VirtualBox Extension Pack
From the VirtualBox Manager window, select the appropriate virtual machine and then from the menu bar select File - Preferences.
In the VirtualBox Settings window, select Extensions in the left navigation pane.
Click the Add package icon (blue square with a yellow upside down triangle) over on the right-hand side and navigate to and select the VirtualBox Extension Pack file that you downloaded in 06 - Step 01 - Download VirtualBox Extension Pack.
Click the OK button to save the change.
To upgrade the extension pack when VirtualBox is upgraded, perform the same previous steps to get to the Extensions section under VirtualBox Preferences.
Highlight the existing extension pack and then click the Remove package icon (blue square with a red X) on the right-hand side.
Next, click the Add package icon (blue square with a yellow upside down triangle) and navigate to and select the new VirtualBox Extension Pack that has been downloaded.
Click the OK button to save the change.
================================================================================
My lack of knowledge in using USB devices under VirtualBox was one of two things that prevented me from being able to fully use Windows 7 Pro under VirtualBox for about two years.
If you will be using USB 2.0 devices, then you also need to add VirtualBox Extension Pack to your virtual machine; reference section 06 - Adding Extension Packs of this how-to.
07 - STEP 01 - USB Vendor and Product IDs
A very important concept to understand in order to be able to access USB devices attached to the host machine under VirtualBox is USB device filters, which require the use of USB information; mainly vendor, and possibly, product IDs. A somewhat unique vendor and product ID is assigned for each USB device. To obtain the USB vendor and product IDs for a USB device, attach the USB device to your host machine (mounting not required) and then from the command line enter one of the following commands:
lsusb
-or-
VBoxManage list usbhost
In the following screenshot, lsusb shows the vendor and product IDs for a Kingston DataTraveler (DTSE9) 16GB USB thumb drive (last line) that I've attached to my CrunchBang host machine.
ID 0930:6545 represents the USB ID. 0930 is the vendor ID and 6545 is the product ID.
07 - STEP 02 - Creating USB Device Filters
Once you have the vendor and product IDs, you can setup a USB filter which will enable you to use the device when it is attached to the host machine.
From the VirtualBox Manager window, select the appropriate virtual machine.
Next, click the Settings icon or from the menu bar select Machine - Settings.
In the left navigation pane, select USB.
On the right-hand side under USB Device Filters, click the top USB plug icon (with a small blue circle).
Right-click the new entry under USB Device Filters and select Edit - Filter. At a minimum, I recommend providing a unique name in the Name field, along with the vendor ID in the Vendor ID field, and the product ID in the Product ID field. Feel free to fill out the other fields but understand that providing more information may cause issues if it is incorrect or not applicable. If you would prefer to be able to use any Kingston device attached to the host, then only provide the vendor ID in the Vendor ID field. Of course, you should also provide an appropriate name in the Name field so that you know that the filter is for all Kingston devices.
Note that creating a USB device filter automatically activates the filter (checked checkbox), meaning that in most instances the device will automatically connect to the guest machine when it is attached to the host machine. If this behavior is not desired, uncheck the checkbox next to the filter to deactivate the filter without deleting it. Additionally, if the USB device you are using is not USB 2, with the appropriate filter selected uncheck the Enable USB 2.0 (EHCI) Controller checkbox.
07 - STEP 03 - Manually Accessing USB Devices Connected to the Host Machine
I have encountered some instances where a USB device attached to the host machine is not automatically connected to the guest machine, even though the appropriate USB device filter has been created and is activated. If you run into this issue, then perform one of the following procedures:
a. Right-click the USB icon in the Mini ToolBar (lower right of the running virtual machine window) and then left-click the device you want to connect to the guest machine.
b. Select Devices - USB from the menu bar at the top left of the running virtual machine window and then left-click the device you want to connect.
If you want to connect a USB device which has been deactivated, then perform one of the recommended procedures above after connecting the device to the host machine.
================================================================================
My lack of understanding of bridged adapter functionality was the other issue that prevented me from being able to fully use Windows 7 Pro under VirtualBox for about two years.
The default network adapter setting when you create a virtual machine under VirtualBox is NAT (Networked Address Translation). This works fine if all you want to do is connect to the internet. However, what if you need to directly connect to a router to configure it, or what if you want to print wirelessly to a wireless printer? For situations such as these, you need to use the appropriate bridged adapter.
08 - STEP 01 - Selecting a Bridged Adapter
For the purposes of this how-to, we're going to assume that we will only be using one adapter. I have no experience using more than one adapter, so I'm unable to provide any advice about such usage.
From the VirtualBox Manager window, select the appropriate virtual machine.
Click the Settings icon in the icon bar or from the menu bar select Machine - Settings.
In the left navigation pane, select Network.
Under the Adapter 1 tab, click the Attached to list box field and select Bridged Adapter.
Click the Name list box field and select the appropriate wireless or ethernet adapter.
Start your virtual machine.
I'm unable to provide any advice about Advanced settings because I've never used them.
In addition to the aforementioned procedures, the network settings can also be changed as follows while the virtual machine is running:
a. Right-click the network icon (two blue squares with white borders) in the Mini ToolBar at the lower right of the virtual machine window and select Network Settings.
b. From the menu bar at the top left of the virtual machine window, select Machine - Settings.
c. From the menu bar at the top left of the virtual machine window, select Devices - Network - Network Settings.
================================================================================
Sources Consulted:
VirtualBox User Manual v4.3.14, available in PDF and HTML formats on the VirtualBox site on the main page.
Last edited by KrunchTime (2016-07-01 01:44:29)
Offline
Thanks for taking the time to move this guide over here KrunchTime, I am sure many will find this useful.
Offline
+1
Awesome effort!
Offline
Offline
Well worth a sticky!
Offline
@HoaS: You're welcome.
@ozitraveller: Thank you!
Offline
Just used this, very helpful. Thanks @KrunchTime
Offline
^ You're very welcome. I'm glad you found the info useful.
Offline
Good stuff Krunch, thanks ... btw: hope you've been well fellow nixer.
Been wanting to do this kinda thing. Windows 8.1 OS as guest. Though thanks to HOAS, lately been getting this nagging urge to install Openbsd onto a KVM vm. Have read the bsd's don't like to share a disk and no way I'm backing up and having to restore every other OS onto the system, or find another work around to try it out. Though sucker won't know it's sharing disk in a VM.
Sadly really don't think anything but bare metal installs can give someone a true picture of how an OS will perform. Though there are distro's specifically meant to support VM's and been playing around with the idea of making a custom install, that's tweaked especially for that purpose. So that the host OS is as minimal as poss. Atm just don't have the time to mess with that though.
Vll!
Last edited by BLizgreat! (2016-11-28 15:26:07)
Offline
^ You're welcome. I've had some health issues and still no job. Other than that, I'm doing okay. Running Windoze 8.1 in a VirtualBox VM on both of my machines here, although I hardly touch them except to perform OS and app updates. I'll borrow a phrase from Charlton Heston: "They can take my Linux when they pry it from my cold, dead fingers."
Last edited by KrunchTime (2016-11-30 09:21:42)
Offline
^Dang it man, sorry to hear the bad parts. Though glad you're still above ground. Never ceases to amazing me, how people who would obviously be good employee's have so much difficulty finding a freakin job nowadays. You're not alone, am between steady employment myself fellow nixer. Supposed to have one lined up but the employer is dragging feet atm. Maybe due to the holidays. Can't say in your area but in this city, many of the bigger employers exclusively only hire through temp agencies. Have you tried those ?
Mentioned planning on and encourage people to start something for themselves. Finding something that's realistic, either product or service you can provide and work for yourself. Plenty of people do it no reason we can't ... eventually.
Random babble story, when was working as a framer on a construction site, while everybody else was on lunch. Some old guy came up and asked me if he could take some of the scrap pieces out of the ever growing scrap pile. Told him sure, would've let the guy take some new boards. Didn't like the contractor I was working for anyway.
Out of curiosity asked him what he was going to do with it. He told me he makes birdhouses and sells them and said he was pocketing like 32thou a year doing it. Guy could check the public records for construction permits people are pulling and probably get most the materials free. Some basic wood working and paint tools. Finding an outlet off/online to sell the buggers and WHAM.
He was making more than I was busting arse in construction. Arghhhh but more power to him.
Yeah once in a blue moon will boot win8.1. Don't bother installing updates from M$ anymore. Been my experience updating from them w/o taking the time to investigate everything in detail can wind up leaving a door open for them to send junk down the pipe to people's systems that cause problems, rather than benefits.
Fact that's the way they got me with updating from win8 to 8.1 via an "update". Didn't want to ... kept telling the nag screen that popped up I didn't want to. Nope using win8 and pop-up out of nowhere. Summin like windows 8.1 installed successfully, rebooting. Arghhhhhh !
Went through the update history on the pc, googled a few of em and found the dang "update" they'd installed to stab me in the back. Which now they're wanting to "upgrade" everybody to win10 too. Though your/(the Krunch) solution would be a good way to prevent such M$ shennagans. Just make sure you make clones of window$.
Also gotta do it.
Seems like the way you're going about it will also much mitigate window$ security concerns Krunch. Though my personal opinion on the best way to secure a M$-OS ? You see that entry in your boot menu that says, xyz-Window$ OS ? Don't ever select it and you're good to go.
At the time was in a tech burn out phase, just wanted to use the fricken computer, w/o having to mess with it at all. When it comes to M$ that's something people may live to regret. After the above and some other issues, started actively watching what was going on. Window$ 8.1 was smashing my hardware quietly behind the scenes. Hadn't bothered to open up task manager to look or I'dve seen what was going on much sooner. Had a brandnew hdd burn out way prematurely due to M$'s default "optimizations". Boot up and it was keeping the disk and cpu ( a fairly beefy quadcore) blasting at 100% for several mins for no real reason. Of course they'd say that's to provide a snappier user experience or whatever bs excuse to justify their sleaziness.
On gnu/Nix, boot up, ... super brief time, cpu is happily idling at 99.8% free and of course gets to a usable desktop in the fraction of the time it takes window$. Lucky the drive was still under warranty at the time.(Sheesh gotta do it.) We had a long drawn out discussion about such things in #! forum, that being failure rate of system components like the diskdrive on M$ vs Nix and gnu/Linux is known to be much kinder and have drastically lower component failures compared to window$.
Personally think they do it on purpose, so people will buy a new system and send crappy "upgrades" down the pipe via installing updates too. That bog people OS's down, makes them buggy or slow or otherwise provides a poor user experience. Again so that people will decide it's time to upgrade. This old thing is so slow, let's buy a new comp hon. Of course with a M$-OS pre-installed by the OEM.
Remember Sector mentioning he had a failing drive on window$ that was about to give out, came over to gnu/Linux and believe he said that drive is still in use today. Hey Krunch, sorry about the off-topicness of this, just like letting people know such things. If this annoy's you in any way. Will remove the stupe babble.
VLL!
Last edited by BLizgreat! (2016-11-30 22:20:31)
Offline
^Dang it man, sorry to hear the bad parts. Though glad you're still above ground. Never ceases to amazing me, how people who would obviously be good employee's have so much difficulty finding a freakin job nowadays. You're not alone, am between steady employment myself fellow nixer. Supposed to have one lined up but the employer is dragging feet atm. Maybe due to the holidays. Can't say in your area but in this city, many of the bigger employers exclusively only hire through temp agencies. Have you tried those ?
About employers and hiring, this guy doesn't mince words about the real problem and it isn't lack of good employees:
http://www.asktheheadhunter.com/blog
I don't necessarily agree with some of his thoughts on getting hired. His methods will not work or are not applicable for many positions, IMO.
I've applied to some openings advertised through temp/placement agencies only to find out that they were fishing for candidates to add to their temp roster. IMO, they're just one rung above used car sales people. I refuse to even deal with them anymore.
It hasn't been lack of jobs that has prevented me from becoming employed. Nobody seems to be interested in me. Guess I'm too old and it's something that I'm not able to hide trying to get back into the field I used to work in over 17 years ago. I even have a degree in the field, honor society membership because of my grades, but that doesn't seem to matter.
I'm not interested in working for large corporations or the federal government because I hate the bureaucracy and political correctness and I know I'll end up getting fired. I refuse to kowtow to the LGBT agenda.
Yeah, I would love to find something that I could specialize in and possibly work for myself. I'm coming up mostly blank on ideas though and I'm not gifted that way.
As far as updating Windows 8.1, I do it but check the updates they want to install, except for the MS Office components. Weird thing about MS Office updates, I get updates for components I don't even have installed; e.g. Outlook, Access, Publisher, and whatever the project management software is called. Never been on my machine, but because I have MS Office installed, I get the updates...go figure.
Offline
I'll borrow a phrase from Charlton Heston: "They can take my Linux when they pry it from my cold, dead fingers."
That's gotta be the greatest mis-quote I've seen in a long time.
Good luck on the job hunt.
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
^ Greatest misquote
I need more than luck at this point. I've given up after almost 3 years of looking. Not sure what I'm going to do at this point.
Offline
OUCH! Things are tough all over.
Never give up, just take a 'pause that refreshes', some of the strangest things happen when least expected.
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline