Page 1 of 1

Service Pack Issue Solved, But Another Issue...

Posted: 29. May 2008, 20:15
by Brian Jester
I got sp1a to install, that was because the windows xp I put in had sp2 pre-installed...Anyway, this time, the problem is that now when I install the drivers from my intel motherboard cd, it tells me this is not an intel motherboard and none of the drivers show in the installation dialog...I believe this is a problem with vbox...Is there someway to get around this issue? Note: I still haven't got my backup drive to show up. The IDE (pata) drive.

Tia,
-Brian

Posted: 30. May 2008, 06:29
by Brian Jester
Any help on this??? I am stumped! I can't figure it out why my intel express cd tells me that an intel motherboard is not detected...I suspect that's Virtualbox causing this to happen, does anyone have a fix to it? I really need to get the Windows XP installed and working with all the drivers from that intel express cd.

I would really appreciate someone's effort in helping me resolve this issue.

In case I didn't post my specs, here they are:

Intel Motherboard: D875PBZ

Ram: 1 Gigabyte - (two 512 DDR chips)

CPU: 3.2 Ghz

2 Hard Drives: 20 Gig Boot Drive (Pata IDE) & 80 Gig Backup (Pata IDE) Which is not detected in the VirtualBox Running Windows XP with or without Service Pack 1a (current sp1a is installed) but IS detected in the host machine Mandriva Linux 2008 Powerpack which I just installed.

I installed Windows XP in the virtualbox using hdd space dynamically not a specific amount and same with the ram (Defaults) I really need to get this to work...If anyone has an idea as to what is causing my IDE backup drive not to show in the virtual box running WinXP w/ service pack 1 installed and also why my intel express cd won't install inside virtualbox, please let me know as soon as you can.



Thanks again!
-Brian

Posted: 30. May 2008, 15:04
by Quantum
Well, understand that you wouldn't be installing it on Intel hardware... you'd be installing it on VirtualBox hardware.

The whole idea is that VB creates a virtual machine environment which makes Winduhs think it has its own machine, and VB must prevent direct access to actual hardware functions in order to protect the integrity of the host. This is particularly true of the video driver.

Now; it is possible that if you activated the IO/APIC and PAE/NX functions that you will have access to more hardware than normal, but understand that these are experimental and probably buggy. Risky.

Posted: 30. May 2008, 20:36
by Brian Jester
I still didn't have any luck with enabling those two options, but thanks anyway, it was worth a shot...

Btw, has this kind of problem ever been addressed before by other users? And do you plan to have a fix for it? Or is it too much to even bother with? Also, is this a problem with older motherboards or with any of them, because I was getting ready to buy a new Linux box soon anyway...I just don't know which would be the best...Especially if I want to boot other systems in a Virtualbox, Specifically Windows XP...

Tia,
-Brian

Posted: 31. May 2008, 03:33
by Quantum
Looks like you didn't actually understand what I said.

Posted: 31. May 2008, 19:00
by Brian Jester
Looks like you didn't actually understand what I said.
Those were options to enable, and that's what I did...Maybe I missed something else? It still didn't work btw.. :cry:

Can someone tell me if this problem can be avoided by purchasing different hardware or even a new pc?

Thanks again!
-Brian