Singularity RDK

COMMENTED ISSUE: Does not boot on Hyper-V

Fabian030 — Fri, 09 May 2008 19:31:04 GMT

I have built Singularity and now i'm trying to boot it on Hyper-V (Windows Server 2008 x64)
I boot from World.Prototype.LegacyPC.MarkSweep.Min.MarkSweep.iso. It writes 1a2345 and nothing else.

On Virtual PC it boots correctly.

Is it possible to launch this OS on Hyper-V?
Comments: ** Comment from web user: Fabian030 **

How do I use the Etfs_BS.asm.diff to fix the issue with the S≡S error?
encountered that, too, on VirtualBox and vPC 2007

NEW POST: Work on Vista

dcoetzee — Fri, 09 May 2008 16:26:52 GMT

Christian24 wrote:
I installed it in another directory now and I installed .net Framework 1.1 and it works. I'm a bit confused now, because I thought you can still use older application with .net 3.5... Just like you can still run a .net 2.0 application using 3.5...

That's an understandable confusion generated by the .NET Framework branding. In reality the .NET Framework 3.0 is just the .NET Framework 2.0 with some additional components, so the base class libraries are the same. The .NET Framework 1.1, however, has a different set of base class libraries and runtime environment, and the 2.0 Framework does not provide backwards compatibility (but does provide support for side-by-side installation).
--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

NEW POST: Work on Vista

Christian24 — Fri, 09 May 2008 12:06:37 GMT

I installed it in another directory now and I installed .net Framework 1.1 and it works. I'm a bit confused now, because I thought you can still use older application with .net 3.5... Just like you can still run a .net 2.0 application using 3.5...

NEW POST: Help with "out of memory error" while using boottest.cmd

dcoetzee — Thu, 08 May 2008 22:55:56 GMT

prudhvighanta wrote:
I am trying to use "boottest.cmd mypc.vmc". Virtual PC doesn't start up. Instead, that gives me an error virtual pc cannot start up. Out of memory error.

I've responded to this issue in a more recent post. See:

https://www.codeplex.com/Thread/View.aspx?ProjectName=singularity&ThreadId=26470

--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

NEW POST: Use of nullable pointers

dcoetzee — Thu, 08 May 2008 22:54:13 GMT

Krusty wrote:
It appears after some limited testing that nullable pointers can't be used unless the compiler can prove that they are not null. Basically run-time null-pointer detection is not supported and possibly null pointers generate an error not a warning at compile time. As a result it seems that nullable member variables are not directly usable because they cannot be proved to be non-null in general due to concurrency issues. Is this true? ... What is the point of this nullable pointer error? Why not just do run-time testing like in normal C#? The end result is not to avoid the run-time check, but just to make the user code it by hand.

Hi Krusty. If you're receiving errors when attempting to use nullable member variables it's not because of the possibility of concurrency issues; the type system does not detect this type of error. To insert a runtime null check without explicitly writing one, you can "cast away the nullable" using (!), as in:

Foo f;
Foo! f2 = (!)f;

Generally, in code that makes wide use of non-null pointers, this type of conversion will not be frequently needed; most member variables can use non-null pointers. Let me know if you have any more questions.
--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

NEW POST: Sing# compiler

dcoetzee — Thu, 08 May 2008 22:46:27 GMT

thiago_farina wrote:
The next release of Singularity RDK 2.0 come with the sources of Sing# Compiler?

Although we can't firmly commit to anything yet, the sources of the Sing# compiler are likely to become available at a future time. No date has been set. The sources of the Bartok compiler, on the other hand, will almost certainly not become available.
--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

NEW POST: case sensitivity in path names

dcoetzee — Thu, 08 May 2008 22:42:16 GMT

Krusty wrote:
I'm implementing the ext2 filesystem and found that when you call File.Exists(), the path is converted to lower case before the query is done. Are paths and file names intended to be case-insensitive as on windows? The shell seems to be case sensitive when running "dir". "dir /INIT" fails...

Yes, a number of our libraries make the assumption that filenames are case-insensitive, because all the filesystems we support are case-insensitive. To add support for ext2, you may have to modify the codebase in order to remove this assumption (particularly CLR libraries such as System.Io). Let me know if you need any help with this, and apologies for the slow response.
--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

NEW POST: Network bootable image

dcoetzee — Thu, 08 May 2008 22:38:07 GMT

Is kernel.dmp a network bootable image? If so, can I use it for normal booting? Please let me know.

Not in the conventional sense; you can only network boot Singularity using the specific procedure described in the "Building and Running Singularity RDK 1.1" PDF. Although we take advantage of PXE to begin the network boot process, the rest of our network boot is done using a custom boot daemon using TFTP, and not using a conventional network boot server. Please read that PDF for more information, and let me know if you have any questions.
--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

