MEPIS Community Forum

Hi All,

Following this thread http://forum.mepiscommunity.org/viewtopic.php?f=8&t=29288, I've been trying to get the new, easy way to create a bootable USB drive working in the MEPIS assistant. Attached to this post are the fruits of my labours (both 32bit and 64bit)...

It's working fine on my system, but I'd appreciate help from you all in testing it on your systems to ensure it really is working. Note there is one bug that I'm aware of where the progress bar doesn't work for the new 'isohybrid' option - it works fine for the others. I can't for the life of me fathom why it isn't working...

I'd also like your opinions on two specific aspects:
1. what should the various options be called? Previously they were named after different versions of MEPIS, but it really didn't make sense to me. So, I've renamed them, but they could be better.
2. Do we actually need all those options? I'd be in favour of just having two: the 'new' method and a simple format USB.

Please let me know what you think, hopefully they'll work and then I can push the changes onto Warren for inclusion. :-D

To run the program it has to be as kdesu, not root. Running as root will fail. To run it, download the attached file suitable for system and then do the following (replace 32 with 64 if you're running 64bit):


BTW I've only tested it in m11. It probably won't work in m8.5 and definitely not on m8.

And remember this is testing code so be careful where you run it. I've run it several times with no serious problems, but that isn't to say it won't cause issues for you. You have been warned

Many thanks!

Edit:
as far as I aware the new 'isohybrid' method will only work with mepis8.5 and mepis11 ISOs/DVDs.

It won't come up for me. Followed your directions and typed Dialog box came up, entered root password, pause, and...back at the prompt. Trying 32bit.

Did you gunzip the download? And are you running it from where you downloaded it?

yes, yes

anyone else confirm?

I needed to make msystem32 executable.

(right click on it, properties, permissions, click the "Is executable"checkbox)

Any reason why you have to use kdesu and not gksu (or sux)? I'd like to test, but I don't want to install kdesu.

Do you have su-to-root installed (or the package that installs it) [edit: the package that installs su-to-root is menu]

In Mepis it brings up the kdesu box but it's also supposed to work with gksu and sux.
Using su-to-root the command is: su-to-root -X -c ./msystem32

.
hey big guys,

what it did for me was to quickly remove everything that was on the flash drive, sandisk 4 gig/3.7, elive 32 bit lenny just flashed it in a second or two, wow. but when i mounted it it was bare so i tried again with the hybrid option which showed the status bar but went a little two quick, mounted, checked, unmounted and tried again all with the same results empty.

i remembered someone had mentioned using the msystem with 8.5 to usb :) which worked quite well in like five or eight minutes. typing from it now, really sweet and quick boot with nvidia option, correct res... ... created with the first in sig... running on the third, both 64s.
will try again after hearing of better results

thanks guys
i previously tried the newer downloaded msystem with my M8 64 wheez... but couldn't get it to start .
also; above mentioned elive cd is very well done cd if somebody wanted to take a look it contained propriety drivers...

64-bit version running as I type on my production laptop, albeit on my old and very slow flash drive (1.5mbps write speed)

Quick question, does the isohybrid option check first to see if the selected ISO image has been prepped with the isohybrid app becasue if it doesn't, then the resultant thumb drive build may very well be useless.

Anyway, the process finished and the thumb drive booted my eee without any glicthes

Mike P

I think Warren packages his executables with a .desktop launcher that requires kdesu--it may be interesting to replace his binary in /usr/sbin with yours and see how that works (downloading now)

Edit: yup, that works to launch it, after renaming the executable to msystem and making it executable.


or use the GUI for that.