Daydream ROM box kit

[schubige]

I just uploaded a new darkmatter version: http://1drv.ms/242hxbI. It fixes a bug in the ethernet driver for NeXT turbo hardware. This bug was there for more than 20 years now and finally got fixed :-)
An update is highly recommended for all users with turbo hardware as well as people using darkmatter together with Previous.

[NeXTnewbe]

I just uploaded a new darkmatter version: http://1drv.ms/242hxbI. It fixes a bug in the ethernet driver for NeXT turbo hardware. This bug was there for more than 20 years now and finally got fixed :-)
An update is highly recommended for all users with turbo hardware as well as people using darkmatter together with Previous.

Thank you

but sorry for the question, how do I install the patch?

[schubige]

These instructions are still valid:

In addition to "darkmatter.jar" you need:

* A recent JRE (Java Runtime Environment). The patch tool runs on Windows, Mac OS or Linux
* A Mac LC ROM image file (not LC II and not LC III, works only with LC ROM); google for "350EACF0 - Mac LC.ROM"
* A daydream 2.11 kernel file; you find it on this site.

What you don't need anymore:

* A daydream ROM box :-)

Invoke the tool with

Code Select Expand

java -jar darkmatter.jar daydream "350EACF0 - Mac LC.ROM"
This will create a folder "darkmatter" which contains the new kernel (size after patch should be 655360 bytes). Enjoy!

But probably someone will provide a patched kernel soon. I'm sorry, but I can't do that for copyright reasons (Mac ROM as well as daydream kernel are copied as part of the patch process). That's the reason for the patch tool.

[Rob Blessin Black Hole]

I just uploaded a new darkmatter version: http://1drv.ms/242hxbI. It fixes a bug in the ethernet driver for NeXT turbo hardware. This bug was there for more than 20 years now and finally got fixed :-)
An update is highly recommended for all users with turbo hardware as well as people using darkmatter together with Previous.

Thank you I'll Check it out !

[mikeboss]

so, does this mean that today mr. grawehr has won the lottery?

http://www.theverge.com/2016/5/18/11683536/google-daydream-virtual-reality-announced-android-n-io-2016

[Rob Blessin Black Hole]

so, does this mean that today mr. grawehr has won the lottery?

http://www.theverge.com/2016/5/18/11683536/google-daydream-virtual-reality-announced-android-n-io-2016

I'm fairly sure if it is a currently trademarked name , he probably will deserve mega compensation. Best Regards Rob Blessin

[Andreas]

These instructions are still valid:

In addition to "darkmatter.jar" you need:

* A recent JRE (Java Runtime Environment). The patch tool runs on Windows, Mac OS or Linux
* A Mac LC ROM image file (not LC II and not LC III, works only with LC ROM); google for "350EACF0 - Mac LC.ROM"
* A daydream 2.11 kernel file; you find it on this site.

What you don't need anymore:

* A daydream ROM box :-)

Invoke the tool with

Code Select Expand

java -jar darkmatter.jar daydream "350EACF0 - Mac LC.ROM"
This will create a folder "darkmatter" which contains the new kernel (size after patch should be 655360 bytes). Enjoy!

But probably someone will provide a patched kernel soon. I'm sorry, but I can't do that for copyright reasons (Mac ROM as well as daydream kernel are copied as part of the patch process). That's the reason for the patch tool.

I get these errors, what i'm doing wrong:

C:\Temp\Darkmatter>java -jar darkmatter.jar daydream "350EACF0 - Mac LC.ROM"
*** darkmatter 0.5
*** daydream kernel 2.11 patcher by Simon Schubiger
*** Credits:
***   Francis Gagné (m68k reasm)
***   Tony Headford (m68k disassembler)
***   Andreas Grabher (Previous support)
***   Michael Bosshard (NeXT Hardware)
*** Optimizing kernel for black NeXT hardware
Reading... daydream
Reading... 350EACF0 - Mac LC.ROM
Decoding...
Applying patches...
MC68000: Loaded 46371 instructions
darkmatter.patch.Decode...
darkmatter.patch.DrawMenuBar...
darkmatter.patch.UnknownDSPCheck...
darkmatter.patch.DSPUpload...
darkmatter.patch.XPRAM...
Pass 1
Pass 1
darkmatter.patch.Init...
Exception in thread "main" java.io.FileNotFoundException: file:\C:\Temp\Darkmatter\darkmatter.jar!\darkmatter\patch\Init.a.asm (Die
Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch)
       at java.io.FileOutputStream.open(Native Method)
       at java.io.FileOutputStream.<init>(Unknown Source)
       at java.io.FileOutputStream.<init>(Unknown Source)
       at java.io.FileWriter.<init>(Unknown Source)
       at darkmatter.Section.writeAsm(Section.java:126)
       at darkmatter.Section.writeAsm(Section.java:117)
       at darkmatter.patch.Init.patch(Init.java:19)
       at darkmatter.Main.main(Main.java:84)

