Oberon Community Platform Forum
October 16, 2019, 02:29:39 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: 1 2 [3] 4 5 ... 10
 21 
 on: August 17, 2015, 03:39:06 PM 
Started by peasthope - Last post by peasthope
Date:   Sat, 15 Aug 2015 17:18:00 -0700
To:   oberon@lists.inf.ethz.ch
> UsbEhci.Mod 6847 fails to compile and is 4 months old. 

A little more pertinent:
I'm building A2 for I386.  UsbEhci imports UsbHcdi.  For UsbHcdi the
compiler complains that Machine.Address32 is an undeclared identifier. 
http://easthope.ca/A2UsbHcdiErrors.png

Address32 is in I386.Machine.Mod.  Error?

Thanks,                        ... Peter E.


 22 
 on: August 07, 2015, 06:15:33 AM 
Started by peasthope - Last post by peasthope
Hi,

Months ago there was a mention that the version number is
recorded in Unix.I386.Machine.Mod.Version.  I can't cite the
discussion.

After updating the local repository, revising Unix.I386.Machine.Mod.Version
accordingly and recompiling, the new version number is in
Machine.Obj.  The old number remains on the window frame. (?)
The only copy of the old number reported by a Find search of all 
Obj files is in CryptoCAST.Obj .  Ideas?

Thanks,                             ... Peter E.



 23 
 on: April 27, 2015, 12:14:13 PM 
Started by dimon - Last post by dimon
thanks

 24 
 on: April 27, 2015, 09:24:51 AM 
Started by dimon - Last post by Serge
You can edit the Release.Tool file, place FoxBasic.Mod before StaticLinker.Mod in PACKAGE Compiler

 25 
 on: April 24, 2015, 08:36:38 AM 
Started by dimon - Last post by dimon
I can't build release.

I did:

1. in win:

D:\Work\A2\Work>svn update
Updating '.':
U    source\FoxSemanticChecker.Mod
U    source\FoxGlobal.Mod
U    source\FoxPrintout.Mod
U    source\StaticLinker.Mod
U    source\FoxBackend.Mod
U    source\WMTextView.Mod
Updated to revision 6056.

D:\Work\A2\Work>

2. in A2:

Release.Build --build WinAos ~
Loading package description file Release.Tool ... done.
WinAos: Check if all files are present... 3s done.
WinAos: Check modules and imports... 0s done.
   Release.Tool@13877   error: WinAos: Import FoxBasic not found in file StaticLinker.Mod
   Release.Tool@13877   error: WinAos: Import FoxBasic not found in file StaticLinker.Mod

But StaticLinker.Mod imports FoxBasic:

MODULE StaticLinker;   (* AUTHOR "negelef"; PURPOSE "Static Object File Linker"; *)

IMPORT Commands, Options, Diagnostics, Files, GenericLinker, ObjectFile, BitSets, Strings, Streams, FoxBasic, D:=Debugging, Basic:=FoxBasic;

TYPE
...


What's wrong?

 26 
 on: April 09, 2015, 04:51:31 AM 
Started by peasthope - Last post by peasthope
Reference
http://www.ocp.inf.ethz.ch/forum/index.php/topic,927.0.html

A2.iso was built with customizations in Release.Tool.
BiosFreePCI.Mod replacing I386.PCI.Mod,
I386, WIN, UNIX { I386.Math.Mod I386.MathL.Mod }
replacing
I386, WIN, UNIX { XMM.I386.Math.Mod XMM.I386.MathL.Mod }
and with COMPILEOPTIONS "--useFPU".

The A2.iso was run under QEMU to install A2 to a CF card.  
The CF was plugged into an old Pentium S machine as IDE0  
and the machine was started with ATADetect=legacy .

The serial trace is visible at http://easthope.ca/V24.Log .
The CF is identified correctly.  Then "IDE0 Issue: 020" is repeated
until access to the file system fails.  

I386.ATADisks.Mod has
Code:
PROCEDURE NewCommand
...
(* mode std ext dma dma ext
write 30 34 CA 35
read 20 24 C8 25
*)
...
CMD[4] := 20H; CMD[5] := 24H; CMD[6] := 0C8H; CMD[7] := 25H;

From that and the trace, I conclude that A2 has identified the CF but fails to
read a sector or sectors from it.  Nevertheless, NO can run from the CF, IDE0#1
and has been tested in IDE0#2, suggesting the CF card is OK.  

