Capture is only 2.5MB
-
It’s XP pro 32bit yeah
-
@KeithDib Not the OS, the Device itself?
-
My host is i7 running Windows 10 pro 64 bit, running virtualbox.
Running FOG on Ubuntu 14.x.x (not in front at the moment for exact version)
VMs are 32bit xp and 64bit win 7
-
@KeithDib So the VM is 32 bit CPU only? The OS doesn’t matter. You can have 64 bit CPU with a 32 bit OS. Sorry if it seems like it should be obvious, but you keep placing the OS as part of it. I don’t care about the OS. Is the system 32 bit?
I’m asking because I’m trying to find out if what you’re seeing is potentially an Architecture issue in the inits. The OS does not tell us the System’s own architecture.
-
It’s 64 bit,
as I say in previous post, an older version of FOG on the pre buit VM has been working fine on same hosts and same VMs
-
You still have given us no information.
WHAT is 64 bit? What is 32 bit?
Do you have a VM that is your test bed set to do 32 bit windows mode which would be why it’s loading the init_32 and bzImage32 files? If that is the case then can you try a windows XP image with a 64 bit cpu?
-
Does FOG only work with 64bit hardware then?
-
@KeithDib I never once said that it does or doesn’t. (It should)
I’m trying to figure out if the problem you are having is because of the init arch or not.
-
It’s just weird the older version I have works fine
I think tomorrow I’ll try from scratch on fresh install see if same issue
-
@KeithDib I’ve got virtual box on my mint laptop. Can you describe how you setup up the VM where you are installing XP? I’ll try to duplicate your setup in my home lab.
This is just straight XP out of the box running on virtual box?
-
@george1421
Windows xp pro 32bit, vanilla install with no other apps, virtualbox with 4GB ram, 25gb HDD, NAT on the network, everything else as default settings. -
@KeithDib said in Capture is only 2.5MB:
NAT on the network
just for a data point: this should be bridged
I’ll get this environment setup and tested tonight.
-
Sat down and worked with @george1421 and we believe the issue has been found and is now fixed.
RC 3 has been released in hopes to get this fix out there.
-
I will download RC 3 tonight and try a fresh install with this version and will report my progress
thanks for the help
-
@KeithDib While I was able to capture the image no problem with 1.4.0RC3 I wasn’t able to deploy it correctly. I tested that part (deployment) after Tom broke off the debugging session.
On a side note I was able to duplicate your issue exactly in my dev environment that is how we were able to find the exact cause of the capture problem.
Also I found with virtualbox (not related to fog), that you should set the NIC to bridged and under advanced change the interface type from amd to one of the intel nics (I used the bottom intel MT adapter) and the capture went much faster.
-
cheers, i will try different NIC setting later today, where is best download location for the updated version? in work at the moment and cant get to some locations through search
-
@KeithDib There still seems to be an issue with deployment. Capture works as far as we can tell (having a successful deployment would prove it). So for right now I would hold off on doing anything.
But you will need to follow the process for upgrading to the trunk then switch to the dev branch. I will follow up with instructions once we are sure this issue is resolved.
-
thanks for the info and support
-
I may have a new way to do this, strange as it may sound I forgot one of my NAS boxes can also handle my DHCP, so i need to reconfigure the network when i get some free time.
-
I’m confused here. NAS can do DHCP just fine, but what is doing this going to fix in regards to Capture having been broken until RC-3?
While I realize the issue of deployment was, as of yet, still broken for Windows XP/Vista, DHCP had no bearing on the capture/deploy process at all.
