BlueSCSI v2 - DaynaPORT WiFi!

PL212

New Tinkerer
Dec 25, 2022
24
12
3
Ah, that's great to hear -- 1.2.2 and 1.2.5 are the versions of the specific SCSI/Link driver from 7.5.3 and 7.7.2 Asanté installers, respectively:

dp122.png
dp125.png


I suppose it's possible that there's something odd on my LC motherboard that's causing the boot crashing when the SCSI/Link is chosen -- again, the BlueSCSI networking just fine *until* a reboot; after which the crash shows up early in the Welcome to Macintosh screen. Clearing PRAM (or booting from a floppy without the SCSI/Link driver, which triggers a "previous network interface unavailable; resetting to LocalTalk" message) causes a clean boot with no other changes -- but obviously no networking either.
 

pwikel

New Tinkerer
Jul 17, 2024
7
0
1
I'm not techy in the least. I'd just like to know why every emulator I've used won't import files, and because of this, makes it impossible to transfer files from either my modern macbook pro or my macintosh classic 2.
Please give me the layman/egghead response. I don't know coding. I just want to transfer files between my macintosh classic 2 and my macbook pro.
 

JDW

Administrator
Staff member
Founder
Sep 2, 2021
1,740
1,490
113
53
Japan
youtube.com
I'm not techy in the least. I'd just like to know why every emulator I've used won't import files, and because of this, makes it impossible to transfer files from either my modern macbook pro or my macintosh classic 2.
Please give me the layman/egghead response. I don't know coding. I just want to transfer files between my macintosh classic 2 and my macbook pro.
The title of this thread is “BlueSCSI v2 - DaynaPORT WiFi!” If by “emulator” you mean Mini vMac or Basilisk II, please consider staring a new thread.

Daynaport WIFI does include topics like transferring files, but it seems you want help with a specific emulator, which isn’t something directly tied to BlueSCSI and WIFI, hence my recommendation for you to start a new thread.

I never like to send people in need empty handed though, so if you want a detailed walkthrough and a curated disk image that made specifically to help people like yourself, check out my latest video here. Even though that video is targeting ROM-inator users, my Mini vMac tutorial and disk image (linked in the video description) should get you up to speed fast. If you need further help, please start a new thread. And when you do that, feel free to tag me so I don’t miss it.

Thanks!
 

naruse

New Tinkerer
Sep 14, 2024
41
23
8
As described in my earlier post, I was successful in getting BSv2 WIFI to work properly with Open Transport running under System 7.1 and higher.

Today, I shall describe my experience getting BSv2 WIFI to work under System 6.0.8 running on a Macintosh Portable which has a 16MHz 68000 processor:
  1. I opened the WiFi DaynaPORT page here. You should too as you follow my guide.

  2. The Macintosh Portable requires Mac Plus code to be in the .ini file, so I added the required WIFI code under that, exactly as follows (and saved to my SD card):
    [SCSI]
    System=MacPlus
    WiFiSSID=MyWiFi
    WiFiPassword=pass123
    # Optional - Each Pico-W will generate its own MAC address, so normally not needed.
    # WiFiMACAddress=00:80:19:C0:FF:EE

  3. I then created a new text file using BBEDIT with Macintosh encoding named (nothing conflicts with SCSI ID 4): NE4.hda

  4. I then downloaded this HDA file to my SD card.

  5. I booted my Portable into System 6.0.8 (with 8MB total RAM) and then opened the drive named "BlueSCSI PicoW" and dragged MacTCP (v2.1) from there to my System Folder.

  6. The instructions then say to: "Install the DaynaPORT 7.5.3 drivers via the provided disk image". That's where trouble began. The instructions go on to say: "use the `MountImage 11b3` cdev (included on the image) to allow the image to be mounted" , but in fact, that was not true in my case. Double-clicking MountImage 11b3 resulted in an error dialog saying the application required cannot be found! Thankfully, I already had MountImage 1.2b2 installed as a Control Panel. Note that when you use it, however, you must checkmark "allow changes to the disk image" or you'll get an error.

  7. With the DaynaPort disk image mounted, I then double-clicked "Installer". Despite what the instructions say though, I cannot do an Easy Install because the "Install" button is dimmed, and it says: "Please install your DayaPORT hardware, or make sure the hardware is installed correctly." Thankfully, you can click the "Customize" button and then click on "DaynaPORT SCSI/Link" (which the instructions tell you to do). I already had AppleTalk 58.0 installed, so I didn't select that. I clicked the "Install" button and I saw it building "System file" which indicated the items were installed inside that file rather than in the System Folder, because I later couldn't find any "Dayna" named files in the System Folder. It then required me to Restart after the install.

  8. The instructions then say to open MacTCP, which I did. I chose "Ethernet Built-In".

  9. Now came the part that was rather confusing because the instructions are incomplete. It indicates you should confirm your Router IP, which I did on my modern Mac by opening System Preferences > Network > Ethernet. It shows my Router to be 192.168.0.1, with DNS set to 8.8.8.8, and Subnet Mask: 255.255.255.0. Now here's where the instructions are lacking. It shows you this pic:

    View attachment 16148
    Fine and well, but it needs to tell the user to do this: "Click into the IP Address field and type a number that matches the leftmost 3 segments of your Router, then type an unused number at right." In other words, in my case: 192.168.0.xxx, where xxx is for me to decide. I chose 73 because that was suggested and not used on my network. In other words: 192.167.0.73

    But yet another failure of the instructions is that they don't specifically say to click the "More..." button, but you need to do that next. I did that and then clicked the "Manually" radio button. The instructions don't specifically say that. You must assume it based on the following pic:

    View attachment 16149

    So after clicking the "Manually" radio button at left in the above, I proceeded to fill out the Routing Information section with my ROUTER info: 255.255.255.0 & 192.168.0.1.

    After that, I didn't know what to do in the Domain Name Server Information section because the instructions make zero mention of what I ought to type into the Domain field. Must I type "local" to match the screenshot? Maybe not because the screenshot is showing an IP of 192.168.1.150 which the text instructions make no mention about! So what I did was type "Google" into the Domain field, and then I typed 8.8.8.8 into the IP Address field, and then I clicked the Default radio button, and lastly, I clicked OK.

    The instructions say I will be asked to Restart, but I wasn't. So I restarted manually.

  10. The instructions said to open MacTCP after Restarting and check that Built-in Ethernet was still selected, and I found it was, so I closed my Control Panels. But the instructions seem to be in error, because it says "proceed to Step 5," which cannot be right.

  11. I then proceeded to the next instruction which is oddly marked "1." and says: "Now open 'MacTCP Ping' and try to ping 1.1.1.1." I did that. Success!

  12. Because web browsers won't run under System 6, the best we can do is run Fetch (sorry, Panic's Transit or Transmit won't run under System 6 either). I used the following as a test, which worked perfectly:
    repo1.macintoshgarden.org
    user: macgarden
    psw: publicdl
    Directory (leave blank)
