it was so fast on this old machine w/o vt-x but you killed it
VBox.logmpack didn't lock the previous thread because someone mentioned VMWare. mpack locked a thread from 2014, on the Windows Hosts forums. You have a Linux Host with Windows Guest(s). Nothing similar. Next time please pick your sub-forum correctly before you post.omletbapiaz wrote:im sorry if i say it here because mpack locked related post because someone spoke about vmware there.
Your processor is indeed quite old and as you correctly said it doesn't support VT-x. Your choices are limited and are getting fewer. If you say that in the previous versions you were able to run Win7, then stick with the old version. There is no way that you can install Win10 without VT-x. None.00:00:01.174688 Full Name: "Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz"
Some people would say that your computer is way more dead compared to VirtualBox. But, that's just some people...omletbapiaz wrote:virtualbox is dead
Then stick with what was working. The world is moving forward I'm afraid. I have several dead PPCs. They were fast when I bought them. Really fast...omletbapiaz wrote:it was so fast on this old machine w/o vt-x but you killed it
I told you to stay with the version that was working, even for the antivirus. The latest version of anything will have significantly less chances of working. Your computer was EOL'd, so was Windows XP.omletbapiaz wrote:when i install eset internet security latest version
The post mentioning VMWare was from 2015. What kind of mental contortions do you have to pull to think that an action I took on Thursday - right after you posted - was because of the VMware post and not because of your post? You posted an unsubtantiated "me too" into a dead topic which was itself off topic even when it was live. That's why I asked you to provide a better post and then I locked the topic.omletbapiaz wrote:im sorry if i say it here because mpack locked related post because someone spoke about vmware there.
im doing it exactly todaysocratis wrote:I told you to stay with the version that was working, even for the antivirus. The latest version of anything will have significantly less chances of working. Your computer was EOL'd, so was Windows XP.omletbapiaz wrote:when i install eset internet security latest version
I don't expect that if I pull out my physical Pentium/WinNT4 from the basement I could be surfing today's websites. I can't.
i addressed to virtualbox's developersmpack wrote:omletbapiaz wrote:That doesn't seem to be the your only misunderstanding. When you say that "you killed it", who is the "you" being addressed? This is a users forum. We use, we neither created nor killed anything.
As this has nothing to do with VirtualBox, if I hear anything more like that, the thread gets locked. Enough is enough.omletbapiaz wrote:real matter is money ... C.I.A advertising this windows 10 ... C.I.A spies our information ... "intel management engine" a super hidden hardware backdoor ... waiting for new amd cpu's backdoor!! ... open your mind ... your smartphone is a spy in your pocket under water on your eyes ears and legs ... wikileaks
I agree.omletbapiaz wrote:in future you are dead.
man you just trying to give answer to me and make it personal. if there is nothing to do with vitrualbox. why when there is something you say use old versions and easily you decided to destroy best versions with new versions you just check my log file and only said you cpu is too old good job you gave a lot of technical info to peoples that will see this post at futuresocratis wrote:As this has nothing to do with VirtualBox, if I hear anything more like that, the thread gets locked. Enough is enough.omletbapiaz wrote:real matter is money ... C.I.A advertising this windows 10 ... C.I.A spies our information ... "intel management engine" a super hidden hardware backdoor ... waiting for new amd cpu's backdoor!! ... open your mind ... your smartphone is a spy in your pocket under water on your eyes ears and legs ... wikileaks
I agree.omletbapiaz wrote:in future you are dead.
i came here and signed up yesterday because of big fail of virtualbox and you expect total posts (ꝏ posts), users helped (ꝏ users)mpack wrote:omletbapiaz wrote: Then there's the implied threat to go to VMWare. Again, this is a users forum, where we users pass information about VirtualBox to each other. I'm sorry to be blunt, but none of us cares if you switch to VMWare. Stick around, help 1000 other users, and then your defection might be seen as a sad loss. You current score is: total posts (4), users helped (0). So judge for yourself how much your loss would hurt us.
i used this windows image on an asus P8H77 and Core i3 and on WINDOWS HOST and same problem is there also so 5.1.22 is a horibble version or windows image isomletbapiaz wrote:i enabled PAE/NX and it fixed 0xc0000260 but after it now i get 0x0000000A