Re: [Vectorlinux-devel] First beta rollout of SOHO 6.0 (testing) B1.6/1.7

[Newt <gen...@gm...>]

Hello,

I attempted both methods mentioned below, and I had great expectations that one of
them would work, but unfortunately neither fixed the issue. I even tried a
standard CD install with no luck.

However, after much playing and comparing 'ps ax' screens between the IDE and
runtime I think I've determined my problem. I think it's directly related to my
built-in/usb card reader. I kept noticing that the installer was hanging on the
command: "sh -c parted /dev/sdd print | grep -i partition table: | cut -f2 d:"
(each of these would then be listed individually in the processes immediately
following the combined statement). After checking probedisk I determined that sdd,
sde, sdf, sdg are individual slots on the card reader. With the installer running
and stalled, I started killing the individual 'parted' processes and as I killed
them a new but different statement would appear for a total of 2 parted statements
per device. After killing the 8 processes (2 process for 4 devices), the throbber
began spinning again and the installer continued by finding the CD. At this point
I bailed out of the installation to report my findings.

I guess the strangest part (to me) is why the IDE would run the installer normally
but directly from the runtime would not. I did notice that when running the
installer from the IDE a separate process (gbx2 -f -d .... /speedy --) would run
the project. I guess this would indicate the the IDE runs the project itself while
the runtime has to run a binary/compiled version??

More (possibly unnecessary) info:

When I would manually run the command "parted /dev/sdd print" I would receive an
error stating: "Error opening /dev/sdd: No medium found. Retry/Cancel?"

When I would manually run the command "sh -c parted /dev/sdd print", the actual
parted command interpreter would start up using /dev/hda and I would have to
manually 'quit'.

Cheers, newt

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

M0E wrote:
ML> Try this
ML> load the gambas IDE
ML> Instead of clicking the play button, click on Project -> Make -> Executable
ML> This will create a brand new binary based off the current code.
ML> Once that is done, exit the IDE, and execute the new binary
./speedy.gambas >> gui.log &

Uel wrote:
ua> I just found out we are not using the latest installer there after all.
ua> there are 3 different installer binaries in the speedy folder.
ua> Newt,
ua> can you chmod +x vinstall-ng,gambas.r938 and then run it from a terminal to
ua> confirm that it works or not?