So I puzzle that NO can read the CF but A2 can not.  Is anyone running a recent
A2 from a CF card?  Any peculiar configuration applied?  If someone has a working
A2 system, installed by a procedure similar to that described above, a little
information could be helpful.  Other ideas?

Thanks,                   ... Peter E.

 27 
 on: April 08, 2015, 03:55:28 PM 
Started by peasthope - Last post by peasthope
Continuing the topic;
A2.iso was built with BiosFreePCI.Mod and run under QEMU to install A2 to
a CF card.  The CF was plugged into an old Pentium S machine as IDE0.  
The serial trace at power up is visible at
http://easthope.ca/V24.Log .
More details in the AOS section of the forum.
http://www.ocp.inf.ethz.ch/forum/index.php/topic,928.msg3017.html#msg3017

Thanks,                   ... Peter E.



 28 
 on: April 08, 2015, 01:01:58 AM 
Started by peasthope - Last post by peasthope
Currently using rev.6033 and aosrep/source 6034.

When an A2.iso is built, the following Kernel Log is produced.
The reports of "Duplicate file found" are from /usr/aos/source/*.Mod
duplicating ~/build/aosrep/source/*.Mod.  Correct?  And, given that
~/build/aosrep/source takes precedence, the duplication is harmless. 
Correct?

Thanks,                  ... Peter E.

Quote
Autostart: executing SkinEngine.Unload
ZeroSkin already loaded
Autostart: executing WMRestorable.Load Auto.dsk
{P cpuid= 0, pid= 46 Starting logger}
WMRestorable: Loading desktop from Auto.dsk...
Autostart: executing WMNavigate.Open -vs 1 0 0 Navigation:TaskList
Autostart: executing Kernel.GC
Autostart: executing WMTextView.EnablePiemenu
Piemenu enabled
SyntaxHighlighter: Auto-loading SyntaxHighlighter.XML ... done.
   ReleaseTree@13760   warning: Duplicate file found: StringPool.Mod
   ReleaseTree@13775   warning: Duplicate file found: Diagnostics.Mod
   ReleaseTree@13817   warning: Duplicate file found: BitSets.Mod
   ReleaseTree@13829   warning: Duplicate file found: ObjectFile.Mod
   ReleaseTree@13844   warning: Duplicate file found: GenericLinker.Mod
   ReleaseTree@15419   warning: Duplicate file found: XMM.I386.Math.Mod
        ...
   ReleaseTree@38742   warning: Duplicate file found: OPA.Data
Backup created  in source/Release.Tool.Bak
Backup created  in source/Release.Tool.Bak
   ReleaseTree@416   error: HEADER section expected
   ReleaseTree@13768   warning: Duplicate file found: StringPool.Mod
   ReleaseTree@13783   warning: Duplicate file found: Diagnostics.Mod
        ...
   ReleaseTree@38801   warning: Duplicate file found: OPA.Data
Backup created  in source/Release.Tool.Bak
   ReleaseTree@416   error: HEADER section expected
Backup created  in source/Build.Tool.Bak
Backup created  in source/Build.Tool.Bak
Backup created  in source/Build.Tool.Bak
DiskFS: Index not found on RAM0
DiskFS: Scanning RAM0... marking     0 files
DiskFS: 7999992K of 8000000K available on RAM0
DiskFS: Index not found on VDISK0#0
DiskFS: Scanning VDISK0#0... marking     0 files
DiskFS: 148964K of 148972K available on VDISK0#0
{P cpuid= 0, pid= 165 Files: 762 open files on VDISK0#0}
DiskFS: Map saved on VDISK0#0
{P cpuid= 0, pid= 170 Files: 1 open files on RAM0}
DiskFS: Map saved on RAM0

Some lines replaced by ... for brevity.

 29 
 on: March 10, 2015, 03:33:53 PM 
Started by leledumbo - Last post by fld
Yes it is possible.
The problem is that you don't have access to the
sources of large software projects 'Voyager' and 'Ants'.
These are not really needed. You can disable them
if you modify the section A2 in the file Release.Tool:
   
    A2{
       . . .
       EXCLUDEPACKAGES "OberonVoyager OberonAnts"
       . . .
   }


-- G√ľnter

 30 
 on: March 07, 2015, 10:07:15 AM 
Started by leledumbo - Last post by leledumbo
Is it possible to do so from UnixAOS? The tool fails when it searches for Oberon.vyCompatibility.Mod, though I found Win32.Oberon.vyCompatibility.Mod. The module itself depends on many others Oberon.*.Mod but represented as Win32.Oberon.*.Mod.

Pages: 1 2 [3] 4 5 ... 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!