virtualbox.org

at older versions of virtualbox i was able to install win 7 x86 on my debian but now i cant my system has not vt-x in bios and no-execute memory protect is enabled at default whats problem with newer version of virtualbox ? i enabled PAE/NX and it fixed 0xc0000260 but after it now i get 0x0000000A how i should fix it ?

changing chipset from PIIX3 to ICH9 and enabling I/O APIC are useless

i uninstalled fglrx-driver because had problem and now use default of debian
vga: hd5450

log file ATTACHED

im sorry if i say it here because mpack locked related post because someone spoke about vmware there.

virtualbox is dead it was so fast on this old machine w/o vt-x but you killed it
and now im forced to use vmware that runs but suckly

omletbapiaz wrote:im sorry if i say it here because mpack locked related post because someone spoke about vmware there.

mpack 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.

Splitting your post to a new topic in the "Linux Hosts" from "VirtualBox on Windows pre-releases".

00:00:01.174688 Full Name: "Intel(R) Pentium(R) Dual  CPU  E2200  @ 2.20GHz"

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.

omletbapiaz wrote:virtualbox is dead

Some people would say that your computer is way more dead compared to VirtualBox. But, that's just some people...

omletbapiaz wrote:it was so fast on this old machine w/o vt-x but you killed it

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...

and what about windows xp ? i installed it but when i install eset internet security latest version i get fatal error even host crashed logs attached

omletbapiaz wrote:when i install eset internet security latest version

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.

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.

and this is another log file from it

omletbapiaz wrote:im sorry if i say it here because mpack locked related post because someone spoke about vmware there.

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.

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.

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.

socratis wrote:

omletbapiaz wrote:when i install eset internet security latest version

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.

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.

im doing it exactly today

new computers are for gaming i dont need them i am just programming and this pc is enough because some people are Neophiliac i dont throw this pc away

as my experience avoid supporting old machines has negative population

this version of vbox is free so why like microsoft want throw away old versions because of security(real matter is money) old machines will be more secure in future.
for example if you try to write a virus for win 7 x86 all anti-virus companies collected a lot of signature from x86 but writing a virus for new x64 pc is easier because less signature collected and just THINK why C.I.A advertising this windows 10 of course C.I.A spies our information and windows 10 is best TOOL. and why peoples should buy new computers for easy jobs producing silicon and copper is hard you are just sitting front of pc and dont know what is happening for it

and why intel putted "intel management engine" a super hidden hardware backdoor and just used by C.I.A
i just waiting for new amd cpu's backdoor!! but you want buy it and you love to spend your lifetime for getting newer pc dont be so fast when there are faster computers in future you are dead.

if you think i should buy new pc yet your brain is pruned and closed
open your mind.

i using nokia 6600 yet!!!! made in finland at 2004 lol even they have a day for throwing away old phones but not me.
your smartphone is a spy in your pocket under water on your eyes ears and legs
https://wikileaks.org/

mpack 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.

i addressed to virtualbox's developers

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

As this has nothing to do with VirtualBox, if I hear anything more like that, the thread gets locked. Enough is enough.

omletbapiaz wrote:in future you are dead.

I agree.

socratis wrote:

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

As this has nothing to do with VirtualBox, if I hear anything more like that, the thread gets locked. Enough is enough.

omletbapiaz wrote:in future you are dead.

I agree.

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 future

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 came here and signed up yesterday because of big fail of virtualbox and you expect total posts (ꝏ posts), users helped (ꝏ users)

if i was VMware fan i wasnt here im here because virtualbox was best until these new versions

i dont know why you guys answer personal really!!! i want hear your technical words but its seems some barrier are made for this forum because of some noobish ideas

for example i want speak technical: i checked old versions no one of them worked i can remember that 5.1.10 worked but now doesnt so some other thing is the problem so let check what is changed i forced to uninstall my fglrx-driver because error "fglrx_setsuspendresumestate failed -9" so now i use defaut vga drivers i mean a null xorg.0.conf file. and my windows 7 image for install is updated that has splash screen like windows 10

so can be source of error from vga driver or windows image ?

some1 reported these bugs exactly today and they are mine also:

https://www.mail-archive.com/debian-bug ... 06866.html
https://bugs.debian.org/cgi-bin/bugrepo ... bug=860825

they updated backports my installed version of linux kernel is 4.8.0-0-amd64-bpo but they removed it and now you just can install 4.9 that fglrx dkms module is unable to compile for it

so i think source of problem can be from here

pFfffffffffffffffffffffffffff

completly not related to my cpu or pc

error is this and:

omletbapiaz wrote:i enabled PAE/NX and it fixed 0xc0000260 but after it now i get 0x0000000A

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 is

Win_7_x86_ Ultimate_ Sp1_ En-Us_April_ 2017.iso

First step would proably to try to find an official unhacked legal version of Windows...

stop wasting my time i tested a lot of old and new windows 7 images all of them just show damn windows 10 installation splash screen and same error 0x0000000a

fix this .