NEW POST: Kernel.dmp image

dcoetzee — Thu, 08 May 2008 22:33:35 GMT

When I try to use "boottest.cmd mypc.vmc", is the Virtual PC supposed to boot singularity os? It is not happening my case. I get an error:
"Virtual PC could not be started because there is not enough memory in the host"
Is this problem specific to Virtual PC? Please let me know.

This is probably because you're either using a machine with limited RAM (such as 512MB of RAM) or have configured the virtual machine to use more memory than is available on your machine. Try configuring it to use 256MB; a full build of Singularity may exhibit lower performance with this limited amount of RAM, however. Try just building the distribution Tiny.proj to test your setup. Please let me know if you continue to experience difficulty with this.
--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

NEW POST: Other than Microsoft Virtual PC 2007

dcoetzee — Thu, 08 May 2008 22:30:06 GMT

prudhvighanta wrote:
Hi,

Can we try some other Virtual Machine software, say, VMWare, other than Microsoft Virtual PC to boot the built "kernel.dmp" image?
Do you think this will work?

Any suggestions?

Thanks,
Prudhvi

Hi Prudhvi. Although we relied on Virtual PC during development and have not tested our system for compatibility with the virtual hardware exposed by VMWare, I wouldn't be surprised if it worked anyway, since we boot correctly on many native platforms and VMWare simulates such a platform. Please try it and let me know if you encounter any problems. Good luck.
--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

NEW POST: Work on Vista

dcoetzee — Thu, 08 May 2008 22:27:30 GMT

Christian24 wrote:
Hi,
has anyone got it built on Vista?

