Recent changes to bugs

#27 MultibootUSB don't start and freeze

Nicolai Garrecht — Tue, 30 Jan 2018 07:51:58 -0000

Same behavior with V9.1.0-1 on linux Ubuntu 14.04.5 LTS (32bit).
Iso I use is: https://sourceforge.net/projects/camerubuntu-hotspot-12-04/?source=directory
Stick has 4GB
- Format stick (one partition, FAT32)
- Choose stick (as drive dev/sdb) in Multibootusb
- Choose Iso in Multibootusb
- Write image to disk
- after a warning it starts at 0% and it stays at 0%. With top you can see that a dd command is running which let's the LED of the stick flash. When dd is finished, the LED stops flashing.
- Result: Multibootusb is frozen, USB stick needs new formatting for further usage.

#34 multbootusb quit after clicking 'All Drives'

Daniello Alto — Fri, 08 Dec 2017 22:02:29 -0000

Sorry I forgot to mention that is problem was 'introduced' with multibootusb-8.9.0
multibootusb-8.8.0 still works fine.

multbootusb quit after clicking 'All Drives'

Daniello Alto — Fri, 08 Dec 2017 21:55:23 -0000

... well before it quits I shortly see a black windows diskpart.exe.

System is Win7 x64 german

diskpart.exe /s data\tools\gdisk\list-disk.txt
output looks like this:

Microsoft DiskPart-Version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
Auf Computer: JO-PC

  Datenträger ###  Status         Größe    Frei     Dyn  GPT
  ---------------  -------------  -------  -------  ---  ---
  Datenträger 0    Online          465 GB     9 MB         
  Datenträger 1    Kein Medium        0 B      0 B         
  Datenträger 2    Kein Medium        0 B      0 B         
  Datenträger 3    Kein Medium        0 B      0 B         
  Datenträger 4    Kein Medium        0 B      0 B

okay ya really using the windows commandline tools and parsing it's output.
multibootusb-8.9.0\scripts\usb.py
def gpt_device(dev_name):

if platform.system() == 'Windows':
        diskpart_cmd = 'diskpart.exe /s ' + os.path.join('data', 'tools', 'gdisk', 'list-disk.txt')
        dev_no = get_physical_disk_number(dev_name)
        cmd_out = subprocess.check_output(diskpart_cmd)
        cmd_spt = cmd_out.split(b'\r')
        for line in cmd_spt:
            line = line.decode('utf-8')
            if '**Disk **' + dev_no in line:
                if '*' not in line.split()[-1]:
                    config.usb_gpt = False
                    gen.log('Device ' + dev_name + ' is a MBR disk...')
                    return False
                else:
                    config.usb_gpt = True
                    gen.log('Device ' + dev_name + ' is a GPT disk...')
                    return False

Guess that's not a good idea on windows.
Commandline output is localised and that'll create problems.
on some English system it is 'Disk ' but on German the same string your are looking for will be 'Datenträger '....

So use API's or that crappy WMI.
like this
wmic.exe logicaldisk get

#32 MultiBootUSB 8.5.0 No Module Found

sundar_ima — Tue, 16 May 2017 17:13:05 -0000

status: open --> closed

#32 MultiBootUSB 8.5.0 No Module Found

sundar_ima — Tue, 16 May 2017 17:12:43 -0000

Issue is solved in latest release. Current release is 8.8.0.

#31 Crash with CAINE Live CD/USB

sundar_ima — Wed, 26 Apr 2017 16:53:03 -0000

status: open --> closed

#31 Crash with CAINE Live CD/USB

sundar_ima — Wed, 26 Apr 2017 16:52:46 -0000

Fixed in latest version.

#32 MultiBootUSB 8.5.0 No Module Found

sundar_ima — Wed, 12 Apr 2017 01:27:46 -0000

Care and share ? At least you can do me what you think of and I can do it in upstream.

Pmagic on Verbatim USB is giving "Searching for PMAGIC_2013_08_01.SQFS" error

Mattes — Sun, 19 Feb 2017 22:15:39 -0000

Hi Guys,

I have a strange interesting problem.

I installed pmagic and ubuntu together on one USB Stick.

Ubuntu is starting without problem. Pmagic throw the error message "Searching for PMAGIC_2013_08_01.SQFS" and failed to start.

The USB stick is a Verbatim STORE_N_GO 8GB

When I try the same on a Crosair, Flash Voyager USB stick Ubtuntu and PMagic are working.

I did a diff between both sticks and they are basically the same. Only the files below are different. I assume because of different UUID.

multibootusb/ldlinux.sys
multibootusb/pmagic_2013_08_01/boot/syslinux/ldlinux.sys
multibootusb/pmagic_2013_08_01/boot/syslinux/parted-magic.bs
multibootusb/ubuntu-16.10-desktop-amd64/boot/grub/grub.cfg
multibootusb/ubuntu-16.10-desktop-amd64/boot/grub/loopback.cfg
multibootusb/ubuntu-16.10-desktop-amd64/isolinux/ldlinux.sys
multibootusb/ubuntu-16.10-desktop-amd64/isolinux/txt.cfg
multibootusb/ubuntu-16.10-desktop-amd64/isolinux/ubuntu.bs

Another thing I tested was copying the working stick (Crosair) to the not working one (Verbatim). No change, Verbatim still not working.

But the other direction is giving interesting results. Copying the not work stick (Verbatim) to the Voyager stick is working. Voyager is staring PMagic correctly.

So I assume the installation is basically ok. But the stick has some problems with PMagic.

I have three of the same Verbatim sticks. All behave the same. And Ubtuntu is working nicely on all of them. That is why I assume the hardware is not broken. I assume there is a strange relation between Verbatim USB sticks, PMagic and MultiBootUSB. But what?

BTW.: I have tried the same with YUMI. Same result. Crosair is working fine (PMagic and Ubuntu). Verbatim only with Ubtuntu.

Does anybody know if a problem with Verbatim USB sticks, PMagic and MultiBootUSB exists.

Any hint appreciated.

Thanks a lot
Matthias

PS.: I was looking for a MultiBootUSB forum but couldn't find one. If I'm wrong here please point me to the right place for asking this kind of questions.

#32 MultiBootUSB 8.5.0 No Module Found

Charlie Smith — Fri, 10 Feb 2017 15:59:46 -0000

I found the issue causing this problem and have taken corrective steps.

MultiBootUSB 8.5.0 now starts properly. Will try to actually create some entries this weekend.

Thanks