C:\Temp\Darkmatter>

[cuby]

I get these errors, what i'm doing wrong:

C:\Temp\Darkmatter>java -jar darkmatter.jar daydream "350EACF0 - Mac LC.ROM"
[...]
darkmatter.patch.Init...
Exception in thread "main" java.io.FileNotFoundException: file:\C:\Temp\Darkmatter\darkmatter.jar!\darkmatter\patch\Init.a.asm (Die
Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch)
       at java.io.FileOutputStream.open(Native Method)
       at java.io.FileOutputStream.<init>(Unknown Source)
       at java.io.FileOutputStream.<init>(Unknown Source)
       at java.io.FileWriter.<init>(Unknown Source)
       at darkmatter.Section.writeAsm(Section.java:126)
       at darkmatter.Section.writeAsm(Section.java:117)
       at darkmatter.patch.Init.patch(Init.java:19)
       at darkmatter.Main.main(Main.java:84)

I get the same error when running the jar file code on OS X. I suspect there is a problem (sorry, had a peek inside the classfiles with a Java decompiler) with opening the "Init.a.asm" temporary file for output, since Java assumes this should be located inside the jar file.

This workaround runs successfully for me (darkmatter.jar, daydream kernel and the LC.ROM file in the current directory):

Code Select Expand

$ mkdir darkmatter
$ cd darkmatter
$ unzip ../darkmatter.jar
$ java -cp . darkmatter.Main ../daydream ../LC.ROM

This results in a daydream kernel with the following md5 sum (haven't tried running the new kernel yet...):

Code Select Expand

$ md5 ../daydream % Original kernel
MD5 (../daydream) = 2ace94152af70dd909bc803837993ae9
$ md5 darkmatter/daydream % Patched kernel
MD5 (darkmatter/daydream) = 70af8d2951414232edfe3c50775526d9

Hope that helps,
   Michael

[Andreas]

...snip
Hope that helps,
   Michael

OK, works for me also without errors but i get these md5:
3de89b82ed185f02973eb35fb87f517d *daydream

and the kernel is 646.144 bytes, but it should be

Invoke the tool with

Code Select Expand

java -jar darkmatter.jar daydream "350EACF0 - Mac LC.ROM"
This will create a folder "darkmatter" which contains the new kernel (size after patch should be 655360 bytes). Enjoy!

[Andreas]

OK, the kernel boots - success :-)

[Andreas]

Anyway - as before - i don't get network running on a Turbo Cube. it looks like the cable isn't connected to the router, but it is and works in NS3.3. Pinging the own adress works, pinging the router doesn't work. The MAC-adress is the right one. Any hints?

[cuby]

OK, works for me also without errors but i get these md5:
3de89b82ed185f02973eb35fb87f517d *daydream

and the kernel is 646.144 bytes, but it should be

Invoke the tool with

Code Select Expand

java -jar darkmatter.jar daydream "350EACF0 - Mac LC.ROM"
This will create a folder "darkmatter" which contains the new kernel (size after patch should be 655360 bytes). Enjoy!

Maybe I was using a different version of the LC ROM here, that might explain it... good to see that you got it to work!

[Andreas]

Maybe I was using a different version of the LC ROM here, that might explain it... good to see that you got it to work!

i was using exactly "350EACF0 - Mac LC.ROM"

[Andreas]

I just uploaded a new darkmatter version: http://1drv.ms/242hxbI. It fixes a bug in the ethernet driver for NeXT turbo hardware. This bug was there for more than 20 years now and finally got fixed :-)

The bug seems always present. I have put in a harddrive (NS 3.3 and MacOS 8.1 image) in a monoslab and ethernet works fine.
The same hd in a color turbo or a cube turbo doesn't get me ethernet, se other posts

[schubige]

Sorry for the troubles with the darkmatter patcher. Here is an updated version which should work with "java -jar ...":

Code Select Expand

https://1drv.ms/u/s!ALWHYwiFLPiFhLMl

Regarding the Ethernet: I have no idea what it could be.  I've tested it with a turbo cube and I was able to open web pages with Internet Explorer and Netscape Navigator. Anyone else with the same problem? What kind of Ethernet switch do you have between the NeXT and the modem? Could it be that switch's auto-negotiation down to 10MBit/s fails?