Daydream ROM box kit

Started by pentium, September 15, 2008, 05:26:02 PM

Previous topic - Next topic

Andreas

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

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?

Makes no sense, if the switch was the bad one, i had also no network on the NeXTstep side, but on all machines i have network on the NeXTstep side.

i have on the same desktop place tested some spare NeXTs, the same ethernet cable, the same harddrive (same powerplug :-)), same Monitor. Exchanged i have the Soundbox, keyboard, Y-cable from ADB to non-ADB (or to mono) regarding the used NeXT.

I have first tested a NeXT Turbo Color slab, with no ethernet uplink in MacOS, have removed the hard disk and installed it in the NeXT mono nonturbo, booted and Voala, i had an uplink and network after starting the 8.1 harddrive.

The MacPing App shows also the pinging of the router. At now i have configured fixed adresses.

Do you have tested the Turbo with ADB or non-ADB equipment?

schubige

It was non-ADB. Is it possible to check if some packets are sent at all over the Ethernet port (e.g. with Wireshark running on another machine) while daydream runs?

Andreas

Quote from: "schubige"It was non-ADB. Is it possible to check if some packets are sent at all over the Ethernet port (e.g. with Wireshark running on another machine) while daydream runs?

I hadn't yet the time to examine with wireshark, but i think not i will see something.
If NeXTstep boots up, after loading the network driver the LED on the RJ45 socket lights on, on booting darkmatter (or the old daydream) the LED on the RJ45 is dark. So i assume the ethernet chip wasn't enabled properly.

I have tested my equipment also with non-ADB but no working at all

pentium

Before I root through 15 pages of posts, did anyone ever post the completed schematics for the ROM box? Someone gave me all the IC's to build one just before we patched the box out completely but for the hell of it I'd be willing to finish it anyways. I just need the schematics.

-NeXT 68040 Cube with NS 3.3 and 64Mb ram

Andreas

Quote from: "Andreas"
Quote from: "schubige"It was non-ADB. Is it possible to check if some packets are sent at all over the Ethernet port (e.g. with Wireshark running on another machine) while daydream runs?

I hadn't yet the time to examine with wireshark, but i think not i will see something.
If NeXTstep boots up, after loading the network driver the LED on the RJ45 socket lights on, on booting darkmatter (or the old daydream) the LED on the RJ45 is dark. So i assume the ethernet chip wasn't enabled properly.

I have tested my equipment also with non-ADB but no working at all

I have now tested with an 25MHz Cube, and networkig is also working. Maybe there are different ethernet chips in the Turbo line?

Mono-Cube: OK
Mono-Slab: OK
Turbo-Color slab: not working
Turbo-Mono slab: not working
Turbo-Cube: not working
25MHz Color slab but with Turbo-MB: not working

Andreas

Quote from: "Andreas"
Quote from: "Andreas"
Quote from: "schubige"It was non-ADB. Is it possible to check if some packets are sent at all over the Ethernet port (e.g. with Wireshark running on another machine) while daydream runs?

I hadn't yet the time to examine with wireshark, but i think not i will see something.
If NeXTstep boots up, after loading the network driver the LED on the RJ45 socket lights on, on booting darkmatter (or the old daydream) the LED on the RJ45 is dark. So i assume the ethernet chip wasn't enabled properly.

I have tested my equipment also with non-ADB but no working at all

I have now tested with an 25MHz Cube, and networkig is also working. Maybe there are different ethernet chips in the Turbo line?

Mono-Cube: OK
Mono-Slab: OK
Turbo-Color slab: not working
Turbo-Mono slab: not working
Turbo-Cube: not working
25MHz Color slab but with Turbo-MB: not working

Any news on this? I have now a Color Station and network is also working, but not on all the turbo machines. The behavier is so, as it would never an ethernet chip build in, so whireshark doesn't help by a non-exisiting network card.

mietek

This is amazing.  In just a few minutes, I was able to boot into System 7.1, on a virtual NEXTSTEP 3.3 machine, emulated by Previous 1.5, running on my physical macOS 10.12.3 machine.  A sincere thank you to everyone who has made this possible.

Unfortunately, there is a small problem.  I was only able to use the pre-patched daydream kernel, dated 2015-08-01, MD5 checksum cfccff69cd93a51962b43c1bccf4e996, and I would like to use the updated patch, dated 2016-06-16.  I tried following the instructions to patch the 2.11 daydream kernel, but I failed just as Rob Blessin Black Hole did earlier.

