Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: jur on February 28, 2011, 07:07:00 PM
-
I loaded virtualbox-ose and -additions, and installed win XP as a virtual machine. Works, but I can't get internet access or any network connection happening. I have already gone into the devices-network menu and tried various settings with no success. I have also installed additions on the XP virtual machine.
Any help?
PS Is it necessary to load the -additions in tcl?
-
never load additions on a host system it is only for guests
tested internet connection with tiny core in tiny core :) it is fine here
-
What are the setting you used on the network adapter device?
-
my friend had a similar problem, he says has set the intel ethernet card settings in vbox and install driver but i dont know in specific
tinycore in tinycore work well also for me
-
default settings, didn't change anything
-
my friend have a windows personalized with nlite, probably have been removed ethernet driver
-
OK I got it going. Posting from win XP running inside tcl!
I got it going by win XP's hardware manager, uninstalling the ethernet adapter and scanning for new h/w. It promptly found the vbox network card and installed it, asking for a driver file which I didn't have. No problem, switch to tcl, download it, put on shared drive and presto! network adapter installed.
Could not connect to inet initially, so I switched back to default network device setting in vbox (NAT), and after that I was on.
-
Here's the kicker: booting into tcl and then into win XP on vbox, is actually faster than booting directly into winxp!
-
Ahah, great!
-
*I like button*
-
Hmmm... I think I'll finally retire my old XP box. Maybe the wife's O.X.B., too.
-
Here's the kicker: booting into tcl and then into win XP on vbox, is actually faster than booting directly into winxp!
This is not so by design, I'm sure :D
-
Here's the kicker: booting into tcl and then into win XP on vbox, is actually faster than booting directly into winxp!
Now that would attract attention at scale9x!
-
Here's the kicker: booting into tcl and then into win XP on vbox, is actually faster than booting directly into winxp!
Sounds to me like the difference between an "old" XP system (booted natively) that was installed a while ago and had lots of opportunities to "go slow" (as they all do over some time with software and driver installations etc.) vs. a "new" XP system freshly installed in a VM.
-
Admittedly I have not performed rigorous testing. But what I can say with certainty, is the vbox boots win xp a LOT faster than directly. That's on my eee pc.
-
Here I am with the same problem on a different machine. The is the powerful work laptop; I have a dual-boot and often boot into TC. Now I have VBox set up in TC and want to tun a Windows XP guest to run a heavyweight win application.
Problem is, I cannot get the network adapter driver installed. I have tried everything I can think of but nothing works. Searched the V irtualbox forums, nothing. I am about to give up. Help!
Machine is Dell Latitude, if that helps. I have tried every network adapter in VBox but all respond exactly the same. I have used the exact same winxp.iso previously on my netbook.
-
And solved again, in exactly the same way as before. I am not sure why this didn't work before.
-
@Jur: As I found your little problem rather surprising I tried to replicate it here: I did a rather "quick and dirty" installation of XP (just SP2 as that was the slipstreamed CD I could find right now), BUT I left initially the network configuration of the VM without any NIC.
After the OS installation (and some minor customisation of the UI) I also installed from 'VBoxGuestAdditions.iso' the GA for XP (note: the ISO image I had previously downloaded and copied to '/usr/local/share/virtualbox'). I then performed a shutdown and added a NIC leaving everything to the default settings (i.e. 'PCnet-FAST III (NAT)' which XP recognizes as "AMD PCNET Family PCI Ethernet Adaptor"). The following restart of the VM lead not even to any kind of pop-up message box and I was mildly surprised that the NIC was fully operational.
So I'm not sure what's happing at your side of the ditch. I can only assume that your VM was using a different default NIC. I'd imagine that the choice of it might differ depending on the OS type settings when one initially creates the VM.
EDIT: I've now done a bit of extra testing and of the six NIC adapter types one could chose from in VBox the following ones were requiring extra drivers for XP: - Intel PRO/1000 MT Desktop (82540EM),
- Intel PRO/1000 MT Server (82545EM), and
- Paravirtualized Network (virtio-net)
OTOH the following three were fine insofar as XP already had a driver for them:- PCnet-PCI II (Am79C970A),
- PCnet-FAST III (Am79C973), and
- Intel PRO/1000 T Server (82543GC)
-
I think I figured it out: my virtual CD was pointing to VBoxadditions.iso, so the OS could not find the XP disk with drivers on it. Once I put the xp.iso back in, it worked, but the xp.iso was a self-built one from the OEM winxp that came with the netbook, so no CD. I assume that one driver file was missing.