After 2 days of trouble free operation since I upgraded from MOS 3.0 to 3.1, today I got 2 error messages and I'm unable to launch OWB (I'm posting from my PC). The error mesaages are:

Startup Sequence
1. Need version 0 of bedsocket.library
2. Need version 0 of open url.library.

Interesting enough, yesterday I only used OWB and did not download or installed anything. It just happened overnight after powering off.

What can be done to fix these issues and/or where to find those missing libraries? More importantly, is there a way to avoid this from happening again?

Please help.

[ Edited by WeiXing3D 13.07.2012 - 22:23 ]

Had left this hoping someone more knowledgable would reply, but...

Something is very wrong:
bsdsocket.library doesn't exist on disk, it's created dynamically in memory. If this isn't found, network has not been started.
Openurl.library should be in sys:morphos/libs (iirc), so should always be found.

sys:morphos/ (everything in this path) should never be touched, added to or removed by the user (there are one or two specific exceptions).

It's unclear - are the error messages occuring on system startup, or when launching OWB?

This only happens if the network is not ready.

Depending on the DHCP/network speed the system may be up, but network is not. Sometimes I have to wait for about around 10 seconds here, too.

Also check your network cable is plugged in correct.

Geit

This is happening right after startup, and when I try to launch OWB.

All cables are plugged in. Like I said, this started to happen overnight. I don't know whether this is a coincidence or not, but I never had any problems while running 3.0.

If I reinstall 3.1 the system runs fine, and OWB works, but the problem comes back the next time I boot up.

The thing is that my system is useless this way I hope someone can help.

It could be that the DHCP is failing/lagging for you for some reason. You could try using a static IP address.

Have you, by any chance, created sys:s/network-startup to run c:setclockntp to set the correct time (as suggested by Geit in this thread?

If so, have you accidentally saved it as sys:morphos/s/network-startup instead, thus overwriting the existing script (which actually starts the network stack)?

If so, simply restore sys:morphos/s/network-startup from the ISO and copy your customised script to sys:s/network-startup.

(Personally, I think it is wise to avoid duplicating system-script names like this - better to call your your customised one "user-netstart" or something instead.)

[ Edited by boot_wb 14.07.2012 - 14:37 ]

Just tested on a vanilla installation: What I suggested above would cause unable to find bsdsocket.library, but doesn't fail get to looking up openurl.library. Neither does it state required version. Errors are only returned when starting OWB through cli, not when double-clicking the icon.

Having network cable unplugged with network left at default settings (dhcp) simply causes interface to revert to some default IP, but doesn't prevent netstack (or OWB) starting. No errors.

Don't know, will leave it to the experts.

(slight ot: I couldn't find where mossys:s/network-startup is called from, yet it clearly runs on boot. What runs it at boot-time?)

I thank you all who are trying to help. You are giving me too much credit though.

I have only been using MOS for less than a month now. I don't even know how to do the things that @boot_wb mentions above, so how could I have done that?

The truth is that since I BOUGHT my license for 79 Euros, all I have done is installed Grunch, Hurrican, Foobillard and surfed the web using OWB. I managed to do all that while running MOS 3.0. Then when I upgraded to 3.1 I started to get all these error messages. The installation seems to run fine and it completes; sometimes (I've done this several times now, trying to fix errors after installation), the installation doesn't work because it cannot find a USB stick that I used before to install my morphos key. This happens with the USB stick in or out. Then after I try again, the installation starts, apparently, normally.

After installing everything seems to work OK and I can use OWB and install the same software I mentioned above. Then when I power the computer off and come back to use it again, I get those two messages. All other installed software runs fine.

The messages pop up right after start up in sequence.

Is it possible that my CD burnt with 3.1 is not completely good and the installation therefore is not good? Should I restore my Mac Mini back to Mac OS X and start installation all over again? What drastic measure can I take to restore my system and make some use of my 79 Euro investment?

I'd definately try burning a new disc, just in case. CD burning is a fickle thing sometimes

runequester,
Quote:

Without Internet in Mac Mini MOS, can I download and burn the CD in my PC?

yeah, that's what I did for my powermac.

Quote:

Yes of course!

[ Edited by takemehomegrandma 14.07.2012 - 18:49 ]

My Mac Mini doesn't lie MOS 3.1; it's the only conclusion I carrive to for now. I burnt 2 different versions of MOS 3.1 in 2 different CDs. Both CDs were burnt in 2 different PC's; both giving the same checksum.

With neither installation I can run OWB. They either give staup error messages and OWB woul not open, or OWB woud open but be unable to solve the host.

So, I re-installed 3.0 back in my Mac Mini, and I'm using it to write this post.

Would it be possible to have someone in the Morphos development team to look into this? I really need some expert help to resolve these issues. After all, as most of you, I paid for my key, and I haven't even started to enjoy the ride yet.

I really hope for someone to throw me a lifeline. In the meantim, i will be living in the past with 3.0. It doesn't feel good to be left out though.