The Java patcher does not recognise the 2.11 daydream kernel, MD5 checksum 6fe7a3d67bb7ab1b4123876aa49c5e65, even though I have extracted it from the "update-v2.11.img" disk image included in the "Daydream_docs_n_floppies.tar" archive.  The error message simply says "Not a version 2.11 daydream kernel".

Can someone confirm what is the MD5 checksum of a daydream kernel that the patcher will accept?

Alternatively, can someone send me a pre-patched kernel that includes the latest patch and is optimised for Previous?

mietek

After starting from scratch, I was able to patch the 2.11 daydream kernel successfully.

MD5 (Original 1.41/daydream) = 2eec01fa466094191fb2d3bb8f5d8abb
MD5 (Original 2.11/daydream) = 2ace94152af70dd909bc803837993ae9
MD5 (Patched 2.11 2015-08-01/daydream) = cfccff69cd93a51962b43c1bccf4e996
MD5 (Patched 2.11 2016-06-16/daydream) = 3e6d1c12d11c569b6a8e911d54eb0077

Rob Blessin Black Hole

Quote from: "schubige"These instructions are still valid:

Quote from: "schubige"

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
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.

As soundboxes are in limited supply and an eventual achillies heal for NeXT hardware .....

I had a question(s) would it be possible to be proactive to create a NeXT software "rom" patch
that would create Keyboard and Mice ADB peripheral compatability or better yet USB to legacy NeXT NON ADB systems?  
Are the earlier systems hard coded to be non adb only with no chance of modification or emulated woraround?

I know you have an incredible understanding of NeXT hardware/ software that no one else came close to.... especially the rom patch boot up as a mac

Would it be a ... pcb adb rom dsp dongle like the original Daydream to solve this dilema.  

Ideally an adaptor convertor box that spoofs the NeXT soundbox  or bypasses it that would allow peripherals to directly plug in to a NeXT?

I should ask can one bypass the soundbox and plug peripherals directly into the NeXT using a custom dongle like the drakware or wombat ?

Could serial mouse keyboard drivers be written that would do this using the a/b ports on the NeXT ?

On Turbo systems what chips control determining if it is an adb or non adb set up as it would be interesting to see if  the specific chips could be moved to non adb systems and the rom upgraded lol I know the ram changed as well , I feel like we are slowly being painted into a corner..... but breakthroughs in modern technology keep amazing me and I'm sure it exists in the reality distortion field.
Rob Blessin President computerpowwow ebay  [email protected] http://www.blackholeinc.com
303-741-9998 Serving the NeXT Community  since 2/9/93

gtnicol

Should be possible to plug right into the DB-19 and create a complete keyboard, mouse, sounds, and video adapter. From memory the bus runs at 5MHz and everything is serial except the video.

NeXTnewbe

I'm trying to use the mcos simulation, but I would like to know how do I set a exiting hd in Nextstep to be accessible via daydream

i.e. I have the Mcos 8.1 update file in a folder in my cub and i want to map it to day dream to then be used and allow me the update


any advice will be welcome

thanks

pentium

Part of me feels like trying to run 8.1 on a cube even if Daydream helps to run closer to the hardware will be pretty unusable.

-NeXT 68040 Cube with NS 3.3 and 64Mb ram

Andreas

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

and the kernel is 646.144 bytes, but it should be


OK, Ethernet isn't working for me, but my build have also the false MD5 - had anyone a proper running darkmatter 0.5 or newer binary?

freon

Is anybody able to re-upload the Java patcher? All OneDrive links are dead. Yes, there is a pre-patched kernel in http://www.nextcomputers.org/NeXTfiles/Docs/Hardware/Daydream/, but the patcher itself isn't preserved.

mikeboss

Quote from: freon on March 09, 2023, 04:24:58 PMIs anybody able to re-upload the Java patcher? All OneDrive links are dead. Yes, there is a pre-patched kernel in http://www.nextcomputers.org/NeXTfiles/Docs/Hardware/Daydream/, but the patcher itself isn't preserved.

here you go -> https://mega.nz/file/Q5J2ya7A#0qH_QZ29kYfLo7tk_aNMCigbqDwsl46wWAnnNZZV_Zo
October 12, 1988 Computing Advances To The NeXT Level