And there you have it. I hope the above is helpful to those who haven't yet been able to get BSv2 WIFI to work under System 6!

UPDATE: I left my Mac Portable as I typed the above, which took me more than the 2 minute sleep timer. I went back and found it asleep. I pressed a key which work the machine, showing Fetch still logged into Macintosh Garden. But it was frozen. Moving the trackball did not move the arrow pointer, and even pressing Interrupt did nothing. Pressing Restart worked, however. At the desktop, I took note that the ACT LED on BSv2 was not flashing (which is normal, I think, because I didn't yet open Fetch. I put the machine to Sleep. I then woke the machine. No freeze. I then launched Fetch which causes the ACT LED on BSv2 to start flashing. I then quit Fetch, but the ACT LED keeps flashing. At the desktop, I put the machine to sleep. Upon wake, it froze. So the flashing LED seems to trigger the freeze on wake from Sleep.
@JDW you cannot imagine how helpful this post has been for me!

For the past few days I have been struggling to get BlueSCSI dynaport working with MacTCP on system 6.0.8 on my Mac SE and I have done the same exact process several times but I discovered that if I install the appletalk v58 drivers then when I go ahead and try to use "MacTCP Ping" it kept telling me that the drivers couldnt be located.

Anyways long story short. In my case (and if people is struggling getting dynaport working with bluescsi on 6.0.8) DO NOT install the v58 apple talk drivers, JUST install the SCSI/Link drivers and that should work!

Also, as a side note; this is a fresh install of System 6.0.8 from the legacy recovery CD and if I installed (again on my Mac SE) the v58 apple talk with Dynaport, I would get a crash error every time; to avoid this. it forced me to not only install the Appletalk v58, SCSI/Link drivers but also the SCSI SE one.

Regardless, in my Case Just installing the SCSI/Link (and NO appletalk v58) drivers get me going on 6.0.8 :)
 

eric

Administrator
Staff member
Sep 2, 2021
1,015
1,671
113
MN
bluescsi.com
@jcs has released version 1.3 of the BlueSCSI Wi-Fi Desk Accessory. This includes work by @OneGeekArmy and others to inlcude translations in the app!


Changes in this version:
  • Fix a handful of bugs
  • Add a log window that can be toggled by clicking on the signal icon
  • Add localization for strings shown in the UI for Macs running non-English installations, which was initiated by Jean-Michel Durand
  • Add Dutch translation by Axel Roest
  • Add French translation by Jean-Michel-Durand (onegeekarmy)
  • Add Italian translation by qwertyoruiop
 

wottle

Active Tinkerer
Oct 30, 2021
645
387
63
47
Fort Mill, SC
I think this is a pretty petty feature request, but I'll put it out there and maybe there's other options people can suggest. I use Basilisk II primarily to load software onto my images. It works fantastically, allowing me to install the version of the OS I want plus almost any software I need (can't install the Dynaport software in the emulator because the software checks that the hardware is installed). But the pain in this solution is that Basilisk II on the Mac won't allow you to mount .hda files. So every time I want to add something to an image, I have to rename it.

Is there any way to allow BlueSCSI to accept hard drive images with the .img extension? Is there a better solution I haven't thought of? I tried aliases. I tried symlinks. The only solution I've found has been to rename the file to add the .img extension, then hope I remember to remove the extension after I am done in Basilisk. I don't know what other implications it might have from a support perspective (are there other .img files that aren't hard drive images that people may get confused thinking they might be supported? Floppy disk images?). Anyway, maybe I'm the only one frustrated by this, or maybe there are other solutions, but I figured I'd bring it up since I'm going through it right now trying to load up software for a bunch of machines.

