Oberon Community Platform Forum

The code in the repository is newer than the alpha ISO. So, for instance, in WinAos (updated from the repository with svn in Linux, then executed with wine*), there is a new guibuilder tool. My Native A2 box cannot, of course, update itself from the repository, so should I use ftp to grab the updated files from the Linux box? Or dare one hope for a new ISO?


*which works well. Certainly it works better than UnixAos.

I recommend building the current ISO image from the repository. This can be done quite easily (and quickly) using WinAos. Make sure that the folder ../Test/ exists and follow the steps in Build.Tool.

It probably works very well in WinAos. Except on Linux with "wine WinAos.EXE". Because this happens at about 20% build:


wine client error:153: pipe: Too many open files
err:ntdll:RtlpWaitForCriticalSection section 0x411928 "?" wait timed out in thread 0016, blocked by 0013, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x411928 "?" wait timed out in thread 0016, blocked by 0013, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x411928 "?" wait timed out in thread 0016, blocked by 0013, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x411928 "?" wait timed out in thread 0016, blocked by 0013, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x411928 "?" wait timed out in thread 0016, blocked by 0013, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x411928 "?" wait timed out in thread 001c, blocked by 0013, retrying (60 sec)

i think this is easily done in less than 5 clicks. you'll have an instant new ISO

Not running WinAos in Linux with wine you won't.

hmm, where should ../Test/ be.

Is it relative to WinAOS.exe or relative to Build.Tool?

Regards
    Bernhard

Work directory

Спасибо (thanks also to google translate) ...

Ok, I successfully created the A2 ISO image of SVN Revision 3620 (yesterday afternoon) and I have put it here: ftp.lrz.de/transfer/BlueBottle-A2/ (ftp://ftp.lrz.de/transfer/BlueBottle-A2/) ... no guarantees, this is the first image I created, have fun.

Bernhard

Beware: At least, when booted from CD, the Oberon subsystem is defunct, i.e. only a black background in a dead window (no chance to close it).

Excellent work. I am downloading it now.

I unwisely installed it just now and will have to reinstall a previous ISO. The compiler is broken.

Hold on a minute. I am not sure the compiler is broken. Maybe my old code modules have some subtle inconsistency with the new system. Investigating.

What compiler does PET use now? Is it still Paco (PC.Mod)?

Progress progress progress. The new ISO works. Once more the assembler has been changed! Please release source for srE.Mod that compiles! I would paste the code I am asking about here, but I can't because FTP and USB are both not working from that box. I'll type a line or two:

     MOV     EDI, 8[EBP] ; dest  = ADR(out)         Error: Carriage Return Expected

     MOV     4[ESP], EBX                                    Error: addressing mode not allowed

MOV EDI, 8[EBP] must now be written as
MOV EDI, [EDI+8]

got it

I don't know if everything in this new alpha works, but the tracer now compiles and runs.

Revision 3630 is here: ftp.lrz.de/transfer/BlueBottle-A2/A2_Rev-3630.iso (ftp://ftp.lrz.de/transfer/BlueBottle-A2/A2_Rev-3630.iso)

Works well. Except that networking doesn't start up.

on my dual PIII (see: http://www.ocp.inf.ethz.ch/wiki/Documentation/HardwareCompatibility#toc3) neither Rev 3620 nor 3630 boots from CD (via PLoP)  ...

I have traced it on the serial port:

It hangs with a black screen indefinitely on loading something like USBKeyboard (I don't have the log at hand and could not find any name which rings a bell when looking at PartitionsSetConfig in the Build.Tool with which I created the images).

so: more to come later ...

Try to disable automatic hardware detection (don't call PCITools.DetectHardware). This also causes USB device drivers to be loaded.

Hi Sven,

although I scanned the Partitions.SetConfig arguments and the Configuration.XML (located in ../Test/System.zip) on my build system, I could not find the place where PCITools.Detecthardware might be called.

In the mean time I realized that this system had both a PS/2 and a USB mouse connected. I removed the USB mouse and now it boots nicely.

Should I try anything further?

Apparently the reason for the hanging is the combination of an USB mouse and a PS/2 style keyboard. I attached the serial loog of several attempts (successful and hanging during initializing the usb keyboard).

regards
   Bernhard
-----------------------------
thread continued here: www.ocp.inf.ethz.ch/forum/index.php/topic,439.0.html (http://www.ocp.inf.ethz.ch/forum/index.php/topic,439.0.html)

Which was of course a hardware issue.