It is not I am afraid... it has to do with how the filesystem is compressed before the iso is created.
That is fixed now, and networking should be fixed as well. I have 3 known issues...
1 vesa drivers (for people installing in virtual machines) are not being loaded when hitting a driver it doesn't know (InnoTek in the case of my VM). I can sneak in while avwizard starts with a sed command and replace InnoTek with vesa, and it boots fine. It uses the ATI/nVidia/intel drivers correctly however.
The second issue is the desktop. After install, clicking KDE Desktop from teh orbiter craps out with an error about kstartupconfig4 file. If you can still test given these conditions, it is appreciated.
The third issue is that an extra networking thing is stuck in there by a recent change to other code. I believe that has been resolved, but not tested yet... so check your /etc/network/interfaces file and make sure there is not a third nic entry there with blank values.
In VM, while it is loading the first time it reboots, you can right ctrl + f2, login, and issue issue (over and over)
sed -i 's/InnoTek/vesa/g' /etc/X11/xorg.conf.pluto.avwizard
Replacing InnoTek with whatever your VM identifies as (Wasn't InnoTek the company in Office Space?) and it will load and work right.
I am working to resolve all of these problems.
*** oh... a fourth issue is that purple screen which you ONLY see in VM. I have no idea how that thing is persisting.
