LOL!I noticed the "Could not write to file: No space left on device" errors but didn't know if I trusted them as so much has gone goofy for you. And I didn't have the <insert possibly profane word for round bouncy things here> to ask you if you had enough disk space.

Uhmm....The uninstaller of the MMBD doesn't work?I ran that one, but my partition is still stuffed to the rim and the MMBD-programs are still there and working, even though the uninstaller said the uninstall was successfull.

Not really a disaster where it consideres my installation(this one's gonna get nuked anyway.) but do other people encounter the same?

I see now that I should have implemented a check for disc space function. That is possibly why the user account problems occurred and also why the uninstaller doesn't as well. I am able to uninstall the entire disc quite easily and have been able to do so on many systems. But, I also have a 320gb hard drive with plenty of space to install as much as I want.

What if you repartitioned to give yourself a larger space to install SOHO? That may help. When you are completely out of disc space, things really do get weird.

Then the uninstaller cheerfully tells me, the MMBD is removed from the system, which is not the case.Also; it appears, the MMBD packeges don' t register with GSLAPT; I tried to use that one to remove the packages manually, but no such luck.According to GSLAPT, there were no such packages.

Maybe an idea to make the MMBD call GSLAPT to install its packages? That way, there' s always a means of purging the system, so to say.(If not; why?)

sh install.shAre you executing the install file inside of the MMBD_Data folder or directly from the CD? There were some issues to get around some bug/problem with kde desktop files for installing. The install file on the CD was meant to be run directly and it should work. The error lies in being unable to find the Packages folder.

Quote

Maybe an idea to make the MMBD call GSLAPT to install its packages? That way, there' s always a means of purging the system, so to say.(If not; why?)

That is exactly how the installer was written and the uninstaller should work exactly as you think it should (using gslapt). And that is weird that Gslapt does not show the packages. Man! Everything works great here...but that doesn't help you much does it?

Go ahead and try the installer again. Try just clicking on the Install-SOHO file on the cd and see if that works for ya.

My copy of SOHO disc 2 was downloaded. I never did a full install (aminly didn't want some of the non-MMDB bonus apps) and I didn't have any of the problems you described. There were a couple of bugs that dweeberkitty warned me were there (gtkam has issues) but mostly I was very pleased.

Yeah... I looked for xmms too. Howwever, I've discovered that I really, really like Aqualung better and it's included I still hate ripperX and would like to see grip in the next version. I've noticed some Slackware based distros (Wolvix, AliXe) managed to include it without having a ton of GNOMEish stuff installed.

sh install.shAre you executing the install file inside of the MMBD_Data folder or directly from the CD? There were some issues to get around some bug/problem with kde desktop files for installing. The install file on the CD was meant to be run directly and it should work. The error lies in being unable to find the Packages folder.

Quote

Maybe an idea to make the MMBD call GSLAPT to install its packages? That way, there' s always a means of purging the system, so to say.(If not; why?)

Uhm... yes I did, since that's the first one I encountered and hence concluded, it was the only/preferred one.

That is exactly how the installer was written and the uninstaller should work exactly as you think it should (using gslapt). And that is weird that Gslapt does not show the packages. Man! Everything works great here...but that doesn't help you much does it?

Go ahead and try the installer again. Try just clicking on the Install-SOHO file on the cd and see if that works for ya.

Not gonna happen today; Just finished posting my experiences with a fresh, double-checked installation with plenty of room everywhere. Didn't even get to installing the MMBD...(And as it is now, I won't risk my last remaining working installation...)

Not gonna happen today; Just finished posting my experiences with a fresh, double-checked installation with plenty of room everywhere. Didn't even get to installing the MMBD...(And as it is now, I won't risk my last remaining working installation...)

Fair enough. Once I get these bugs fixed, and implement the free space checking, I'll probably release a MMBD 1.5 update to make sure that the problems are fixed before proceeding on to 2.0 on VL6. We'll see how it works out.

EDIT: Did you ever decide whether those CDs were actually a "bad burn?" Or was it the freespace problem?