I'm in Wary5.5-Live and had a hd-partition (sda1) and 1 (sdb5) of 2 partitions on a USB-stick mounted (sdb1 unmounted).
after some time sdb5 was spontaneously unmounted and the stick registered back as sdc1 and 5.
I've been all the way up to sdi1 and 5 already (CTRL-Alt-Backspace was necessary because SeaMonkey bogged down the system and killing was impossible and this reset it back to sdb1 and 5).

keeping a window open in ROX doesn't help, the message says 'Directory missing/deleted'

could this have anything to do with a time-out on wake-up of the USB-stick??
if so, can I do something about it in a Live-session (also if it has another cause)??

have located that dir, but want to check first if the hub is causing this. now the stick is plugged directly in the port of the PC. if nothing strange happens over the next 24 hrs I'll restore the old situation and THEN delete as suggested: before or after I plug in the stick in the hub?

have located that dir, but want to check first if the hub is causing this. now the stick is plugged directly in the port of the PC. if nothing strange happens over the next 24 hrs I'll restore the old situation and THEN delete as suggested: before or after I plug in the stick in the hub?

once I've chosen that, what will happen and what input do I need to give to get back into the desktop or is this done automatically (plse don't forget I'm a relative newbie on the more intricate goings-on in linux)?

once I've chosen that, what will happen and what input do I need to give to get back into the desktop or is this done automatically (plse don't forget I'm a relative newbie on the more intricate goings-on in linux)?

It should happen super-ultra-archi-magically

Just in case it does not happen... (probability one in millions due to a non correct planetary alignment)
if you are left in a text mode console (like the ancient D.O.S.) typing

#xwin

will load the graphical server (who shows the desktop) again.

The graphical server can be killed with Ctrl+Alt+Backspace with no harm except that it also kills your open apps and looses the unsaved work.

Wary 5.5 is buggy with respect to usb drive assignments... something which I mentioned to BarryK earlier this year. If this is a major concern, I recommend that you install Wary 5.3 instead.

Monsie

I've got no problem working around this (in the mean time I'm 1letter up already, so the erasing of the dir and restarting X-server didn't do the trick). before I save to the USB I check what the assignment is and adjust accordingly.

I've got no problem working around this (in the mean time I'm 1letter up already, so the erasing of the dir and restarting X-server didn't do the trick). before I save to the USB I check what the assignment is and adjust accordingly.

Have you some hardware drives attached to your machine which you do not use? Example: a printer with a card-reader. If you boot in this case puppy with the printer on, the drive b could be assigned to the card reader of the printer...

I've got no problem working around this (in the mean time I'm 1letter up already, so the erasing of the dir and restarting X-server didn't do the trick). before I save to the USB I check what the assignment is and adjust accordingly.

Have you some hardware drives attached to your machine which you do not use? Example: a printer with a card-reader. If you boot in this case puppy with the printer on, the drive b could be assigned to the card reader of the printer...

nope!
just a mounted hdd and, via the 4-port hub, the stick (1 of 2 part. mounted).
the first partition holds the Save-file so I'm curious if this sponteaneous unmounting etc. will also happen if I run from USB. should that be the case, than I do expect problems when I want to shut down and the file has to be updated. if it's no longer sdb1 but f.i. sdf1, will puppy find it?

this question has now been answered:
even though at start-up sdb1 with the save-file has an orange square around it, also this partition is, together with the other sdb5 unmounted (wether sdb5 is mounted or not) and logged off and logged on again as sdc1 and 5.

if I then try to save the puppy-file (so the save-file also has the latest changes) it goes on and saves to sdb1, even though sdb1 isn't there anymore and the PC hangs.

the same happens if I try to shutdown. puppy doesn't register that sdb1 isn't there anymore and tries to save anyway! and hangs!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum