Страница 2 из 2
-
kot99
- Регистрация:
- 5 янв 2014
- Сообщения:
- 14
В VirtualPC 2007 для работы Win95 необходимо отключить аппаратную виртуализацию, иначе появляется та самая ошибка защиты Windows.
-
Лечение такое же самое — установить патч amdk6upd.exe. Это ошибка самой винды, а не виртуалок. А потом можно опять врубать аппаратную виртуализацию. Я смутно припоминаю, что в году 99-00 я и с реальным железом сталкивался с такой проблемой.
-
Помогите, стистема не хочет запускаться.
Вложения:
-
-
Bato-San
Чеширский волк-киборг
- Регистрация:
- 24 июн 2010
- Сообщения:
- 14.136
@Dimalyozov, ну она жалуется, что у тебя чего то в конфигурационных файлах не так.
После прохождения BIOS POST зажми кнопку ctrl. И держи. Появится меню. Там выбери самый нижний пункт. Ну и при помощи редактора edit смотри чего у тебя там не так. -
Achez
- Регистрация:
- 3 сен 2016
- Сообщения:
- 1
Чувак, огромное спасибо тебе! Не первый день бьюсь над этой ошибкой. Теперь буду знать.
-
конфиг:
Elitegroup P4M800PRO-M478 (V1.0)
Intel Pentium 4 Processor supporting HT Technology 2.80 GHz, 512K Cache, 800 MHz FSB
AcBel Polytech E2 Power 510 450W (PC7006)
Samsung M368L3223FTN-CCC/256Mb DDR /или/ Kingston KVR667D2N5/512
Hitachi Travelstar 5K250 HTS542516K9SA00 160GB Internal 5400RPM 2.5″ (отформатирован в 120 гб)Сразу после окончания успешной установки Win98SE выдает эту ошибку при загрузке с хдд в обычном и безопасном режиме:
While initializing device VCACHE: Windows protection error. You need to restart your computer.
Пробовал менять разную оперативку, вставлять PCI видеокарту (вместо встроенной) и ставить IDE жесткий, ничего не изменилось. Что еще можно сделать?
Последнее редактирование: 9 сен 2016
-
Винду то с лиц образа конечно ставишь надеюсь? Ну и сбросить настройки биос до дефолтных (не оптимальных, а дефолтных) тоже попробовал уже небось? Это так , первое что в голову пришло пока просто
.
P.S. Просто если вдруг окажется что не SE а обычный win98 то он как известно на процах > 2.1 ггц не работает. В Win98se уже пофикшена эта проблема вроде как. Ну и кстати устанавливаешь то правильно её (сис раздел до 2 гб и т д). У нас тут где-то фак лежал, как установить win98 оптимально для старых гамесов и тд (если ты для них ставишь её) в wiki наверное. Еще помозгую короче ).
Последнее редактирование: 9 сен 2016
SILENT_Pavel нравится это.
-
Так в итоге сколько памяти стоит ?
Неплохо проверить память.Попробовать поднять лимиты.
[386Enh]
MaxPhysPage=39900[vcache]
MinFileCache=65536
MaxFileCache=131072
chunksize=2048
namecache=4096 -
Нужен не винт IDE, а режим контроллера HDD установить в Compatible, IDE или что-то подобное.
SILENT_Pavel нравится это.
-
nest
- Регистрация:
- 27 июл 2008
- Сообщения:
- 86
Только что ставил Win95 и была именно такая ошибка.
снял один «подозрительный» SIMM — ошибка пропала. Так что … просмотреть память.
Страница 2 из 2
Windows 95: Windows protection error after setup
-
Thread starterN7I2S5
-
Start dateMay 7, 2011
- Status
- Not open for further replies.
-
#1
I have tried booting up in safe mode and have formatted the VHD and reinstalled it several times, but I can’t figure out why it won’t work. It worked fine once before, but the hard drive it was on went bad, so I have to set it up again.
Thank you for any help/solutions.
-
- Mar 6, 2011
-
- 54
-
- 0
-
- 18,660
- 14
-
#2
Try reducing the available amount of RAM on the virtual setup and try again. Windows 95 is a very fast OS on hardware from 1998 and up, so I wouldn’t allocate more than 384MB RAM.
-
#4
I have tried booting up in safe mode and have formatted the VHD and reinstalled it several times, but I can’t figure out why it won’t work. It worked fine once before, but the hard drive it was on went bad, so I have to set it up again.
Thank you for any help/solutions.
Have you tried disabling Hardware Virtualization? That mostly fixes the problem
-
- Dec 10, 2012
-
- 41
-
- 0
-
- 10,540
- 1
-
#5
-
#6
Try reducing the available amount of RAM on the virtual setup and try again. Windows 95 is a very fast OS on hardware from 1998 and up, so I wouldn’t allocate more than 384MB RAM.
Holy *** man, thanks a damn lot. That solved my problem. You’re my hero of today =)
-
- Nov 22, 2010
-
- 52
-
- 0
-
- 18,640
- 1
-
#7
I just started my virtual Win 95 for the 1st time on VMWare 9. The Windows 95 Logo comes up fine but then I get the same error » Windows protection error»
I have set my RAM at about 250 MB. It doesn’t help. How do I disable Hardware Actualization?. Is it done within the guest system in VMWare or in the main Host system? ( I am on Windows 7)
Thanks
Ittiandro
-
#8
(this is what I had to do to get it working on windows 7)
installing windows 95 manually without the floppy setup disk
what you need:
.DOS on a floppy or on an image (.flp .img)
.Windows 95 cd
.VMWARE player (it’s free) or virtualpc (I recommend VMWARE)
.Magiciso (the free trial version will do)
.a copy of MSCDEX.EXE and oakcdrom.sys (both can be found online)
step 1
create a new virtual machine (make sure to add a floppy image drive if you are using vmware)
step 2
put your dos floppy/image in or mount it and install dos
step 3
download and install the free version of magiciso
open magic iso
go to new — floppy — 1.44
find a copy of mscdex.exe
find a copy of oakcdrom.sys (generic cd rom driver that works with dos.. might have to try another if it doesn’t work)
RENAME the oakcdrom.sys to cdrom.sys
drag both these files into magic iso on the floppy disk we just created
save the file
close magic iso
find the file we just saved in your explorer
change the extension from .ima to .flp (if you are using vmware) or .img (if you are using virtualpc)
(if you can’t see the extensions you’re going to need to change your folder options to show extensions)
google it. it’s easy to do
step 4
go back to your virtual machine
mount the floppy image we just created
a:
copy mscdex.exe c:
copy cdrom.sys c:
(don’t forget to rename oakcdrom.sys to cdrom.sys in step 3)
step 5
find config.sys in your c drive
type:
edit config.sys
now add a line that says this
device=c:cdrom.sys /d:mscd001
exit and save
step 6
find autoexec.bat in your c drive
type:
edit autoexec.bat
now add a line that says this
c:mscdex.exe /d:mscd001
exit and save
step 7
restart the computer or virtual machine
step 8
we’re still not done yet
now move to your c drive and type
mscdex.exe: /d:mscd001 /M:5 /V /L:d /S /K
(this part /M:x refers to the amount of buffers your drive has.. it’s either 4 or 5. usually 5)
step 9
create a blank floppy image either in vmware or magic iso then mount that new one
put your windows 95 cd in the cd drive
type:
d:
setup.exe
step 10
it should be booting windows 95 now
now you might run into troubles when it tries to install the other drivers
it might ask you for windows floppies even if you’re using the cd version
which I never understood
but anyways, you can find all of these drivers on the windows 95b cd if you have it
they’re all in cab files
so you’d need to extract them 1 by 1 and put them on floppy images to use them.
(huge pain)
but I actually just got it to load the drivers off the win95 cd by just trying it over and over again until
it worked. it might have been because I either did or didn’t restart after putting in the windows 95 cd
can’t remember, but I’d try both if you’re having trouble
all in all windows 95 is incredible wonky to install in a virtual machine. I highly recommend using VMWARE
and not virtual pc for this one.
If you didn’t have a hard time installing this.. you got incredible lucky
make sure you check to make sure windows95 is seeing your cd drive
if not go to the add new hardware wizard in the control panel and see if that detects it
(note: I tried it first without installing dos before hand and was running into troubles even though I had build the autoexec.bat and the config.sys correctly. Installing ms-dos first made the installation process a lot smoother)
Michael MacDonald
State of Psychosis
www.stateofpsychosis.com
www.soundcloud.com/state-of-psychosis
- Status
- Not open for further replies.
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
|
Discussion Which Windows Theme? (1995 ’till Today) | Windows Legacy | 18 | Oct 22, 2022 |
D
|
Question Where is the Windows 98 display driver? | Windows Legacy | 9 | Aug 7, 2022 |
S
|
Question PC won’t boot from a Windows 98 floppy boot disk ? | Windows Legacy | 12 | Jul 23, 2022 |
|
Question Dual-boot Windows 98/XP on old system, XP is on Drive D ? | Windows Legacy | 11 | Jun 4, 2022 |
|
Question Does DISM command really delete any of my data or installed apps or my other drives data ? | Windows Legacy | 6 | May 6, 2022 |
|
Question I can’t set or create a pagefile on windows 8.1 | Windows Legacy | 8 | May 5, 2022 |
|
Question How do i add Legacy mode to my BIOS, so i can install Windows XP and 7? | Windows Legacy | 3 | May 3, 2022 |
A
|
Question Windows 98 question… From boot to sleep | Windows Legacy | 8 | Apr 21, 2022 |
A
|
Question Windows Update Error 80071A30 — has anyone else run into this ? | Windows Legacy | 0 | Apr 19, 2022 |
|
Question Windows not booting. | Windows Legacy | 1 | Apr 16, 2022 |
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics
How to Fix Windows Protection Error in Windows 95 on VirtualBox
In this article, we will examine step by step how to fix the Protection Error error for Win95 virtual machine running on the Oracle VM VirtualBox virtualization program.
If you encounter this error when installing Windows 95, an older operating system, using the Oracle VM VBox virtualization program on the VM, the solution to this fault is quite simple.
After completing the installation of Win 95 on VirtualBox, you will see a mistake “While initializing device OS: Win Protection Error. You need to restart your computer.” failure when the setup restarts the virtual machine to finish the last steps.
This fault can often be due to incompatible hardware drivers, unsupported hardware, or startup apps.
For VM Protection Failure resolution, we will fix this problem by turning off VT-x from the VM settings.
In our previous article, we did a step-by-step Win 95 installation using Oracle VM VBox.
- How to Install Windows 95 on VirtualBox
How to Repair Boot Error in Win 95/98/2000
When you look at the image below, you will be able to see this error better. This error causes a boot error when you want to use the Win95, Win98 or Win2000 operating system with Oracle VM VBox. Because, according to today’s operating systems, virtualization programs are being developed.
Step 1
First, completely shut down the Win 95 VM. Click X (Close) to close the VM and select Power off the machine option in the Close VM window that opens and click the OK button.
Step 2
Click the Right Key / Settings on Windows 95 from the VirtualBox VM partition. In the Windows 95 settings window, first, click System and in the right pane, on the Acceleration tab, clear the Enable VT-x / AMD-V checkbox against Hardware VT-x and click the OK button.
Step 3
When you reboot the Win 95 VM, you will see this error resolved. As a result, check the Enable VT-x / AMD-V option when you encounter this error when running older Microsoft operating systems on VT-x programs.
Final Word
In this article, we have fixed the Win 95/98/200 Boot Error that we encounter when installed Windows 95 with Oracle VM VBox. Thanks for following us!
Related Articles
♦ How to Fix Screen Resolution on Win 95/98 in VBox
♦ How to Run Windows 7 in VirtualBox on Windows 10
♦ How to Run Windows 98 on Windows 10
♦ How to Create a New VM in Oracle VM VirtualBox
♦ How to Install VirtualBox on Ubuntu 17.10
About Author
tolqabaqci
SYSNETTECH Solutions
You should use VMware Player for Windows 95, as it has officially support for that. Here’s an alternative way to install it:
What you need:
- DOS on a floppy or on an image (.flp, .img)
- Windows 95 CD
- VMware player (it’s free) or VirtualPC (I recommend VMware)
- MagicIso (the free trial version will do)
- a copy of MSCDEX.EXE and oakcdrom.sys (both can be found online)
Procedure:
- Create a new virtual machine (make sure to add a floppy image drive if you are using VMware)
- Put your DOS floppy/image in or mount it and install DOS
-
Download and install the free version of MagicIso. Run it and go to new -> floppy -> 1.44
- Find a copy of mscdex.exe and oakcdrom.sys (generic CD-Rom driver that works with DOS. (might have to try another if it doesn’t work)
- Rename the oakcdrom.sys to cdrom.sys
- Drag both these files into MagicIso on the floppy disk we just created
- Save the file
- Close MagicIso
- Find the file we just saved in Explorer and change the extension from .ima to .flp (if you are using VMware) or .img (if you are using VirtualPC). (if you can’t see the extensions you’re going to need to change your folder options to show extensions)
-
Go back to your virtual machine and mount the floppy image we just created. run the following commands:
a: copy mscdex.exe c: copy cdrom.sys c:
-
Find config.sys in your C drive. type:
edit config.sys
Add a line that says this:
device=c:cdrom.sys /d:mscd001
Exit and save
-
Find autoexec.bat in your C drive. Type:
edit autoexec.bat
Now add a line that says this
c:mscdex.exe /d:mscd001
Exit and save
-
Restart the computer or virtual machine
-
Now move to your C drive and type:
mscdex.exe: /d:mscd001 /M:5 /V /L:d /S /K
(this part
/M:x
refers to the amount of buffers your drive has.. it’s either 4 or 5. usually 5) -
Create a blank floppy image either in VMware or MagicIso, then mount that new one. Put your Windows 95 CD in the CD drive and type:
d: setup.exe
-
It should be booting Windows 95 now
You might run into troubles when it tries to install the other drivers as it might ask you for Windows floppies even if you’re using the CD version. You can find all of these drivers on the windows 95b CD if you have it, as they are all in .cab files (you would need to extract them 1 by 1 and put them on floppy images to use them).
I actually just got it to load the drivers off the Windows 95 CD by just trying it over and over again until it worked. It might have been because I either did or didn’t restart after putting in the Windows 95 CD.
Make sure you check to make sure Windows 95 is seeing your CD drive. If not, go to the Add New Hardware Wizard in the Control Panel and see if that detects it.
(Note: I initially tried doing it without installing DOS using fdisk and format and manually adding the autoexec.bat and config.sys files but I was running into similar issues until I installed DOS first)