[Oberon] Problems with the 24/01/2006 release -probs with Startmenu.XML

[Rene Krywult]

I'm just trying to get started. I had the ancient "current" up and running.

So I burnt a Cd with the crazy-fresh and booted. Everything seemed to be 
OK, but unfortunately, the USB-Logitech-Mouse doesn't function. Also, in 
teh Log Window I get the following message at least 21 times: "No 
decoder found for NIL". Next I tried adding Boot6=AosUsbMouse.Install. 
Didn't help. Keyboard works, though, because Meta-Home and Meta-Cursor 
keys give a reaction.

So I downloaded all the ZIP-Files of the crazy-fresh and saved them to a 
FAT32-HDD. Then just started my old version (installed on a HDD), 
mounted the FAT32-HDD, opened the FAT:Install.Tool and followed through 
the Update-procedure. Everything worked fine. So I rebooted. The good 
thing: My mouse now works ok.

The bad thing: It seems that a certain "StartMenu.XML" could not be 
loaded. Unfortunately, it is nowhere in the distributed files, and it 
was not with the old files. I opened Oberon via command in the 
Log-Window and searched for anything resembling that XML, but it's not 
there. So I looked into all the ZIPs, but it'S not there. Apparently it 
is on the CD, but I can't access the CD from my installed BB version, 
and in Windows it simply is empty.

So, where do I get a StartMenu.XML?

Rene

>-- Aubrey McIntosh, Ph.D.
>   
>
>  
>
>>>>staubesv at student.ethz.ch 1/29/2006 8:10 AM >>>
>>>>        
>>>>
>Hi,
> 
>  
>
>>The Jan 24th Crazy Fresh release boots from a 1GB Toshiba flash memory stick.
>>The release does allow re-creation of the boot file AosUsb.Bin.
>>    
>>
>Cool!
> 
>  
>
>>There are a few issues, but they may be due to my odd Configuration strings.
>>    
>>
>What issues? The only configuration string you need extra for USB booting is "BootFromUsb=1" which forces the USB storage driver to block until a USB storage device has been found and put into the AosDisks.registry.
>Did it work with all host controller drivers linked into the kernel (AosUsbUhci, AosUsbOhci & AosUsbEhci), or have you only linked one if them into the kernel?
> 
>Cheers,
>Sven Stauber
>
>
>
>Well, I'll start with the release CD.
>
>I have a HP/Compaq D530 SFF (DC578AV) computer with internal DVD/ROM, PS/2 keyboard, and Logitech USB Mouse, and LiteOn CD burner model USB SOHR-5239SX.
>
>1.  This appears to be a dual processor machine.
>2.  Frequently, it does not complete the boot process, and re-boots.  On older releases there are a lot of interrupt traps, and presumably the internal DVD/Rom and Bluebottle don't play well together.
>3.  It is necessary to add the configuration string Boot6=AosUsbMouse.Install to be able to use the mouse.
>4.  When the Lite-On USB burner is connected, there are some configurations that never allow the mouse to work, and some which occasionally allow the mouse to work.
>
>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>Status                Mouse                   LiteOn
>fail                  USBHC1/1                USBHC1/2
>fail                  USBHC1/2                USBHC1/1
>fail                  USBHC0/2                USBHC1/2
>sporadic              USBHC0/2                USBHC1/2
>sporadic              USBHC0/1                USBHC0/2
>
>
>5.  When I edit the configuration strings, I have to type very quickly:  if the DVD/ROM motor stops or slows, the system will hard reboot.
>
>6.  After the system boots, I typically open either a BB editor, or Oberon.  When I do this, the system acts as if I have pressed the meta key---if the mouse bumps the edge of the screen, it scrolls.  When I depress and release the meta key, the system returns to good behavior.
>
>I have the results of PCITools.Scan, and the System.Log saved to USB stick, but was not going to post them unless they might be useful.
>
>
>
>--
>Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
>https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
>
>  
>