It's official.
I have now returned my second Micro (due to hard dri've locking up after owning it for 2 weeks) and am getting an Ipod Nano tonight. Just too many issues discussed on here with the Micro's durability. I've enjoyed reading this board. Hope you all have better luck than I have had.
mhayward259 wrote:
Well Volrus, i reckon you made a good move. As you say just too many problems with Creative Products.
And as I keep saying, Apple have problems also and no-one knows for sure what the relati've difference is between any of the manufacturers.
SSR seems to answer 90% of the Posts here, and he luvs Creative stuff as he keeps tellin us
When exactly have I been saying that I love Creative stuff? Got a link?
I'm here to help people, you should try it.
but one day he will realise - Just too many problems, people are voting with their feet and taking their money elsewhere. One day in the future he may just be the only one left answering his own problems lmao.
Why can't you try doing something constructi've? For starters we have iPod users coming here who are sick and tired of failing iPods. Or are you just an iPod Zealot who can't stand the truth?
If you can't offer something useful to the forum (which you haven't so far) best to go elsewhere.
Similar Messages
-
At the risk of sounding like CL official and/or brown nose. l
To start I mean no dissrespect to anyone in any way or form, but how the hell is it possiable that anyone can have issues with their Creative cards?
I mean Look at the stickies. Pretty much every know issues is covered and every possible set up option is there for you.
The day I bought my Audigy 2 ZS, about a year or more ago the only issue i had was 5. sound in Movies. After 2 seconds of reading the FAQ it was solved and the card ran perfectly for the entire time i had it. I have sold that card now and the guy I sold it to had zero issues also.
I have got my self an X-FI Platnium. Now before i got the card i spent some time reading the FAQ and researching the card for all possiable issues I may encounter. From the moment i put the card in to the moment the last application was installed to the final re-boot i've had not issue what so ever. the card works flawlessly.
Now, again no dissrespect to those having issues but why blame CL? Why not take the time and look over your system. ENSURE ALL componants are of high quality. You cant use generic RAM on a high end board with no name power surrplies and have fans all over the place, plus running firewalls, Anti virus, other programmes in the background, old bios, old drivers, messy Windows install, crowed desktop, fancy tools running, every possiable USB port acti've, firewire cards, TV cards and the expect everything to run fine.
Take note that PCs are not and have never been designed to run games. Sure the hardware is but the software is not and never will be until Bill Gates is dead and then the dorr is open for a better running OS that allows games to run without all the over heads of Windows not to mention other apps like Firewalls and Antivirus.
Simply put, if you really want to play games and have them run at their best, keep your syste, simple, but still high end enough to run games.
EG. You dont need TV cards, firewire cards, Firewalls, Anti-virus, more than 3 USB devices ( mouse, K/B and Pad ) You dont need anything in startup programmes to run games.
Also, low end hardware = crashes - BSOD and all other kinds of issues. Dont skimp on hardware. You want to play games right? Spemd the cash and get the best RAM, get a top high end board. Dont use cheap leads and for the love of god get a GOOD, nah get the BEST POSSIABLE PSU you cant.
Keep your system clean from dust.
Clean temps files EVERY day.
Defrag and scan disc everyday.
Set ALL antivirus to manual in services.msc and only run it when you want to.
Forget firewalls. Just because your firwall may block a few things dont mean the other million or so bots are not getting in looking for numbers. Ive never used a firewall and see, well whats the point? if a hacker really wants in hwe will get in plus if you dont store credit card numbers and use your credit card online then who cares.
The latest drivers are not always the greatest. Not just for sound but for everything.
Anyway, i could go on for days but ill leave it there and hope that some of you understand my point.
Why blame CL all the time? Your other hardware parts, even a modem, yep a simple PCI modem can cause all kinds of crazy things so look it over.
Is you mainboard a GOOD brand ? Asus - Abit ?
Ram.
HDD.
Cable and leads old?
Dusty?
Power Surrply unit's Just because it says 450 watt dont mean that its good enough. YOU MUST HAVE THE RAILS AT THE REQUIRED VOLT ALL THE TIME. A single drop and thats it, crash.
Too many fans hogging amps?
Too many Driver hogging volts?
FDD, bah, dont need on so remove it.
MAIN BOARD BIOS SET UP right?
Look at your hardware, stripe it down a bit. IF you really need TV cards and firewire and stuff. build cheap PC for that job and keep your Gaming PC clean and free.
I for one highly reconmend Creative sound to anyone i build a PC for simply because they are the best. You just need to spend the time and cash and get your system balenced, keep it tidy and junk free, spend a few days trying out different driver combo's until it hits the sweet spot.
All the best.Pretty much all I got out of your post was a pro CL fanboy rant. I'm glad your card works for you. Do all XFI owners have problems? No. Do some have problems? Yes.
You said:
"but how the hell is it possible that anyone can have issues with their Creative cards? "
Are you for real? Is it not possible to have problems with Creative cards, no matter how much time you put into trying to get it to work? If you had the scp issue, you would understand. You would try everything possible to get it fixed. In the end, if it still puked out the scp, you would not have posted this topic and ended up disgruntled like many of us. Do you not think CL support try's to walk people through many of the things you posted to try to fix it's Should half the stuff you posted be listed on the box as a warning so Jim Johnny down the block does'nt make a mistake by buying it to put in his year old Dell, HP or whatever?
PS, you did risk it and it is official!
Message Edited by powerstroke on <SPAN class=date_text>08-23-2006 <SPAN class=time_text>04:08 PM
Message Edited by powerstroke on 08-23-2006 04:5 PM -
Official PlayBook OS v2.0.1.668 Announcement and Breathing Life back into a Dead Battery
Where is it?!
Well, you can go to the software update page and discover that the only thing RIM indicates the update does is provide a security update for the Adobe Flash player,
http://ca.blackberry.com/support/tablets/playbook/software-updates.html
The details can be found here.
http://btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB31675&sliceId=1&cmd=displayKC&d...
That said, it would appear speculation related to wifi and browser improvements (among other things) is very subjective and likely as varied as individual user experience. Here’s a quote from a Crackberry News & Rumours Post
http://crackberry.com/whats-new-playbook-os-201668
Frankly, this sort of commentary drives me crazy. What company would make the kind of improvements identified above without documenting them for their existing and future customers, if they were real. Is it that we're all so desperate for good news from RIM that we have to make it up? If anyone can find anything official behind the article's claims, feel free to post a link in response.
A couple things do still confuse me though. Some users are claiming that the new OS v2.0.1.668 version has been pulled. My Playbook upgraded to this update without any issue on the first try. Didn't take hours and the whole process seemed quite normal. Smooth as molasses.
Didn't notice anything weird at all until last evening, a few days after the upgrade. I pulled off the charger cable and looked at the battery and it was 0%, dead as a door nail. Perhaps the magnetic head of the fast charger wasn't seated properly. I turned off the Playbook and then attached the fast charger. Left it alone and went back about an hour later and it was still at 0%! It was acting like it was still losing charge and getting weaker. This is not typically the case, so I shut down wifi, turned off backlighting, put it into airplane mode and tried again. No change when I checked back later. At some points, I couldn't even get it to boot to the main screen, just battery empty symbol, at best.
I read on this and other forums how others were having problems after teh update. Erasing their Playbook and reloading OS. I couldn't even do that, because the Playbook has to have enough power to update the software through the Desktop. While I could connect and see the device via Desktop, there wasn't enough juice to do anything at 0%. It seemed that there were folks holding the battery button for 10-20 seconds claiming that worked, but it didn't do anything for me.
To say the least, I was getting pretty ticked off after reading the forum and discovering that the battery issue I was dealing with might be related to a pulled OS upgrade that had screwed my Playbook. Proper QA and testing should preventthis sort of blunder. Even more ticked, if the update has been pulled and RIM has not made any official statement that I can find to that effect! If they have pulled it (which I still haven't been able to personally confirm), this information should be publically available and explained. The one thing they need to do is look after any loyal customers they still have left. Personally, I have loved my playbook, although RIM has definitely botched a great piece of hardware with inadequate software enhancements to the OS, that continues to this day. The fact that we still can't categorize browser favorites in folders at this point is inexcusable. Anyway, I digress.
Back to the battery. Here's what I did after about two hours of snarling and becoming increasingly frustrated with my dead playbook and not being able to find any way to breathe life back into it. I remembered what happens to my rechargeable batteries for my xbox controllers when they drain dead. They simply won't charge. They become un-rechargeable. I eventually figured out via an obscure internet posting, what no retail clerk or xbox support person seemed to know. I returned more than my share of brand new unrechargeable batteries, because they wouldn't charge when drained. This is what I discovered. You take the dead controller with battery and connect it to the charging cable. It lights red... but after 13 seconds it goes green. If you leave it connected it simply will not charge. Originally, I concluded I had a faulty battery that would not recharge. Not so. You must pull the cable off. Light goes out, connect it again. Light goes red, 13 seconds turns green. Pull the cable off. Light goes out, connect it again. Light goes red, 13 seconds turns green. Pull the cable off. Light goes out, connect it again. Light goes red, 13 seconds turns green. Pull the cable off. Repeat until you figure there is no point to this exercise, and then do it one more time. Pull the cable off. Light goes out, connect it again. Light goes red, 13 seconds later it stays red and doesn't go green, it stays red. Might be the 5th try, 20th try, 30th try, who knows, but eventually the xbox controller light will actually stay red and not switch to green and will then recharge. It's almost like each previous failed connection provides a bit more juice to the battery, until it has enough to finally be rechargeable again. Come back in a couple hours and what appeared to be an unrechargeable battery is fully charged.
So I took my Playbook, Turned it off. Connected cable. Light turned red, then turned green. Disconnected cable. Held power button to shut playbook off. Connected cable. Light turned red, then turned green. Disconnected cable. Held power button to shut playbook off. Connected cable. Light turned red, then turned green. Disconnected cable. Held power button to shut playbook off. Connected cable. Light turned red, then turned green. Disconnected cable. Held power button to shut playbook off. Not sure how many times I went through this painful exercise. Maybe 15-20. Maybe I only needed to do it 5 or 10times. Maybe I didn't need to do it at all.
Frankly, in the course of doing it, it seemed like I was almost draining the battery more. I think there was a point where it almost was dead and wouldn't even light up. That had me spooked. By pressing and holding the on button and connecting the cable, I somehow got the red light to come on, then switch to green and it began pulsating. At this point, I didn't want to push my luck. Left it alone and went to bed. Got up this morning and it was alive and 100% charged. It went into an automatic reboot. The wifi password had to be re-entered and saved in order to get connected back to the internet, but everything else seemed to be fine.
I’ve used it solid for one hour and the battery dropped to 80%. This felt like a much faster drop than in the past. It's been in standby mode for an additional two and a half hours since and it is now at 60%. I never shut my PlayBook off. I keep mine in standby all day, with the screen on lowest brightness and wifi typically on. Do I think that the latest update has had an impact on battery life? Well, my Playbook originally died and ran out of charge, when I had it attached to the fast charger! Can't explain that right now. I suppose I could have improperly connected via the magnet and this was my own user error. Could be just coincidental that this happened to me after the update and at the same time others are complaining about battery issues. Personally, it does “feel” like my Playbook is draining faster in standby mode than it has in the past. I have my eye on this and if it goes dead again, I'll repost. Obviously, my recharging "technique" worked for me, so if it helps breathe life back into your battery dead playbook, I'd be interested to know.
If RIM has actually pulled the update and not updated their own web site to reflect a battery issue and not officially disclosed a known problem to their customers it would be at best totally unprofessional and at worst inexcusable. I'm still not sure what to make of everyone's comments and issues, when RIM still lists the v2.0.1.668 update on their corporate page.
gRIMace
Solved!
Go to Solution.RIM exec Michael Clewley confirm that 668 was pulled because it has upgrading issues with Playbook with OS 1.0.7 --- and that is the ONLY reason why it was pulled.
http://twitter.com/michaelclewley -
Is office 2010 officially supported on windows server 2012 R2
hello,
can someone tell me if office 2010 is officially supported on windows server 2012 R2 RDS?
This link only talks about Windows server 2012 not R2.
Thanks in advance.
Regards
AnthonyHi Anthony,
I successfully installed Microsoft Office Professional Plus 2010 on Windows Server 2012 R2 before in my testing environment.
So yes, Office 2010 is supported on Windows Server 2012 R2.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs. -
Downloaded new iOS for iPhone 5. Now the handset is running hot, keeps freezing on different screens, won't charge on official charger ( only charges on crap poundland one) and battery is loosing 1% every two minutes! I've closed all apps and reset the complete phone but no luck. Any one know what else I can try apart from a new phone?
I have done a factory reset at 45% battery. After the reset it's still hot and at 35% now
-
My iPhone 4S lost its official permanent SIM unlock
Hi,
I've had my iPhone 4S officially unlocked by my carrier (Orange France) through Apple.
As instructed by Apple, I restored it in order to fully unlock it. Restoring it is supposed to make the unlock permanent therefore bypassing the need for activation when using different sims.
This worked perfectly until last week (I traveled to the UK and Brazil and used local prepaid cards without having to re-activate it) when I tried using a brand new French Free Mobile sim card. To my surprise, I had to re-activate this iPhone using a wifi connection. This shouldn't have happened as the iPhone had been fully and permanently unlocked by restoring it (iTunes confirmed this after the restoration).
Now, I have to reactivate it every time I want to use a different carrier sim card as if it had lost its permanent unlock.
Activation on a SIM basis works using wifi BUT I shouldn't have to go through this. It looks like the iPhone lost its permanent sim unlock. This is very frustrating. It might not seem like much of a trouble but it is. For instance, when flying to a foreign country, if I want to switch sim cards in the plane, I won't be able to activate the iPhone without wifi connectivity which forces me to "hunt" for a wifi hotspot after landing in order to be able to use my iPhone.
There are many reports of French users having issues with Free sims with either activation or unlock.
My question is simple: if I restore once again my iPhone, how can I be sure the permanent unlock will stay that way if I use a Free Mobile sim card?
Will this problem be fixed soon?
In addition, switching sim cards in a plane is problematic with current firmwares as, when switching sims in a non-permanently unlocked iPhone, wifi is automatically turned on in order to try and activate it without the user actively choosing to do so. So many people will end up having wifi on in a plane when regulation prohibits it.http://support.apple.com/kb/TS3198
Ps
You are not addressing Apple here this is a User to User technical help community
Apple host and Mod but do not monitor -
So it happens that since Lion and now, of course, Mavericks, the DVI to Video/S-Video support is not only unsupported, but crashes your 2008 Macbook Pro (MacbookPro3,1, 15 inch) if you plug the official adaptor in. The screen went with artifacts and the computer needed a hard reset.
What happened after that is that the computer wouldn't start. Of course I immediately did SMC and PRAM resets without results. No leds, no start chime, nothing. Only method found was to bypass the SMC (which is done via holding de power button with battery/power cord unplugged, then plugging power cord still holding it, releasing, and pressing it again). Everything is then ok except, of course, everything controlled by the SMC (no battery, leds, fans at full speed). Did Apple's Hardware Check, full test, no errors found. Reflashed manually the SMC via an EFI Shell, as found on the internet: the SMC is in "U" mode and can't be correctly reflashed. After that, I unmounted the logic board looking for any kind of corruption; found nothing.
In resume, did everything I could for a week. The last thing I found out is that plugging the adaptor itself, without connecting to any external device (no TV), still crashes the screen with artifacts. I beleive this has to do with the adaptor having inside some chips, since it's function is not to rewire cables, but to convert one signal to another. What happens after that and a hard-reset again, and after that hard reset the now installed rEFIt screen doesn't appear, so I believe that, effectively, connecting the adaptor affects your computer's boot system somehow.
I know Apple doesn't support computers old as these anymore, and I don't even care they quit the Video-out support with their new free OS, but if by doing that you enable your own official 20-30€ adaptor to kill an otherwise fully functional Macbook, that's foul play.
Any advice will be greatly received. Thanks for reading.Forgot to mention that the DVI adaptor works ok if plugged to a DVI monitor, so it's not a physical problem from the DVI output plug.
-
I can't reply on the official 7.0 topic so I'll ju...
Your forums suck as much as your new client. Nothing works as it's supposed to. When you need help, it's nowhere to be found. Was looking for an email address or live chat to ask help with my problem but right now I can't even remember what the problem was... I'm so pissed at this thing you call "help" on your website. It might be worth reading if you haven't tried turning it off and on again. Other than that it's worthless.
So... after trying to find a proper answer to the problem I was having with Skype, I came here and tried replying to an "official post" about this version of Skype... No dice! "LOL YOU CAN'T REPLY TO AN OFFICIAL POST BUT YOU CAN START YOUR OWN, MMKAY?! =8-D"
If you want to alienate your old users then keep doing what you're doing. If not, get your act together. I'm not one to accept bull**bleep** from anyone. Facebook hasn't got me and neither will you if you keep up with this BS.
<EDIT>
<QUOTE>
If you are a Skype customer, you can contact live chat support as follows:
Sign in with your Skype Name and password.
Select the topic you need help with and the problem you’re having. Some information that might help with your problem is displayed.
If the information doesn’t help, click Next.
Select your contact method.
You will see an option to request chat support. Click Text chat support.
</QUOTE>
So, I'm a customer or at least I thought so. Where is this "Next" button I'm supposed to click? I don't see it... Not after I "selected my topic", not before it. Please do send me some instructions! Never had such problems finding one button on a website!
WAIT! I finally found it behind 10 different links! YAY! All I need is to login with my Live account! Umm... WHAT? I'm already logged in with my Skype account when trying to find help and now you want me to login with a Live account to get ACTUAL help... You got to be kidding me...
</EDIT>
With best regards,
Someone heading back to IRC & VentriloI have what would probably be the same problem. While I can read official threads just fine, the big green "Reply" button is greyed out. Made a forum account just to post my suggestion, too. >.< Anyways...
Could someone post this next bit in the "7.0 and your feedback on the new chat UI" thread for me, please, since it won't let me even make a reply there?
"I would suggest adding a toggle for Classic and Enhanced modes to the View menu. Classic mode is the old interface, Enhanced is the new one. Text formatting is available in both modes, and new features are added to both modes as they're introduced, in the style appropriate to the mode. Enhanced mode keeps the new 'compact' settings, and allows you to play around with them more to further customise the interface, possibly even going as far as allowing you to rearrange each pane's features as you see fit. Overall, enhanced is designed more for mobile and/or touchscreen systems (but gives you room to play around with the interface and customise it for any system), while Classic is intended for desktops & laptops." -
Open-vm-tools/official vmware tools not installing.
I'm trying to install the latest offical vmware tools (16/9/2013) and open-vm-tools but both seem to always fail. I tried some of the patches listed on the wiki, but nothing got me anywhere. The big thing I'm trying to accomplish is to be able to use vmhgfs but, I'd like to have all the tools if possible. Here is what I did.
Open Vm Tools
#[root@localhost] - [14-01-01 18:09:33] - [/home/toxicarrow/Documents/firewall] - [R:0]
pacman -S open-vm-tools open-vm-tools-dkms
resolving dependencies...
looking for inter-conflicts...
Packages (2): open-vm-tools-5:2013.09.16-5 open-vm-tools-dkms-5:2013.09.16-5
Total Installed Size: 8.21 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [#####################################################################################################################] 100%
(2/2) checking package integrity [#####################################################################################################################] 100%
(2/2) loading package files [#####################################################################################################################] 100%
(2/2) checking for file conflicts [#####################################################################################################################] 100%
(2/2) checking available disk space [#####################################################################################################################] 100%
(1/2) installing open-vm-tools [#####################################################################################################################] 100%
>>>
>>> You can mount VMware Shared Folders via:
>>> mount -t vmhgfs .host:/ /mnt/hgfs
>>>
>>> or by adding this line to /etc/fstab:
>>> .host:/ /mnt/hgfs vmhgfs defaults 0 0
>>>
Optional dependencies for open-vm-tools
gtkmm [installed]
libnotify [installed]
libxtst [installed]
fuse [installed]
libsm [installed]
open-vm-tools-modules: for linux kernel
open-vm-tools-dkms: for linux-lts and other kernels [pending]
netctl: suspend-resume network state [installed]
networkmanager: suspend-resume network state
(2/2) installing open-vm-tools-dkms [#####################################################################################################################] 100%
>>> Enable building of open-vm-tools modules:
>>> $ dkms add open-vm-tools/2013.09.16
>>>
>>> Enabling vmxnet driver in /usr/lib/modprobe.d/open-vm-tools-modules.conf
>>> (this will disable pcnet32 driver)
>>>
>>> If vmxnet driver doesn't handle your NIC, you have to manually
>>> disable loading of pcnet32 driver
>>>
#[root@localhost] - [14-01-01 18:09:47] - [/home/toxicarrow/Documents/firewall] - [R:0]
pacman -S open-vm-tools-modules
warning: open-vm-tools-dkms-5:2013.09.16-5 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (1): open-vm-tools-dkms-5:2013.09.16-5
Total Installed Size: 5.57 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#####################################################################################################################] 100%
(1/1) checking package integrity [#####################################################################################################################] 100%
(1/1) loading package files [#####################################################################################################################] 100%
(1/1) checking for file conflicts [#####################################################################################################################] 100%
(1/1) checking available disk space [#####################################################################################################################] 100%
(1/1) reinstalling open-vm-tools-dkms [#####################################################################################################################] 100%
>>> Enable building of open-vm-tools modules:
>>> $ dkms add open-vm-tools/2013.09.16
>>>
#[root@localhost] - [14-01-01 18:10:14] - [/home/toxicarrow/Documents/firewall] - [R:0]
dkms install -m open-vm-tools -v 2013.04.16 -k $(uname -r)
Error! Could not find module source directory.
Directory: /usr/src/open-vm-tools-2013.04.16 does not exist.
#[root@localhost] - [14-01-01 18:13:14] - [/home/toxicarrow/Documents/firewall] - [R:2]
dkms install -m open-vm-tools -v 2013.09.16 -k $(uname -r)
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.12.6-1-ARCH VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmblock; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmci; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmhgfs; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmsync; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmxnet; make VM_UNAME=3.12.6-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vsock........
Error! Build of vmblock.ko failed for: 3.12.6-1-ARCH (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
#[root@localhost] - [14-01-01 18:13:45] - [/home/toxicarrow/Documents/firewall] - [R:7]
Official Tools
Before patches
#[root@localhost] - [14-01-02 2:40:49] - [/home/toxicarrow/vmware/vmware-tools-distrib] - [R:32]
./vmware-install.pl
A previous installation of VMware Tools has been detected.
The previous installation was made by the tar installer (version 4).
Keeping the tar4 installer database format.
You have a version of VMware Tools installed. Continuing this install will
first uninstall the currently installed version. Do you wish to continue?
(yes/no) [yes]
Uninstalling the tar installation of VMware Tools.
Stopping services for VMware Tools
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface socket family: done
VM communication interface: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
The removal of VMware Tools 9.6.1 build-1378637 for Linux completed
successfully.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/usr/bin]
What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc/init.d]
What is the directory that contains the init scripts?
[/etc/init.d]
In which directory do you want to install the daemon files?
[/usr/sbin]
In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]
In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
The installation of VMware Tools 9.6.1 build-1378637 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
Initializing...
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
VM communication interface socket family: done
VM communication interface: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
sh: : command not found
sh: : command not found
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Searching for GCC...
Detected GCC binary at "/bin/gcc".
The path "/bin/gcc" appears to be a valid path to the gcc binary.
Would you like to change it? [no]
Searching for a valid kernel header path...
Detected the kernel headers at "/lib/modules/3.12.6-1-ARCH/build/include".
The path "/lib/modules/3.12.6-1-ARCH/build/include" appears to be a valid path
to the 3.12.6-1-ARCH kernel headers.
Would you like to change it? [no]
make: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-lyoMIO/vmci-only/driverLog.o
LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-lyoMIO/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-lyoMIO/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-lyoMIO/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-lyoMIO/vmci-only'
make: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-VlEWPD/vmci-only/driverLog.o
LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-VlEWPD/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-VlEWPD/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-VlEWPD/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-VlEWPD/vmci-only'
make: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/util.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-VlEWPD/vsock-only/driverLog.o
LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-VlEWPD/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-VlEWPD/vsock-only/vsock.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-VlEWPD/vsock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory '/tmp/modconfig-VlEWPD/vsock-only'
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
make: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-C1YUSD/vmci-only/driverLog.o
LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-C1YUSD/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-C1YUSD/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-C1YUSD/vmci-only'
make: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/message.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/request.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/link.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/module.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/file.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/super.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/page.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-C1YUSD/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-C1YUSD/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory '/tmp/modconfig-C1YUSD/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[yes]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.14.5
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
VM communication interface socket family: failed
Guest filesystem driver: failed
Mounting HGFS shares: failed
VMware User Agent: done
Guest operating system daemon: done
Unable to start services for VMware Tools
Execution aborted.
After patches
#[root@localhost] - [14-01-02 2:44:39] - [/home/toxicarrow/vmware] - [R:0]
git clone https://github.com/rasa/vmware-tools-patches.git
Cloning into 'vmware-tools-patches'...
remote: Reusing existing pack: 134, done.
remote: Total 134 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (134/134), 22.06 KiB | 0 bytes/s, done.
Resolving deltas: 100% (74/74), done.
Checking connectivity... done.
#[root@localhost] - [14-01-02 2:44:55] - [/home/toxicarrow/vmware] - [R:0]
ls
= VMwareTools-9.6.1-1378637.tar.gz manifest.txt* run_upgrader.sh vmware-tools-distrib/ vmware-tools-patches/ vmware-tools-upgrader-32* vmware-tools-upgrader-64*
#[root@localhost] - [14-01-02 2:44:57] - [/home/toxicarrow/vmware] - [R:0]
cp VMwareTools-9.6.1-1378637.tar.gz vmware-tools-patches
#[root@localhost] - [14-01-02 2:45:13] - [/home/toxicarrow/vmware] - [R:0]
cd vmware-tools-patches
#[root@localhost] - [14-01-02 2:45:17] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
ls
LICENSE VMwareTools-9.6.1-1378637.tar.gz patch-module.sh* patches/ untar-and-patch-and-compile.sh*
README.md download-patches.sh* patch-modules.sh* untar-all-and-patch.sh* untar-and-patch.sh*
#[root@localhost] - [14-01-02 2:45:18] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
./untar-and-patch-and-compile.sh
=== Patching ./VMwareTools-9.6.1-1378637.tar.gz ...
--- Applying vmci/vmware9.k3.8rc4.patch ...
patching file linux/driver.c
Hunk #1 FAILED at 124.
Hunk #2 FAILED at 1750.
Hunk #3 FAILED at 1978.
3 out of 3 hunks FAILED -- saving rejects to file linux/driver.c.rej
--- Applying vmhgfs/vmhgfs-uid-gid-kernel-3.12-tools-9.6.1.patch ...
patching file file.c
patching file filesystem.c
patching file fsutil.c
patching file inode.c
Hunk #1 succeeded at 514 (offset -3 lines).
Hunk #2 succeeded at 617 (offset -3 lines).
Hunk #3 succeeded at 1216 (offset -3 lines).
patching file shared/compat_cred.h
--- Applying vmhgfs/vmhgfs-d_count-kernel-3.11-tools-9.6.0.patch ...
patching file inode.c
Hunk #1 succeeded at 31 with fuzz 1.
Hunk #2 FAILED at 1893.
Hunk #3 FAILED at 1946.
2 out of 3 hunks FAILED -- saving rejects to file inode.c.rej
--- Applying vmhgfs/vmware9.compat_mm.patch ...
patching file shared/compat_mm.h
Hunk #1 FAILED at 91.
Hunk #2 FAILED at 100.
2 out of 2 hunks FAILED -- saving rejects to file shared/compat_mm.h.rej
--- Applying vmhgfs/patch_inode.c.patch ...
patching file inode.c
Hunk #1 FAILED at 1798.
Hunk #2 FAILED at 1818.
2 out of 2 hunks FAILED -- saving rejects to file inode.c.rej
--- Applying vmblock/vmblock.3.11.patch ...
patching file linux/file.c
--- Applying vmblock/vmblock.3.10.patch ...
patching file linux/control.c
Creating a new VMware Tools installer database using the tar4 format.
Installing VMware Tools.
In which directory do you want to install the binary files?
[/usr/bin]
What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc/init.d]
What is the directory that contains the init scripts?
[/etc/init.d]
In which directory do you want to install the daemon files?
[/usr/sbin]
In which directory do you want to install the library files?
[/usr/lib/vmware-tools]
The path "/usr/lib/vmware-tools" does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]
In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]
The path "/usr/share/doc/vmware-tools" does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]
The installation of VMware Tools 9.6.1 build-1378637 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: "/usr/bin/vmware-uninstall-tools.pl".
Before running VMware Tools for the first time, you need to configure it by
invoking the following command: "/usr/bin/vmware-config-tools.pl". Do you want
this program to invoke the command for you now? [yes]
Initializing...
Making sure services for VMware Tools are stopped.
Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: done
Unmounting HGFS shares: done
Guest filesystem driver: done
Stopping Thinprint services in the virtual machine:
Stopping Virtual Printing daemon: done
sh: : command not found
sh: : command not found
make: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-HrsGw6/vmci-only/driverLog.o
LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-HrsGw6/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-HrsGw6/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-HrsGw6/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-HrsGw6/vmci-only'
make: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-pVUBEq/vmci-only/driverLog.o
LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-pVUBEq/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-pVUBEq/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-pVUBEq/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-pVUBEq/vmci-only'
make: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/af_vsock.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/vsockAddr.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notifyQState.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/util.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/stats.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/linux/notify.o
CC [M] /tmp/modconfig-pVUBEq/vsock-only/driverLog.o
LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-pVUBEq/vsock-only/vsock.mod.o
LD [M] /tmp/modconfig-pVUBEq/vsock-only/vsock.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-pVUBEq/vsock-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory '/tmp/modconfig-pVUBEq/vsock-only'
The module vmxnet3 from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module pvscsi from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The module vmmemctl from this package is not supported for kernels >= 3.10.
Please enable this module in your kernel. You may also have to enable
HYPERVISOR_GUEST.
The VMware Host-Guest Filesystem allows for shared folders between the host OS
and the guest OS in a Fusion or Workstation virtual environment. Do you wish
to enable this feature? [yes]
make: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/driver.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/linux/vmciKernelIf.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDriver.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciResource.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciContext.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDatagram.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciHashtable.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciEvent.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQueuePair.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciDoorbell.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciQPair.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/common/vmciRoute.o
CC [M] /tmp/modconfig-ukgHfB/vmci-only/driverLog.o
LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ukgHfB/vmci-only/vmci.mod.o
LD [M] /tmp/modconfig-ukgHfB/vmci-only/vmci.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmci-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory '/tmp/modconfig-ukgHfB/vmci-only'
make: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
Using 2.6.x kernel build system.
/bin/make -C /lib/modules/3.12.6-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-3.12.6-1-ARCH'
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoorGcc64.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/message.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/request.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/filesystem.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpName.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dentry.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/rpcout.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsUtil.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/stubs.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsEscape.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/link.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/transport.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/module.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/file.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/super.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmci.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/bdhandler.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/dir.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/fsutil.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLinux.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/hgfsBd.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/page.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/backdoor.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/inode.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/cpNameLite.o
CC [M] /tmp/modconfig-ukgHfB/vmhgfs-only/kernelStubsLinux.o
LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.mod.o
LD [M] /tmp/modconfig-ukgHfB/vmhgfs-only/vmhgfs.ko
make[1]: Leaving directory '/usr/src/linux-3.12.6-1-ARCH'
/bin/make -C $PWD SRCROOT=$PWD/. \
MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
cp -f vmhgfs.ko ./../vmhgfs.o
make: Leaving directory '/tmp/modconfig-ukgHfB/vmhgfs-only'
The vmxnet driver is no longer supported on kernels 3.3 and greater. Please
upgrade to a newer virtual NIC. (e.g., vmxnet3 or e1000e)
The vmblock enables dragging or copying files between host and guest in a
Fusion or Workstation virtual environment. Do you wish to enable this feature?
[yes]
NOTICE: It appears your system does not have the required fuse packages
installed. The VMware blocking filesystem requires the fuse packages and its
libraries to function properly. Please install the fuse or fuse-utils package
using your systems package management utility and re-run this script in order
to enable the VMware blocking filesystem.
VMware automatic kernel modules enables automatic building and installation of
VMware kernel modules at boot that are not already present. This feature can be
enabled/disabled by re-running vmware-config-tools.pl.
Would you like to enable VMware automatic kernel modules?
[no]
Detected X server version 1.14.5
Distribution provided drivers for Xorg X server are used.
Skipping X configuration because X drivers are not included.
Warning: This script could not find mkinitrd or update-initramfs and cannot
remake the initrd file!
Checking acpi hot plug done
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: done
VM communication interface: done
VM communication interface socket family: failed
Guest filesystem driver: failed
Mounting HGFS shares: failed
Guest operating system daemon: done
Unable to start services for VMware Tools
Execution aborted.
#[root@localhost] - [14-01-02 2:46:53] - [/home/toxicarrow/vmware/vmware-tools-patches] - [R:0]
Any idea what I should be doing?I have the same problem on ESXI 5.5 for over a month now, tried the patches, tried the LTS kernel which others say results in an immediate result without patches, nothing seems to work and nobody seems to be able to offer a solution.
Did you make any progress ??
Error! Build of vmblock.ko failed for: 3.10.25-1-lts (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/open-vm-tools/2013.09.16/build/ for more information.
make[2]: *** No rule to make target '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/linux/inode', needed by '/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock/vmblock.o'. Stop.
Makefile:1224: recipe for target '_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock' failed
make[1]: *** [_module_/var/lib/dkms/open-vm-tools/2013.09.16/build/vmblock] Error 2
make[1]: Leaving directory '/usr/src/linux-3.10.25-1-lts'
Makefile:120: recipe for target 'vmblock.ko' failed
Last edited by crankshaft (2014-01-10 11:32:32) -
With my i phone 4 , the Push notifications doesn't work for apps like (fb viber , whatsapp etc ) it only works for the official apps like message even when im using the phone, has this probleme with the iOs 6.0.1 and also with the iOs 6.1
This isn't an issue. Notice the screen prior to the one that shows usage has an iCloud section and a Manage Storage button. For this button to activate ios needs to download a few kb from icloud. Switching back to this screen forces ios to download those few kb.
-
Despite requesting several times through iforgot, I have not received any email from Apple support on my official email address.
try this...
Apple ID: Contacting Apple for help with Apple ID account security
ÇÇÇ -
can i use some other company's locked iphone? or can i get official unlock from apple? cause i had iphone but it got water damage and don't want to pay crazy amount of money to get brand new...
and i m getting locked phone from my family memeber for free. but he's with some other carrier. so can i get official unlock for that phone. please help me with this.
thank youOnly the original cellular provider can authorize unlocking. You will need to contact them to determine if they offer unlocking and if the phone qualifies.
-
Can I use officially unlocked iPhone in different countries?
I'm moving to Rome with my job for eight months, then on to Chicago for four months, then back to London. I'm trying to find out if I buy an unlocked Pay as You Go iPhone in one of the various EU countries selling manufacturer unlocked units (France, Germany, Italy, etc) , will it work in each country if I switch to that country's telecom's Sim cards.
The blogs and iPhone dedicated websites are full of opinions but no one seems to have definitive experience doing this. Some users say it should work, others say the EU iPhones are unlocked for the specific country of purchase but will not work with another country's telecom's Sim cards. The Apple Stores will not confirm any usage outside their own country. Similar response from the relevant telecoms. The Apple Support pages do not make any reference to cross country usage beyond roaming.
A privately unlocked iPhone is an option but I prefer an official unlock so there are no hassles. Not looking for opinions here - can find more than enough on the internet. I'm looking for actual first hand experience using these officially unlocked iPhones between countries.Thanks for the correction on the relevant carriers. Looking at the European options: Belgium, Italy, Luxembourg, and Czech Republic should work based on details from Apple's carrier list.
Before I buy I would like to confirm someone has actually purchased an unlocked iPhone in either Belgium, Italy, Luxembourg or Czech Republic and used it with Sim cards from another country. -
Have you officially joined BPX? How many people have you invited?
For those who are watching the Business Process Expert "general discussion" forum:
The first question is: <b>Have you officially joined the BPX Community here? </b>
If so, <u>thank you</u>. You are one of the 8,328 people who have already joined in only the first four weeks of this community being available. Note, too, that we're still in "sneak preview" mode so we haven't even done any announcements or awareness campaigns! You're in on the "ground floor" with visionaries and leaders.
If you're not an official member yet, please join ... just go to the top of the page in the header under "Profile Management," see the category for "Update Profile," and check the box at the very bottom of that page that says "I would like to join the new Business Process Expert (BPX) Community." Of course it's free and you get the benefits of posting forum questions and answers, blogging, etc. etc.
Please also sign-up for the newsletter while you're already on that page. More than 100,000 people already subscribe and find it valuable. We send a newsletter approximately every two weeks to highlight just a few of the new items and topics -- mostly as a reminder to return to the online community area(s) if you're not already in the good habit of doing so.
Second question is: <b>How many people have you referred to this new community with the recommendation to join?</b>
If you've invited at least three people who have joined, then "<u>thank you</u>!" If they are new members of BPX and SDN (and if they used your name/email as a referrer when they joined), then you received award points as our thanks.
If you haven't yet invited at least three colleagues to join, please do so. We think it'll help them in their jobs and careers, and we think it'll help you in your work with them (they're smarter, better informed, on the same page with their colleagues -- including you...).
Thank you for your membership, participation, and for spreading the word.
Mark Y.I have had numerous issues. Originally, I couldn't get video to work at all in Leopard (worked fine in Tiger). I just recently did all of the following things:
Set QT STreaming to 1.5
Set bandwidth (in iChat) to 500kbps (Comcast)
Deleted iChat prefs and ichatagent prefs
Set parallels network to "host only" (was on shared)
Reset PRAM
Reset security port to 443 (in iChat prefs, server settings)
Restart iChat (obviously)
Right now, all of my buddies are currently offline, but I did test with apple's auto-bots and interestingly, I'm getting video to work with appleu3test01 and appleu3test03, but I get the same connection problem as before with appleu3test02 ("There was a communication error during your chat"). I'm curious what's different about this bot's settings. I'll report more when I get to test with a real person. -
How many times can Windows 7 be syspreped, what is the official Answer?
Hey everyone, can somebody out there give me the straight answer on this? What is the official number windows 7 can be syspreped? I am looking to build my reference images, but every time I do this I have to 150+ updates each time. Can
I get way with just updating the reference image every time? I have heard there is a Max number of times you can do this before you have to rebuild.
We are running WIndows 7 Enterprise with KMS.
Also will this apply to 8.1?
ThanksHi,
Sysprep limitations are due to the windows activation process.
There is no limit to the number of times that the Sysprep command can run on a computer. However, the clock for Windows Product Activation begins its countdown the first time Windows starts. You can use the sysprep /generalize command to reset Windows Product
Activation a maximum of three times. After the third time that you run the sysprep /generalize command, the clock can no longer be reset.
Assuming you are using a KMS: We recommend that KMS clients use the sysprep /generalize command where the value of the SkipRearm setting is equal to 1. After capturing this image, use the sysprep /generalize command, where the value of the SkipRearm setting
is equal to 0.
Karen Hu
TechNet Community Support -
I had already update mi new factory unlocked iPhone 4S to iOS 5.1.1 and I still having problems with "invalid sim". I'm from Argentina and here we don't have official service. PLEASE HELP ME, WHAT CAN I DO??? In Argentina is too expensive an iPhone 4S. Please I need help to continue believing in Apple. Thanks a lot. If anybody speak spanish better.
Was it purchased from an official Apple Store, not a reseller? Only Apple Stores sell official factory unlocked phones. The others sell hacked to unlock phones, and the unlocking is unstable.
Try these steps, as needed:
1. Reset phone - press both home and on/off buttons for at least 10 seconds until the Apple logo appears.
2. Settings > General > Reset > Reset Network Settings.
3. Replace SIM card (and reset network settings again)
4. Restore Phone in iTunes using a backup
5. Restore in iTunes as new, without using a backup
Maybe you are looking for
-
Hi Friends, I have requirement on BPM scenario.. This is integration between SAP-HR and Third party (Web seriveces) BPM initiates the Process.next action is Logon to Third party. Once we get the response for Login action below action need to be
-
Hi Gurus, Is there any sap std report for extracting Sr no Wise detail for unused stock Available with Distributor (consignment stock). Very very urgent. Regards, Raju.
-
How to troubleshoot an apparent imail hack?
My iMail is more active than I am - with a hundred emails coming in and going out when I send/recieve a single one. Today I got a bunch of 'failures' to addresses that are not anyone I know - one in Russian. How do I get back control of this?
-
hi. i'd like to roll forward standby 9.2.0.8 database using backup of primary made with rman. there is Note:290817.1 on this topic. the only problem is that we don't use recovery catalog at our site. can i create standby controlfile on primary (it'll
-
I want to put in my password to excess mu email but I am having trouble with the keyboard. How do you use the lowercase portion? My password is lowercase sensitive and it doesn't seem to be working. Thanks