Hi Christian, thanks for writing about your build trouble. The developers of Singularity regularly built on Vista during development, so it ought to work. This is just a hunch, but I suspect the number sign (#) in your build path may have something to do with it - try installing Singularity to a different directory. Also, make sure you have the necessary prerequisites; the .NET Framework 1.1 is required and is available from:

http://www.microsoft.com/downloads/details.aspx?familyid=262d25e3-f589-4842-8157-034d1e7cf3a3&displaylang=en

We also haven't experimented with the German version of the build tools, but I don't expect this to make a difference. I hope this helps. Write back if you're still encountering trouble.
--
Derrick Coetzee
Microsoft Research Operating Systems Group developer

COMMENTED ISSUE: Can't override System.ValueType.ToString() in pointerfree struct

a_davis — Wed, 07 May 2008 21:48:52 GMT

The following struct won't compile:

public pointerfree struct Buggy
{
public int data;

public override String ToString()
{
return "I wish this worked!";
}
}

It gives the error:
BugTest.sg(44,32): error CS0508: 'Buggy.Applications.Buggy.ToString()': cannot change return type when overriding inherited member 'System.ValueType.ToString()'

I tried copying the exact method from the ValueType.ToString() implementation, but it had the same problem. Is this a compiler bug, or am I doing something wrong?
I have attached my example console application project.
Comments: ** Comment from web user: a_davis **

The Sing# compiler consider the non-null assertions to be part of the type. So the signature of ToString() is "string! ToString()". Add "!" to your overload, i.e.:

public override string! ToString() { ... }

NEW POST: pointerfree structs don't compose correctly

a_davis — Wed, 07 May 2008 21:40:08 GMT

Can you be more specific? I've used pointerfree structs within pointerfree structs successfully.

NEW POST: Build Problem - Line too long

a_davis — Wed, 07 May 2008 21:37:03 GMT

Make sure the SINGULARITYROOT variable does not have any spaces in it. From looking at the log above, it looks like $(SINGULARITYROOT)\Foo\Bar is getting expanded to "C:\SINGUL~1 (space) \Foo\Bar". The compiler is then interpreting "C:\SINGUL~1" as a file (which it isn't, of course), and "\Foo\Bar" as another (also bogus) file.

NEW POST: Work on Vista

Christian24 — Sat, 03 May 2008 06:42:23 GMT

On my Vista it crashes during build.
I got these errors:
unknown built-in type 'System.Int32'; maybe a missing -reference option
ObsoleteAttribute.csi(38,34): undefined namespace or type 'String'
unknown built-in type 'System.Int32'; maybe a missing -reference option
ObsoleteAttribute.csi(41,34): undefined namespace or type 'String'
unknown built-in type 'System.Int32'; maybe a missing -reference option
unknown built-in type 'System.Boolean'; maybe a missing -reference option
ParamArrayAttribute.csi(21,46): undefined namespace or type 'Attribute'
unknown built-in type 'System.Int32'; maybe a missing -reference option
RequiredAttributeAttribute.csi(13,54): undefined namespace or type 'Attribute'
unknown built-in type 'System.Int32'; maybe a missing -reference option
RequiredAttributeAttribute.csi(16,44): undefined namespace or type 'Type'
unknown built-in type 'System.Int32'; maybe a missing -reference option
RequiredAttributeAttribute.csi(19,16): undefined namespace or type 'Type'
unknown built-in type 'System.Int32'; maybe a missing -reference option
SatelliteContractVersionAttribute.csi(24,61): undefined namespace or type 'Attri
bute'
unknown built-in type 'System.Int32'; maybe a missing -reference option
SatelliteContractVersionAttribute.csi(27,50): undefined namespace or type 'Strin
g'
unknown built-in type 'System.Int32'; maybe a missing -reference option
SatelliteContractVersionAttribute.csi(30,16): undefined namespace or type 'Strin
g'
unknown built-in type 'System.Int32'; maybe a missing -reference option
SecurityAttributes.csi(13,60): invalid namespace or type 'System.Attribute'
unknown built-in type 'System.Int32'; maybe a missing -reference option
ThreadStaticAttribute.csi(23,43): undefined namespace or type 'Attribute'
unknown built-in type 'System.Int32'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Baseattrs.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Baseattrs.ill -outdir:C:\C#\bas
e.obj\Interfaces /nostdlib /r:C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.ex
e -t:library AccessedThroughPropertyAttribute.csi AssemblyFileVersionAttribute.c
si AssemblyReflectionAttributes.csi CLSCompliantAttribute.csi CompilerGlobalScop
eAttribute.csi ConditionalAttribute.csi CustomConstantAttribute.csi DateTimeCons
tantAttribute.csi DebuggerAttributes.csi DecimalConstantAttribute.csi Discardabl
eAttribute.csi IndexerNameAttribute.csi InteropServices.csi IsVolatile.csi Layou
tKind.csi MethodImplAttribute.csi NeutralResourcesLanguageAttribute.csi Obsolete
Attribute.csi ParamArrayAttribute.csi RequiredAttributeAttribute.csi SatelliteCo
ntractVersionAttribute.csi SecurityAttributes.csi ThreadStaticAttribute.csi Base
Attrs.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Baseattrs.ill & del C:\C#\b
ase.obj\Interfaces\Baseattrs.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts Baseattrs.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\Console\Console.csproj (Standardziele):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Console.ill -outdir:C:\
C#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes
.ill=kernel.exe -t:library ConsoleOutput.csi ConsoleInput.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\Console.ill & d
el C:\C#\base.obj\Interfaces\Console.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
ConsoleOutput.csi(28,34): undefined namespace or type 'String'
unknown built-in type 'System.Int32'; maybe a missing -reference option
unknown built-in type 'System.Char'; maybe a missing -reference option
unknown built-in type 'System.Array'; maybe a missing -reference option
unknown built-in type 'System.Int32'; maybe a missing -reference option
unknown built-in type 'System.Int32'; maybe a missing -reference option
unknown built-in type 'System.Object'; maybe a missing -reference option
unknown built-in type 'System.String'; maybe a missing -reference option
unknown built-in type 'System.Int32'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Console.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Console.ill -outdir:C:\C#\base.
obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill=ker
nel.exe -t:library ConsoleOutput.csi ConsoleInput.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Console.ill & del C:\C#\bas
e.obj\Interfaces\Console.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts Console.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\Memory\Memory.csproj (Standardziele):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Memory.ill -outdir:C:\C
#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.
ill=kernel.exe -t:library Memory.csi SharedHeap.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\Memory.ill & de
l C:\C#\base.obj\Interfaces\Memory.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
SharedHeap.csi(21,13): undefined namespace or type 'UIntPtr'
unknown built-in type 'System.Int32'; maybe a missing -reference option
SharedHeap.csi(22,13): undefined namespace or type 'UIntPtr'
unknown built-in type 'System.Int32'; maybe a missing -reference option
unknown built-in type 'System.UInt32'; maybe a missing -reference option
unknown built-in type 'System.ValueType'; maybe a missing -reference option
unknown built-in type 'System.ValueType'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Memory.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Memory.ill -outdir:C:\C#\base.o
bj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill=kern
el.exe -t:library Memory.csi SharedHeap.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Memory.ill & del C:\C#\base
.obj\Interfaces\Memory.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts Memory.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\Diagnostics\Diagnostics.csproj (Standardziele):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Diagnostics.ill -outdir
:C:\C#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Baset
ypes.ill=kernel.exe -t:library Diagnostics.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\Diagnostics.ill
& del C:\C#\base.obj\Interfaces\Diagnostics.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Diagnostics.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Diagnostics.ill -outdir:C:\C#\b
ase.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill
=kernel.exe -t:library Diagnostics.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Diagnostics.ill & del C:\C#
\base.obj\Interfaces\Diagnostics.ill /q & exit 1)-Befehl wurde mit Code 1 beende
t.
Erstellen des Projekts Diagnostics.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\Directory\Directory.csproj (Standardziele):

__________________________________________________
Das Projekt C:\C#\base\Interfaces\Directory\Directory.csproj erstellt C:\C#\base
\Interfaces\Kernel\Kernel.csproj (Build Ziel(e)):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Kernel.ill -outdir:C:\C
#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.
ill=kernel.exe -t:library IoMemory.csi Kernel.csi Process.csi PerfCounters.csi |
| (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\Kernel.ill & de
l C:\C#\base.obj\Interfaces\Kernel.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
unknown built-in type 'System.Object'; maybe a missing -reference option
unknown built-in type 'System.Object'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Kernel.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Kernel.ill -outdir:C:\C#\base.o
bj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill=kern
el.exe -t:library IoMemory.csi Kernel.csi Process.csi PerfCounters.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Kernel.ill & del C:\C#\base
.obj\Interfaces\Kernel.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts Kernel.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Directory\Directory.csproj erstellt C:\C#\base
\Interfaces\Security\Security.csproj (Build Ziel(e)):

__________________________________________________
Das Projekt C:\C#\base\Interfaces\Security\Security.csproj erstellt C:\C#\base\I
nterfaces\Loader\Loader.csproj (Build Ziel(e)):

__________________________________________________
Das Projekt C:\C#\base\Interfaces\Loader\Loader.csproj erstellt C:\C#\base\Inter
faces\IoSystem\IoConfig.csproj (Build Ziel(e)):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\IoConfig.ill -outdir:C:
\C#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetype
s.ill=kernel.exe -t:library IoConfig.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\IoConfig.ill &
del C:\C#\base.obj\Interfaces\IoConfig.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
IoConfig.csi(24,16): undefined namespace or type 'String'
unknown built-in type 'System.Int32'; maybe a missing -reference option
unknown built-in type 'System.Array'; maybe a missing -reference option
IoConfig.csi(25,16): undefined namespace or type 'String'
unknown built-in type 'System.Int32'; maybe a missing -reference option
unknown built-in type 'System.Array'; maybe a missing -reference option
unknown built-in type 'System.String'; maybe a missing -reference option
unknown built-in type 'System.Object'; maybe a missing -reference option
unknown built-in type 'System.Object'; maybe a missing -reference option
unknown built-in type 'System.Object'; maybe a missing -reference option
unknown built-in type 'System.Object'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\IoConfig.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\IoConfig.ill -outdir:C:\C#\base
.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill=ke
rnel.exe -t:library IoConfig.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\IoConfig.ill & del C:\C#\ba
se.obj\Interfaces\IoConfig.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts IoConfig.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\Drivers\Drivers.csproj (Standardziele):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Drivers.ill -outdir:C:\
C#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes
.ill=kernel.exe -t:library Drivers.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\Drivers.ill & d
el C:\C#\base.obj\Interfaces\Drivers.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Drivers.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Drivers.ill -outdir:C:\C#\base.
obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill=ker
nel.exe -t:library Drivers.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Drivers.ill & del C:\C#\bas
e.obj\Interfaces\Drivers.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts Drivers.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\Hal\Hal.csproj (Standardziele):

__________________________________________________
Das Projekt C:\C#\base\Interfaces\Hal\Hal.csproj erstellt C:\C#\base\Interfaces\
Hal\Processor.csproj (Build Ziel(e)):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Processor.ill -outdir:C
:\C#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetyp
es.ill=kernel.exe -t:library Processor.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\Processor.ill &
del C:\C#\base.obj\Interfaces\Processor.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Processor.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Processor.ill -outdir:C:\C#\bas
e.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill=k
ernel.exe -t:library Processor.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Processor.ill & del C:\C#\b
ase.obj\Interfaces\Processor.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts Processor.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\Hypercall\Hypercall.csproj (Standardziele):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Hypercall.ill -outdir:C
:\C#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetyp
es.ill=kernel.exe -t:library Hypercall.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\Hypercall.ill &
del C:\C#\base.obj\Interfaces\Hypercall.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Hypercall.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Hypercall.ill -outdir:C:\C#\bas
e.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill=k
ernel.exe -t:library Hypercall.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Hypercall.ill & del C:\C#\b
ase.obj\Interfaces\Hypercall.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts Hypercall.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\NVidiaDrivers\NVidiaDrivers.csproj (Standardziele):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\NVidiaDrivers.ill -outd
ir:C:\C#\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Bas
etypes.ill=kernel.exe -t:library NVidiaDrivers.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\NVidiaDrivers.i
ll & del C:\C#\base.obj\Interfaces\NVidiaDrivers.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\NVidiaDrivers.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\NVidiaDrivers.ill -outdir:C:\C#
\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.i
ll=kernel.exe -t:library NVidiaDrivers.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\NVidiaDrivers.ill & del C:\
C#\base.obj\Interfaces\NVidiaDrivers.ill /q & exit 1)-Befehl wurde mit Code 1 be
endet.
Erstellen des Projekts NVidiaDrivers.csproj beendet - Fehler beim Erstellen.
__________________________________________________
Das Projekt C:\C#\base\Interfaces\Interfaces.proj erstellt C:\C#\base\Interfaces
\Shell\Shell.csproj (Standardziele):

C:\C#\base\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Shell.ill -outdir:C:\C#
\base.obj\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.i
ll=kernel.exe -t:library Shell.csi || (
echo Deleting corrupted output - C:\C#\base.obj\Interfaces\Shell.ill & del
C:\C#\base.obj\Interfaces\Shell.ill /q & exit 1)
csic: can't find "C:\C#\base.obj\Interfaces\Basetypes.ill=kernel.exe"
unknown built-in type 'System.Object'; maybe a missing -reference option
unknown built-in type 'System.Int32'; maybe a missing -reference option
Shell.csi(20,37): undefined namespace or type 'String'
unknown built-in type 'System.Int32'; maybe a missing -reference option
unknown built-in type 'System.Array'; maybe a missing -reference option
Deleting corrupted output - C:\C#\base.obj\Interfaces\Shell.ill
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: Der C:\C#\ba
se\Build\csic.exe -out:C:\C#\base.obj\Interfaces\Shell.ill -outdir:C:\C#\base.ob
j\Interfaces /nostdlib /unsafe /r:C:\C#\base.obj\Interfaces\Basetypes.ill=kerne
l.exe -t:library Shell.csi || (
C:\C#\base\Targets\InterfaceAssembly.targets(183,5): error MSB3073: echo D
eleting corrupted output - C:\C#\base.obj\Interfaces\Shell.ill & del C:\C#\base.
obj\Interfaces\Shell.ill /q & exit 1)-Befehl wurde mit Code 1 beendet.
Erstellen des Projekts Shell.csproj beendet - Fehler beim Erstellen.
Log file: C:\C#\base.obj\MSBuildLogs\msbuild-LONDON-5.00-083925.log
Build Failed.

C:\C#\base>^A
and the assembler always crashes during built

NEW POST: Work on Vista

prudhvighanta — Sat, 03 May 2008 03:14:24 GMT

Christian24 wrote:
Hi,
has anyone got it built on Vista?

Hi,

I could build the "World" on vista. I am able to boot it from Virtual PC.But, I am having problems with my debugger. I am not able to start the debugger. When I start the debugger, I see an error message "the command line arguments cannot specify more than one kind of debugging to start".This is the only problem I have been facing with Vista.

NEW POST: Work on Vista

Christian24 — Fri, 02 May 2008 22:56:36 GMT

Hi,
has anyone got it built on Vista?

NEW POST: Kernel.dmp image

thiago_farina — Fri, 25 Apr 2008 21:09:10 GMT

Hi,

if your enviroment is set correctly, then the process create a vmc image with this name: pxe.vmc in boot directory.

so to use the command boottest.cmd mypc.vmc you need first rename pxe.vmc.

type this in console: copy boot\pxe.vmc mypc.vmc
then: boottest.cmd mypc.cmd

I hope this helps

NEW POST: Other than Microsoft Virtual PC 2007

prudhvighanta — Thu, 24 Apr 2008 19:54:21 GMT

Hi,

Can we try some other Virtual Machine software, say, VMWare, other than Microsoft Virtual PC to boot the built "kernel.dmp" image?
Do you think this will work?

Any suggestions?

Thanks,
Prudhvi

NEW POST: Network bootable image

prudhvighanta — Wed, 23 Apr 2008 15:42:38 GMT

Hi,

Is kernel.dmp a network bootable image? If so, can I use it for normal booting? Please let me know.

Thanks in advance,
Prudhvi