I'm having hard time installing a fresh copy of NeXTStep 3.3 onto a SCSI2SD card. My equipment:
Turbo Mono 64MB RAM, SCSI2SD 5.0c, AppleCD 300 Plus, proper XML file loaded into SCSI2SD
- Using a burned image I downloaded with User and Dev 3.3, and single 2GB drive emulation, works perfectly fine. CD-ROM works as well - was able to burn the User Patch 3 and Dev Patch 2 onto a CD-R and install on the NeXT.
Now here is the problem. The same basic configuration as above - 2GB drive set up in SCSI2SD but different card (tried multiple just in case), set to ID 0. AppleCD set to ID 3.
When I go into ROM Monitor and do bsd(3,0,0), I get exception 0xC errors.
It does that no matter what ID I put in.
Now, if I just let it try booting to SCSI Error, I can then go to the ROM Monitor, and attempt bsd(3,0,0). It says boot(3,0,0), then after a while SCSI error.
Any ideas what it could be?
Hi polbit,
is the only difference, that you try to install onto other SD cards? First card went fine and you could NeXTstep, all others do not work, you can not boot / install?
I am wondering that you do not need boot floppy and start install process with "bfd".
Cheers, Nuss
Quote from: nuss on March 04, 2022, 02:36:55 PMHi polbit,
is the only difference, that you try to install onto other SD cards? First card went fine and you could NeXTstep, all others do not work, you can not boot / install?
I am wondering that you do not need boot floppy and start install process with "bfd".
Cheers, Nuss
No, the only difference is that I can load the image onto the SD card with win32DiskImager and it works great. But when I try a blank card and doing install from CDs, that's the error I get.
It's a Turbo so it does not need a floppy, and it can actually boot from the CD by itself... I suppose I could try the floppy anyway, since I just got a NOS from Rob to replace my non-working one!
Thanks for clarifying. I have no experience with SCSI2SD yet, but with several tricky installations on real hard drives.
It might help analyzing if you would send screenshot of booting process from bsd(3,0,0) into the error messages.
Aha I think I see what it may be try setting the cdrom drive to scsi ID 6 and terminated,
sometimes it makes a difference , with NeXTSTEP User disk in try this command to get her started bsd(6,0,0)sdmach rootdev=sd6a and a video on my you tube page
NeXTstep 3.3 Install made easy NeXT Cube NeXTstation for Max part 1
https://www.youtube.com/watch?v=-Xt-PdJN8_8
Well, here's my set up:
Apple 300Plus CD-ROM, active termination, SCSI ID 6
SCSI2SD V5.2, loaded with xml from the archive with ISOs and the 2Gb image I'm successfully using
When I put a new SDcard in (Sandisk 32Gb Extreme Pro), load 3.3 User into CD, and go to Monitor, and type:
bsd(6,0,0)sdmatch rootdev=sd6a
It crashes out basically. I have to unplug it as it no longer responds to power button, only shows the prompt as below:
Exception #3 (0xc) at pc 0x1000646 sp 0xc03ee6c
NeXT>
When pressing power button it says:
really power down? g
and back to prompt
Hi polbit,
have checked for the error in my (Usenet) archives and found one answer from 1997 to the "Exception #3" boot error:
Quote1) Is a cdrom-drive with NeXTstep-CD plugged to the slab?
2) Is it terminated?
3) Does it have a unique number?
4) Do you have got some SIMMs in your slab?
If you can answer all of the above with YES:
For us the message always was caused by SIMMs. The order of parity and
non-parity SIMMs (for example) is important. Also sometimes a SIMM is
damaged. I saw a similar exception during a harddisk-crash, too, but I think
this has been exception #2.
Additionally I only found one older thread in this forum (even around SCSI2SD booting). Starting with this post it looks similar to your case:
http://www.nextcomputers.org/forums/index.php?msg=25673Conclusion was about non-functional RAM, too!
POST Power-on Self Test Error Codes mentioned in the Thread:
http://www.asterontech.com/Asterontech/NeXT_POST_Codes.htmlExperienced similar issues often in the 1990s, but not sure if those (back then well known) SIMM issues have also effected Turbo slabs.
Cheers, Nuss
Wow Nuss, thanks for looking into this!
It would seem that it has to be the SIMM but for one issue - it works just fine booting from a SCSI HD drive, or SD card with a proper image on it, or even a CD by itself.
I need to find a memory tester program I think. Also need to try a different SD card - I bought a bunch of the 32Gb SD cards, maybe it's something with them too.
In the meantime, I ordered some new memory, it will either upgrade to 128Mb or replace what's in there now!
And I have to amend my earlier statement about only bsd(6,0,0) not working.
After going into ROM Monitor right after boot, I am unable to execute ANY bsd command. Whether I try the SD card or the CD-ROM, I get the same error, although once I saw Exception #2, which is Access fault.
It nonetheless boots perfectly from an SD card prepared on the PC...
Hello : Do you have new capacitors on the mother board?
What type of Ram do you have? In Sets of 2?
What are the system parameters set to
http://www.nextcomputers.org/NeXTfiles/Docs/NeXTStep/3.3/nsa/09_StartShut.htmld/index.html XML File is configured for a 2Gb partition? Cylinders and parameter settings in XML File
?
Hi Rob,
Quote from: Rob Blessin Black Hole on March 08, 2022, 09:02:43 PMHello : Do you have new capacitors on the mother board?
No new capacitors.
What type of Ram do you have? In Sets of 2?
It's 32MBx2 60ns EDO, same brand for both.
What are the system parameters set to
It is set to boot from disk, and no memory test. It does complete the built-in test though. Fresh battery btw.
XML File is configured for a 2Gb partition? Cylinders and parameter settings in XML File?
The working image is from:
https://winworldpc.com/download/0c6a74c3-8e53-3f11-c3a4-c2a90f7054ef (https://winworldpc.com/download/0c6a74c3-8e53-3f11-c3a4-c2a90f7054ef)
XML file details:
<enableScsi2>true</enableScsi2>
<disableGlitchFilter>false</disableGlitchFilter>
<enableCache>false</enableCache>
<enableDisconnect>false</enableDisconnect>
<selLatch>false</selLatch>
<SCSITarget id="3">
<deviceType>0x0</deviceType>
<sdSectorStart>0</sdSectorStart>
<scsiSectors>4194303</scsiSectors>
<bytesPerSector>512</bytesPerSector>
<sectorsPerTrack>139</sectorsPerTrack>
<headsPerCylinder>4</headsPerCylinder>
I have now been using this machine extensively for about a month, both with original HD with 4.2 as well as SCSI2SD with the above-mentioned 3.3 image. I've installed patches and software from CDs and floppies, and used a lot of software, having the machine run for hours. Not a single issue...
Just saw this and realized bsd(6,0,0)sdmatch rootdev=sd6a
should be bsd(6,0,0)sdmach rootdev=sd6a not sdmatch sdmach