Monday 21 May 2012

VMware Workstation 8.0.2 does not Work with uBuntu 12.04 LTS

Hi there ...

About some day ago, I have updated my system,

I'have created this post to share, the way I have troubleshoot and successfully update the Linux Kernel make VMware Workstation 8.0.2 work and Kubuntu 12.04..


Installing VMware 8.0.2 64bit
Ubuntu 12.04LTS 64bit BETA
My Kernel version is: 3.2.0-20-generic
pst007x@pst007x-Aspire-5741:~$ sudo sh VMware-Workstation-Full-8.0.2- 591240.x86_64.bundle
Installs ok
When I launch I am asked to install modules which are compiled and loaded into the running kernel.
A window opens
VMware Kernel Module Updater
This fails on Virtual Network Device
UPDATE:
When I try to add patch, following error:
 pst007x@pst007x-Aspire-5741:~$ sudo sh patch-modules_3.2.0.sh
 [sudo] password for pst007x: 
 patch-modules_3.2.0.sh: 27: [: workstation8.0.2: unexpected operator
 patch-modules_3.2.0.sh: 28: [: workstation8.0.2: unexpected operator
 Sorry, this script is only for VMWare WorkStation 8.0.2 or VMWare Player 4.0.2. 
 Exiting
 pst007x@pst007x-Aspire-5741:~$
I have fully un-installed, and re-installed. I am installing the correct version. Probably a problem with the patch. VMware installs perfectly on Ubuntu 11.10..
.. Here is how I've worked it out .. 

Move to Home folder

  1. VMware-Workstation-Full-8.0.2-591240.x86_64.bundle
  2. PATCH: patch-modules_3.2.0.sh
  3. PATCH: vmware3.2.0.patch
Patch download link (xtact contents to Home folder):

"root@mukonda:/home/malange/Downloads# sudo  sh VMware-Workstation-Full-8.0.2-i386.bundleExtracting VMware Installer...done.
No protocol specified
No protocol specified
No protocol specified
No protocol specified

You must accept the VMware OVF Tool component for Linux End UserLicense Agreement to continue.  Press Enter to proceed.
                                                
VMWARE OPEN VIRTUALIZATION FORMAT TOOL LICENSE AGREEMENTNotice to User:This Open Virtualization Format Tool ("OVF Tool") License Agreement is a ... "bla bla bla "


Here is the Ubuntu Terminal Log record ...

"root@kubata:/home/malange/Downloads# ./patch-modules_3.2.0.sh                                                                                                                
-bash: ./patch-modules_3.2.0.sh: Permission denied                                                                                                                                  
root@kubata:/home/malange/Downloads# ./patch-modules_3.2.0.sh                                                                                                                      
patching file vmnet-only/filter.c                                                                                                                                                   
patching file vmnet-only/netif.c                                                                                                                                                    
patching file vmnet-only/userif.c                                                                                                                                                   
Stopping VMware services:                                                                                                                                                           
   VMware Authentication Daemon                                        done                                                                                                         
   VM communication interface socket family                            done                                                                                                         
   Virtual machine communication interface                             done                                                                                                         
   Virtual machine monitor                                             done                                                                                                         
   Blocking file system                                                done                                                                                                         
Using 2.6.x kernel build system.                                                                                                                                                    
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'                                                                                                                      
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \                                                                                            
          MODULEBUILDDIR= modules                                                                                                                                                   
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/apic.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/task.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmnet-only/driver.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/hub.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/userif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/netif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/filter.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmnet module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/file.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/inode.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/module.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/super.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmblock module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/driverLog.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmci module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notify.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/stats.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/util.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/driverLog.o
  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vsock-only/vsock.mod.o
  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vsock module
Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                             done
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done
   Shared Memory Available                                             done


All done, you can now run .
Modules sources backup can be found in the '/usr/lib/vmware/modules/source-workstation8.0.2-2012-05-21-
kubata@kubata:/home/malange/Downloads# 
"

Now here it VMware Working ... :-) 

                                                                                             Snapshot 1....


Snapshot 2 ....




This is another posting showing "how to do computing" for everyday computer usages... For a general public

Thursday 19 April 2012

Introducting to XHTML and jQuery

Hi There ..

I am starting one project to get one of  our the pages on http://www.itechreload.co.uk/  to be more interactive.. I made a quick video showing what I want to achieve.. With a video hosted on youtube..

So, relax and watch it..




.. Please anything send me a comment please !! I need help to get this done!!

Wednesday 18 April 2012

I got stuck to on Oracle DataBase Developer apps

Dear Readers, 


Over a period of one entire, month I've being put off by Linux ubuntu 11.10, to install the sqldeveloper package. Every single time I've tried to do it, I got errors ... 


Today finally I managed to find the solution.. Someone had the same problem as me and posted a solution in one forum, so I followed their instructions and got mine working.. Thank you to this guy.. 


Really saved the day.. 


So, I decide to honour him and post his solution here. 


"Hi guys, just got a quick question: 

I need to install Oracle's SQL Developer since I need to use the program for a database unit at Uni. Anyway, if you've tried to use it before you'd realise that there is only a .rpm installer available for it (no .deb). So I tried to convert it to .deb using alien.  When I "sudo alien --scripts" the .rpm I get: error: incorrect format: unknown tag mkdir: cannot create directory `sqldeveloper-2.1.1.64.45': 


File exists unable to mkdir sqldeveloper-2.1.1.64.45: at /usr/share/perl5/Alien/Package.pm line 257.  
Basically, I'm asking, does anyone know what I'm doing wrong here? I've never used alien before since I've never had a need to convert a .rpm before. I also tried installing and running Java JDK and SQL Developer under Wine, but was unsuccessful with that as well :( Anyway, thanks for taking your time to read and (hopefully) help with this ;) 


Oh and I'm using Ubuntu 10.04 32bit, if that helps? 


; -->poltak July 22nd, 2010, 07:49 AM Ah, crud <-- [That's the name of the guy that created the post]
Managed to solve this problem with the help of another more-advanced-than-me linux user. 


Anyway, I'll write up how we got it sorted without needing to convert an rpm package to deb just so if anyone else has this same problem in the future and googles this or something... 
First make sure you have Java JDK installed. I used openjdk (open-source alternative to the official Sun Java jdk thingie). Download the "Oracle SQL Developer for other platforms" from the Oracle site (http://www.oracle.com/technology/software/products/sql/index.html)and then extract it into its own folder. 


Then in terminal, cd to the extracted directory and: sudo sh sqldeveloper.sh 
It'll ask you to type the pathname of your J2SE installation


Mine turned out to be "/usr/lib/jvm/java-6-openjdk". Then press enter and you should be right and it will boot up and work the exact same as it does under Windows or OS X. 


 Hopefully this helps another linux newbie out one day down the track :)"


This is the end result on my computer ..Finally working 
 :-)

Tuesday 27 March 2012

Data recovery walk through.. Guide How to !!


To recover files from a drive containing deleted files or folders, follow these steps:

Key Features:
  • Recover deleted files/folders even after recycle bin has been emptied or use of Shift+Del key.
  • File recovery from Missing or Lost folders.
  • Recognize and preserve long file names when restoring files & folders.
  • Multi-Disk Drive Support - Performs FAT/NTFS, EXT2/EXT3 recovery on all IDE, EIDE, SCSI and SATA disk devices.
1. Download EaseUS Data Recovery Wizard, install it and launch it. Click the "Deleted File Recovery" button on the main window of Data Recovery Wizard.
Data Recovery Software
2. Select the file types you want to recover. Tick 'Search all lost files automatically' to find all lost file types. Tick 'Ignore bad sectors' to skip bad sectors when scanning.
Select file types
3. You can see the list of all volumes found on your computer, select the exact drive and press the "NEXT" button to search. If you are familiar with file system details, you can change "Option" before pressing the "NEXT" button.
recover deleted files
4. Data Recovery Wizard will read file system on selected volume and search the files. This step may take some time depending on the size of disk space. You have to wait until scanning is finished.
recover deleted files
5. After this scanning is finished, you'll see file/folder tree.
Note: If you are not able to get the desired results after Deleted File Recovery, go back to home window and select the option "Complete Recovery" or "Partition Recovery".
recover deleted files
6. The "Search files" or "Find file by name" option makes finding the file you need much easier. You also can check the quality of the data in the container by the "File Preview" option.
recover deleted files
recover deleted files
recover deleted files
7. Select the files or folders that you want to recover and press the "NEXT" button.
recover deleted files
8. Select a directory and press the "NEXT" button to save the files.
Caution: Saving file(s) to the partition or drive where you are recovering data, for it may result in overwriting data and permanent data loss!
Please see "Deleted File Recovery" for more details.
The demo version of Data Recovery Wizard gives you a much fairer idea about chances of data recovery from your hard disk before deciding upon the purchase.

Secure Your Azure DevOps Pipeline: GitHub Advanced Security to the Rescue

  Stop Shipping Your Passwords to Production: How GitHub Advanced Security for Azure DevOps Saves the Day (and Your Reputation) Let's fa...