So what I'm getting is, you are sharing files between distros, but you're not exacly sharing /home (correct me if I'm wrong)

If that is the case then, yeah, You'll have to do it the way you are doing it now.I can't really force UID's @ 1000 regardless of anything, I dont want to be responsible for messing up somebody's home directory.

the gui installer can also be ran from the gambas IDE, by running "gambas2" from a terminal, then when the gambas IDE opens clicking on open project and browsing to the /root/speedy dir.I imagine you will get the same results there, but when the installer crashes you will see the line of code highlighted where the crash happens and with that info we may be able to squash this bug.

I think I did it right this time. After the installer crashes and I look for the crash information, I see a panel with a left tab saying MdlMain.module. Under that I see proble_system_partitions365.1

The highlighted line sayspCurrentFileSystem=Trimpartinfo([5])

Under Stack backtrack,MdlMain.probe_system_partitions.365Step1.Timer1_Timer.357

I hope I got those right because the letters were very small and unclear (running at 800x600 on an LCD with a native resolution of 1280x1024) and I had to copy everything down by hand. My handwriting is terrible and many times I'm not sure what I wrote.

I'm looking forward to the next beta and hope the problem will be solved by then.-- GrannyGeek

Setting up a firewall using VASMCC under the Network category is breaking my systems. I set up a firewall, used the default port openings except I enabled pop and smtp (I use Thunderbird for mail). I also started the firewall and enabled it to start at boot.

Now, my system will not shut down. It goes to the progress bar screen and just sits there. Ctrl-Alt-Del reboots the system from there. I went back into VASMCC and set disabled the firewall from starting at boot and then used the Stop firewall option. System became sluggish. Opened System Monitor, and I had over 2000 processes and 100% CPU usage. The process count was continually climbing, and there were a great many "firewall" processes listed in the table. I watched it roll over 3000 processes, at which time I done a hard power off.

Upon reboot, the firewall is still loading, ie it did not successfully respond to the commands to stop and stop at boot.

Moreover, this entire problem was repeated on a 2nd test machine! Systems are now broken, and I have to power down by holding down the power button for about 5 seconds.

I do a good deal of online ordering, and banking, so I need the firewall to function correctly.

Actually, a closer look @ Granny's results indicates that her hard disks contain some partitions with an unknown filesystem.These could be unformatted partitions (partition with no filesystem) or a partition with some filesystem that the initrd cannot recognize. Take a look

In this case, for some odd reason, parted does not read this partition at all, but fdisk reads this as a swap partition.I can't explain why this would happen, but at any rate, I have made accomodations to prevent this type of crash by reporting the partition in question as 'Unknown'

My suggestion to granny is.If this is a real swap partition, fire up gparted and delete it then re-create it and then see if the problem persists.

If the problem persists, please post the output of the following commands

Actually, a closer look @ Granny's results indicates that her hard disks contain some partitions with an unknown filesystem.These could be unformatted partitions (partition with no filesystem) or a partition with some filesystem that the initrd cannot recognize. Take a look

In this case, for some odd reason, parted does not read this partition at all, but fdisk reads this as a swap partition.I can't explain why this would happen, but at any rate, I have made accomodations to prevent this type of crash by reporting the partition in question as 'Unknown'

My suggestion to granny is.If this is a real swap partition, fire up gparted and delete it then re-create it and then see if the problem persists.

If the problem persists, please post the output of the following commands

Code:

parted /dev/hde print

Hope this at least keeps your box from crashing.

You're talking about Number 6, right? Yes, it's a Linux swap partition. I'll do what you suggest tomorrow and let you know the results. --GrannyGeek

Just tried both beta 1.2 and 1.3. In both cases, I don't get any further than the splash screen. I get the 'loading installer', there is a brief flicker, then nothing for about 30 seconds. After which, the CD is ejected and the machine reboots.

Just tried both beta 1.2 and 1.3. In both cases, I don't get any further than the splash screen. I get the 'loading installer', there is a brief flicker, then nothing for about 30 seconds. After which, the CD is ejected and the machine reboots.

Sorry, this one doesn't like my hardware at all.

Paul.

Paul,I am going to need your help with this. can you boot with "gui 2" then after you login run startx and post me any errors and the /var/log/Xorg.0.log

Just tried both beta 1.2 and 1.3. In both cases, I don't get any further than the splash screen. I get the 'loading installer', there is a brief flicker, then nothing for about 30 seconds. After which, the CD is ejected and the machine reboots.

Sorry, this one doesn't like my hardware at all.

Paul.

Paul,I am going to need your help with this. can you boot with "gui 2" then after you login run startx and post me any errors and the /var/log/Xorg.0.log

Thanks,Uel

Ok, done. When I run startx I get no errors, the prompt goes away for around 30 seconds, then returns to the prompt.

Xorg.0.log is as below:

Code:

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6_XSERVTransOpen: transport open failed for inet6/vector:0_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

I tried this last night too with the exact same results, except i was not using burned cds but rather booting cd1 from iso. When i booted into init 2 and ran lsmod it showed no modules at all were loaded.Running depmod did absolutely notjing. X wouldnt start either because it said it couldnt create the .lock file on a read only filesyatem.

Ended up booting an old b1 iso and running the updated installer there.

During installation, it would not recognize the second iso. Maybe yhe media id or release ids were causing the problem... didnt really check the log. Ended up installing the contents of the secomd iso manually. Once installed it seems to be running fine though