Thanks for considering! Also, just assembled a batch of 10 v2 desktops - assembly and flashing is so much easier than the old version. Really appreciate all the work y'all are doing on this!
 

eric

Administrator
Staff member
Sep 2, 2021
1,015
1,671
113
MN
bluescsi.com
Is there any way to allow BlueSCSI to accept hard drive images with the .img extension?
Have you tried not renaming it... you might be surprised! BlueSCSI v2 has never considered file extensions for anything and we removed the requirement for .hda in v1 back in 2021.

So wish granted :)

(Also BII will allow you to mount .hda files - for some reason whomever built the Basilisk II GUI app put a restriction on it that should probably just be removed.)
 

wottle

Active Tinkerer
Oct 30, 2021
645
387
63
47
Fort Mill, SC
Have you tried not renaming it... you might be surprised! BlueSCSI v2 has never considered file extensions for anything and we removed the requirement for .hda in v1 back in 2021.

So wish granted :)

(Also BII will allow you to mount .hda files - for some reason whomever built the Basilisk II GUI app put a restriction on it that should probably just be removed.)
Oh, man, clearly haven't tried that. Thanks for completing my feature request 4 years ahead of time! I'm a little frustrated that I never gave that a try. Better late than never finding it out, though!
 
  • Like
Reactions: JDW

djc6

New Tinkerer
Oct 19, 2024
19
6
3
Anyone know if a DaynaPORT SCSI/Link driver exists for A/UX? I'm curious to try A/UX on my SE/30, already have BlueSCSI v2 installed.
 

vtgearhead

New Tinkerer
May 1, 2023
15
8
3
Burlington, VT USA
Quick question for folks running Mac OS 7.3.x Appletalk clients over the DaynaPORT SCSI link: Are you able to get remote volumes to remount automatically after restart? I have the appropriate boxes checked in the Chooser, but the volumes do not appear until I reconnect manually. Every time. Is it possible that the SCSI link driver is not initialized at the point where the Appletalk client starts at boot time? Any way to troubleshoot this further?
 

eric

Administrator
Staff member
Sep 2, 2021
1,015
1,671
113
MN
bluescsi.com
Quick question for folks running Mac OS 7.3.x Appletalk clients over the DaynaPORT SCSI link: Are you able to get remote volumes to remount automatically after restart? I have the appropriate boxes checked in the Chooser, but the volumes do not appear until I reconnect manually. Every time. Is it possible that the SCSI link driver is not initialized at the point where the Appletalk client starts at boot time? Any way to troubleshoot this further?
It will be hard to diagnose the true cause of this but I would suspect it's a timing issue with when MacTCP loads (only on request) and when Appletalk is loaded - though it would take some serious knowledge to debug this.

An easy work around would be to make an alias to your share on the desktop and once fully booted double click it - sure not as "streamlined" but would work.
 

vtgearhead

New Tinkerer
May 1, 2023
15
8
3
Burlington, VT USA
I'm using OpenTransport, not MacTCP. The alias approach has been suggested by a number of folks across various fora, but it did not work. I just receive a complaint that the underlying volume is not available. Worse, something that I did in the course of troubleshooting has broken DaynaPORT networking completely... Still trying to backtrack from that.
 

vtgearhead

New Tinkerer
May 1, 2023
15
8
3
Burlington, VT USA
Turns out that the afpd daemon crashed on the server, so networking is restored. However, the alias approach continues to not work. Referencing the alias triggers a login dialog, but after entering credentials (which I should not have to do, since the share was checked as persistent in chooser) it fails with a complaint that the linked volume is not found. Whatever the Appletalk client normally does during system boot is simply not happening with DaynaPORT networking. I have not yet seen anyone report that this works for them, so perhaps it never did and I'm the only person who feels automatic remount to be important? It's more of an annoyance than a showstopper and I can learn to live with it. Thanks for the suggestion!
 

eric

Administrator
Staff member
Sep 2, 2021
1,015
1,671
113
MN
bluescsi.com
Digging into these drivers they seem to be for A/UX 2.0 and only for the EtherPort IIN PDS card.

```
1.2 (Novell) 2/1/90
# Install the EtherPort IIN driver (National Version)
```

The disk image is a bit odd as you can not run the DiskMaker program on A/UX - I ran it on System 7 on my PowerBook to make the images.

If you try to mount the floppy in MacOS or A/UX 3 it will say it's unreadable. It is also a boot disk. The strings seem to indicate it should be booted off of then installed and rebuild the kernel. There is not much beyond a few comments in the scripts.

So while this is indeed a nice find, it wont help for BlueSCSI DaynaPORT - but if you're on A/UX 2.x with a EtherPort card - then it's great for you :)

Also both files seem to contain the exact same contents.
 
  • Sad
Reactions: wottle