Re: SCSI2SD in a DEC 3000/300 - T-ERR-SCSI A
On 9/26/21 4:04 PM, Alexander Jacocks via cctalk wrote: On Sep 26, 2021, at 10:03 AM, Bill Degnan via cctalk wrote: I was either sacrifice a data drive to make it a backup of the primary or find a like drive first, get the system stable and then upgrade. I have a 3000 too here if you want to work together to troubleshoot yours Bill On Sun, Sep 26, 2021, 9:46 AM Zane Healy via cctalk wrote: On Sep 26, 2021, at 12:22 AM, Alexander Jacocks via cctalk < cctalk@classiccmp.org> wrote: I’ve got a DEC 3000/300 system that has some SCSI drives with aging bearings installed. I’d like to be able to start to migrate some of my systems, like this, to flash media, of some kind, as even my large repository of SCSI disks is starting to dry up. Here is my SRM level info: DEC 3000 - M300 Digital Equipment Corporation VPP PAL V5.56-80800101/OSF PAL V1.45-80800201 - Built on 30-SEP-1996 09:18:31.84 As far as I have read, the SCSI2SD v6 2020 should be compatible with several varieties of DEC hardware, from the VAXen to the Alphas. However, I can’t seem to get anywhere useful with mine. I have the virtual disks configured as follows: sh dev BOOTDEV ADDR DEVTYPENUMBYTES RM/FXWPDEVNAM REV --- --- ----- --- ESA0 08-00-2B-3F-4C-9A , TENBT DKA100 A/1/0 DISK 9.54GB FXRZ40 6.0 DKA300 A/3/0 DISK 9.54GB FXRZ40 6.0 DKA400 A/4/0 RODISK 305.01MB RM WPRRD45 6.0 All three disks are from the SCSI2SD. I have attempted to make the inquiry strings match the originals, as closely as possible. In the SCSI2SD utility, I have the following config: General page: all defaults, termination off (I have tried parity, scsi2 mode, and setting SCSI speed to sync, with no improvement) Device 1: enabled, ID 1, device Hard Drive, start sector 0, sector size 512, sector count 18636800, vendor “DEC ", product “RZ40 “, revision “ 6.0”, serial number Device 2: enabled, ID 3, device Hard Drive, start sector 18636800, sector size 512, sector count 18636800, vendor “DEC ", product “RZ40 “, revision “ 6.0”, serial number Device 3: enabled, ID 4, device CDROM, start sector 37273600, sector size 2048, sector count 148933, vendor “DEC ", product “RRD45“, revision “ 6.0”, serial number I’ve also tried booting from a virtual CDROM, only, with no luck there, either. In all cases, I get the following from SRM: test scsi T-STS-SCSI A - Data Trans test ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare T-ERR-SCSI A - id = 1 lun = 0 ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare T-ERR-SCSI A - id = 3 lun = 0 ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare T-ERR-SCSI A - id = 4 lun = 0 ?? 002 SCSI 0x0008 84 FAIL Does anyone have an idea what might be causing this? Has anyone tried a v6 SCSI2SD in a DEC 3000? Thanks! - Alex I picked up a couple v6 boards for my AlphaStation 200 4/233, but haven’t tried to use them yet. Are you using the onboard SCSI, or a SCSI board? I’m ‘going to assume you’ve tried a different cable, and to get it working from actual physical drives? Have you tried turning the termination on, on the board? Is your SCSI Bus Terminated? You actually have RZ40’s in the system? I’m asking as I’m not actually familiar with that drive type, at least it’s not one I remember off the top fo my head. I usually use RZ29’s. On my v5.2 board on my VAXstation 4000/90 I think I went with basic 8GB drives, without a vendor string or product string. I have a Quantum XP2160 and a Seagate 1050 in my 3000. Both function, but have significant bearing whine, and I have no idea how many hours are on each. So, I know my scsi subsystem and termination are fine. I’m going to pull a scsi2sd v5.2 from a Quadra 700 and try that, to see if I get the same errors. I used the RZ40 as the inquiry string, and matched the sector count, to make SRM happy. I have real RZ25s and RZ26es, but they are quite small. Most of my modern scsi disks are 10 and 15k U320s, and not a good choice for heat constrained enclosures like the 3000. Not to mention that 300gb is just silly for Digital UNIX. - Alex Difference in length of data sent or expected for SCSI-1 vs SCSI-2 inq commands? Jerry
Re: An American perspective on the late great Sir Clive Sinclair, from Fast Company
My girlfriend commented to me that Americans don't understand London"s Fleet Street scene of the 70's and early 80s and how Sinclair products were represented there. In the US the "Timex Sinclair TS-1000" was a budget $99 computer for sale in Hallmark gift stores and its marketing represented little of the fleet Street cache. Bill Bill On Sun, Sep 26, 2021, 10:05 AM Liam Proven via cctalk wrote: > I found this interesting for perspective. The British media (and > AFAICS of Australia, New Zealand and several bits of Europe) have been > saturated with coverage of a much-loved, widely-celebrated and revered > hero of tech. > > As FC points out, even the American _tech_ media barely noticed. > > « > The prescient, quirky legacy of U.K. gadget inventor Clive Sinclair > Little known in the U.S., Sinclair democratized computing with his > dirt-cheap 1980s PCs. Even his many failures were decades ahead of > their time. > » > https://www.fastcompany.com/90680349/clive-sinclair-obituary > > -- > Liam Proven – Profile: https://about.me/liamproven > Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com > Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven > UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053 >
Re: SCSI2SD in a DEC 3000/300 - T-ERR-SCSI A
> On Sep 26, 2021, at 10:03 AM, Bill Degnan via cctalk > wrote: > > I was either sacrifice a data drive to make it a backup of the primary or > find a like drive first, get the system stable and then upgrade. I have a > 3000 too here if you want to work together to troubleshoot yours > > Bill > >> On Sun, Sep 26, 2021, 9:46 AM Zane Healy via cctalk >> wrote: >> >>> On Sep 26, 2021, at 12:22 AM, Alexander Jacocks via cctalk < >>> cctalk@classiccmp.org> wrote: >>> >>> I’ve got a DEC 3000/300 system that has some SCSI drives with aging >> bearings installed. I’d like to be able to start to migrate some of my >> systems, like this, to flash media, of some kind, as even my large >> repository of SCSI disks is starting to dry up. >>> >>> Here is my SRM level info: >>> DEC 3000 - M300 >>> Digital Equipment Corporation >>>VPP PAL V5.56-80800101/OSF PAL V1.45-80800201 - Built on 30-SEP-1996 >> 09:18:31.84 >>> >>> As far as I have read, the SCSI2SD v6 2020 should be compatible with >> several varieties of DEC hardware, from the VAXen to the Alphas. However, I >> can’t seem to get anywhere useful with mine. I have the virtual disks >> configured as follows: >>> >> sh dev >>> >>> BOOTDEV ADDR DEVTYPENUMBYTES RM/FXWPDEVNAM >> REV >>> --- --- ----- >> --- >>> ESA0 08-00-2B-3F-4C-9A , TENBT >>> DKA100 A/1/0 DISK 9.54GB FXRZ40 >> 6.0 >>> DKA300 A/3/0 DISK 9.54GB FXRZ40 >> 6.0 >>> DKA400 A/4/0 RODISK 305.01MB RM WPRRD45 >>6.0 >>> >>> All three disks are from the SCSI2SD. I have attempted to make the >> inquiry strings match the originals, as closely as possible. In the SCSI2SD >> utility, I have the following config: >>> >>> General page: all defaults, termination off (I have tried parity, scsi2 >> mode, and setting SCSI speed to sync, with no improvement) >>> Device 1: enabled, ID 1, device Hard Drive, start sector 0, sector size >> 512, sector count 18636800, vendor “DEC ", product “RZ40 “, >> revision “ 6.0”, serial number >>> Device 2: enabled, ID 3, device Hard Drive, start sector 18636800, >> sector size 512, sector count 18636800, vendor “DEC ", product “RZ40 >> “, revision “ 6.0”, serial number >>> Device 3: enabled, ID 4, device CDROM, start sector 37273600, sector >> size 2048, sector count 148933, vendor “DEC ", product “RRD45“, >> revision “ 6.0”, serial number >>> >>> I’ve also tried booting from a virtual CDROM, only, with no luck there, >> either. In all cases, I get the following from SRM: >>> >> test scsi >>> T-STS-SCSI A - Data Trans test >>> ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare >>> T-ERR-SCSI A - id = 1 lun = 0 >>> >>> ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare >>> T-ERR-SCSI A - id = 3 lun = 0 >>> >>> ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare >>> T-ERR-SCSI A - id = 4 lun = 0 >>> ?? 002 SCSI 0x0008 >>> >>> >>> 84 FAIL >>> >>> Does anyone have an idea what might be causing this? Has anyone tried a >> v6 SCSI2SD in a DEC 3000? >>> >>> Thanks! >>> - Alex >> >> I picked up a couple v6 boards for my AlphaStation 200 4/233, but haven’t >> tried to use them yet. >> >> Are you using the onboard SCSI, or a SCSI board? I’m ‘going to assume >> you’ve tried a different cable, and to get it working from actual physical >> drives? Have you tried turning the termination on, on the board? Is your >> SCSI Bus Terminated? >> >> You actually have RZ40’s in the system? I’m asking as I’m not actually >> familiar with that drive type, at least it’s not one I remember off the top >> fo my head. I usually use RZ29’s. On my v5.2 board on my VAXstation >> 4000/90 I think I went with basic 8GB drives, without a vendor string or >> product string. I have a Quantum XP2160 and a Seagate 1050 in my 3000. Both function, but have significant bearing whine, and I have no idea how many hours are on each. So, I know my scsi subsystem and termination are fine. I’m going to pull a scsi2sd v5.2 from a Quadra 700 and try that, to see if I get the same errors. I used the RZ40 as the inquiry string, and matched the sector count, to make SRM happy. I have real RZ25s and RZ26es, but they are quite small. Most of my modern scsi disks are 10 and 15k U320s, and not a good choice for heat constrained enclosures like the 3000. Not to mention that 300gb is just silly for Digital UNIX. - Alex
Re: HP-UX on HP 9000/217
5.1 installation diskettes from bitsavers and hpmuseum are labeled "series 300", we should try to locate the correct release (I also have 217 without software). Regards, Plamen On Tue, Sep 21, 2021 at 8:06 PM Larkin Nickle via cctalk < cctalk@classiccmp.org> wrote: > Hey all, > > According to > > http://bitsavers.trailing-edge.com/pdf/hp/9000_200/9000-200_periphSupp_Dec89.pdf > (see PDF page 2), it seems as if HP-UX 5.1 should work on the 9000/217. > http://hparchive.com/Catalogs/HP-Catalog-1986.pdf also seems to confirm > this (PDF page 71 under Series 200 Bundled Systems, it's mentioned that > the Model 217 can run single-user HP-UX). However, there seems to be > conflicted information based on people that I've talked to and the > hpmuseum page with a copy of HP-UX 5.1 whether it should work at all, > whether 5.1 is a unified release where the boot floppy should work on > both series 200 and 300, or whether there's another boot floppy for > series 200 which apparently has not been archived. > > I recently obtained a Model 217 and would like to know if anyone > has > more info on this, the two people that I know of that have tried it get > a hang on boot. > > Thanks, > Larkin >
Re: Burnable, patched Microvax-2000 SCSI-boot EPROM images?
I just purchased an RK05 Controller for my PDP-8/E, does this emulator work to emulate RK05 packs? If it does then maybe I can use it as mass storage until i can find an RK05 (or Plessey or Diablo clones) . Thanks... On 9/24/2021 3:19 PM, David Gesswein via cctalk wrote: On Tue, Sep 21, 2021 at 12:15:12PM -0400, Paul Koning wrote: On Sep 21, 2021, at 12:00 PM, Jonathan Stone via cctalk wrote: The RD53s in both Microvax 2000s are dead. I'm reluctant to buy more 30+ year old rotating media. If I'm going to buy a disk emulator, I'd much prefer SCSI to MFM, for the obvious performance reasons. Emulators presumably act, performance wise, like SSDs. Given that, an MFM emulator will significantly outperform a SCSI hard drive since it has no seek delays. David Gesswein's MFM emulator works impressively well and is inexpensive, too. The MFM emulator can't transfer data faster than the 5 Mbit/second, 625k Byte/sec of the ST-506 standard. Seek time isn't zero due to overhead in moving the data in the Beaglebone to where the PRU processors can access it. Think its around 0.6ms/head. An entire cylinder is transfered on each seek. Additional time if cylinder was written to. Each track written needs to be moved also. Most ST-506 drives are slower. I'm faster than average seek for RD54 but it wins for single track seek at 4ms with 15 heads.
Re: Burnable, patched Microvax-2000 SCSI-boot EPROM images?
On Tue, Sep 21, 2021 at 12:15:12PM -0400, Paul Koning wrote: > > On Sep 21, 2021, at 12:00 PM, Jonathan Stone via cctalk > > wrote: > > > > The RD53s in both Microvax 2000s are dead. I'm reluctant to buy more 30+ > > year old rotating media. > > If I'm going to buy a disk emulator, I'd much prefer SCSI to MFM, for the > > obvious performance reasons. > > Emulators presumably act, performance wise, like SSDs. Given that, an MFM > emulator will significantly outperform a SCSI hard drive since it has no seek > delays. > > David Gesswein's MFM emulator works impressively well and is inexpensive, too. > The MFM emulator can't transfer data faster than the 5 Mbit/second, 625k Byte/sec of the ST-506 standard. Seek time isn't zero due to overhead in moving the data in the Beaglebone to where the PRU processors can access it. Think its around 0.6ms/head. An entire cylinder is transfered on each seek. Additional time if cylinder was written to. Each track written needs to be moved also. Most ST-506 drives are slower. I'm faster than average seek for RD54 but it wins for single track seek at 4ms with 15 heads.
Re: OpenVMS/VAX license expiration
On Sun, 26 Sep 2021, geneb via cctalk wrote: On Sat, 25 Sep 2021, Adam Thornton via cctalk wrote: I REALLY hate how the list munges email addresses. That was intended to be a private reply. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://scarlet.deltasoft.com - Get it _today_!
Re: OpenVMS/VAX license expiration
On Sat, 25 Sep 2021, Adam Thornton via cctalk wrote: You might want to search the Github repositories of a certain "athornton" looking for something called "yarr". I'm not finding anything. Help! :D Obviously it would be wrong to use it. So don't. Oh absolutely. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://scarlet.deltasoft.com - Get it _today_!
An American perspective on the late great Sir Clive Sinclair, from Fast Company
I found this interesting for perspective. The British media (and AFAICS of Australia, New Zealand and several bits of Europe) have been saturated with coverage of a much-loved, widely-celebrated and revered hero of tech. As FC points out, even the American _tech_ media barely noticed. « The prescient, quirky legacy of U.K. gadget inventor Clive Sinclair Little known in the U.S., Sinclair democratized computing with his dirt-cheap 1980s PCs. Even his many failures were decades ahead of their time. » https://www.fastcompany.com/90680349/clive-sinclair-obituary -- Liam Proven – Profile: https://about.me/liamproven Email: lpro...@cix.co.uk – gMail/gTalk/gHangouts: lpro...@gmail.com Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053
Re: SCSI2SD in a DEC 3000/300 - T-ERR-SCSI A
I was either sacrifice a data drive to make it a backup of the primary or find a like drive first, get the system stable and then upgrade. I have a 3000 too here if you want to work together to troubleshoot yours Bill On Sun, Sep 26, 2021, 9:46 AM Zane Healy via cctalk wrote: > On Sep 26, 2021, at 12:22 AM, Alexander Jacocks via cctalk < > cctalk@classiccmp.org> wrote: > > > > I’ve got a DEC 3000/300 system that has some SCSI drives with aging > bearings installed. I’d like to be able to start to migrate some of my > systems, like this, to flash media, of some kind, as even my large > repository of SCSI disks is starting to dry up. > > > > Here is my SRM level info: > >DEC 3000 - M300 > > Digital Equipment Corporation > > VPP PAL V5.56-80800101/OSF PAL V1.45-80800201 - Built on 30-SEP-1996 > 09:18:31.84 > > > > As far as I have read, the SCSI2SD v6 2020 should be compatible with > several varieties of DEC hardware, from the VAXen to the Alphas. However, I > can’t seem to get anywhere useful with mine. I have the virtual disks > configured as follows: > > > sh dev > > > > BOOTDEV ADDR DEVTYPENUMBYTES RM/FXWPDEVNAM > REV > > --- --- ----- > --- > > ESA0 08-00-2B-3F-4C-9A , TENBT > > DKA100 A/1/0 DISK 9.54GB FXRZ40 >6.0 > > DKA300 A/3/0 DISK 9.54GB FXRZ40 >6.0 > > DKA400 A/4/0 RODISK 305.01MB RM WPRRD45 > 6.0 > > > > All three disks are from the SCSI2SD. I have attempted to make the > inquiry strings match the originals, as closely as possible. In the SCSI2SD > utility, I have the following config: > > > > General page: all defaults, termination off (I have tried parity, scsi2 > mode, and setting SCSI speed to sync, with no improvement) > > Device 1: enabled, ID 1, device Hard Drive, start sector 0, sector size > 512, sector count 18636800, vendor “DEC ", product “RZ40 “, > revision “ 6.0”, serial number > > Device 2: enabled, ID 3, device Hard Drive, start sector 18636800, > sector size 512, sector count 18636800, vendor “DEC ", product “RZ40 > “, revision “ 6.0”, serial number > > Device 3: enabled, ID 4, device CDROM, start sector 37273600, sector > size 2048, sector count 148933, vendor “DEC ", product “RRD45“, > revision “ 6.0”, serial number > > > > I’ve also tried booting from a virtual CDROM, only, with no luck there, > either. In all cases, I get the following from SRM: > > > test scsi > > T-STS-SCSI A - Data Trans test > > ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare > > T-ERR-SCSI A - id = 1 lun = 0 > > > > ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare > > T-ERR-SCSI A - id = 3 lun = 0 > > > > ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare > > T-ERR-SCSI A - id = 4 lun = 0 > > ?? 002 SCSI 0x0008 > > > > > > 84 FAIL > > > > Does anyone have an idea what might be causing this? Has anyone tried a > v6 SCSI2SD in a DEC 3000? > > > > Thanks! > > - Alex > > I picked up a couple v6 boards for my AlphaStation 200 4/233, but haven’t > tried to use them yet. > > Are you using the onboard SCSI, or a SCSI board? I’m ‘going to assume > you’ve tried a different cable, and to get it working from actual physical > drives? Have you tried turning the termination on, on the board? Is your > SCSI Bus Terminated? > > You actually have RZ40’s in the system? I’m asking as I’m not actually > familiar with that drive type, at least it’s not one I remember off the top > fo my head. I usually use RZ29’s. On my v5.2 board on my VAXstation > 4000/90 I think I went with basic 8GB drives, without a vendor string or > product string. > > >
Re: SCSI2SD in a DEC 3000/300 - T-ERR-SCSI A
On Sep 26, 2021, at 12:22 AM, Alexander Jacocks via cctalk wrote: > > I’ve got a DEC 3000/300 system that has some SCSI drives with aging bearings > installed. I’d like to be able to start to migrate some of my systems, like > this, to flash media, of some kind, as even my large repository of SCSI disks > is starting to dry up. > > Here is my SRM level info: >DEC 3000 - M300 > Digital Equipment Corporation > VPP PAL V5.56-80800101/OSF PAL V1.45-80800201 - Built on 30-SEP-1996 > 09:18:31.84 > > As far as I have read, the SCSI2SD v6 2020 should be compatible with several > varieties of DEC hardware, from the VAXen to the Alphas. However, I can’t > seem to get anywhere useful with mine. I have the virtual disks configured as > follows: > sh dev > > BOOTDEV ADDR DEVTYPENUMBYTES RM/FXWPDEVNAM REV > --- --- ----- --- > ESA0 08-00-2B-3F-4C-9A , TENBT > DKA100 A/1/0 DISK 9.54GB FXRZ40 > 6.0 > DKA300 A/3/0 DISK 9.54GB FXRZ40 > 6.0 > DKA400 A/4/0 RODISK 305.01MB RM WPRRD45 > 6.0 > > All three disks are from the SCSI2SD. I have attempted to make the inquiry > strings match the originals, as closely as possible. In the SCSI2SD utility, > I have the following config: > > General page: all defaults, termination off (I have tried parity, scsi2 mode, > and setting SCSI speed to sync, with no improvement) > Device 1: enabled, ID 1, device Hard Drive, start sector 0, sector size 512, > sector count 18636800, vendor “DEC ", product “RZ40 “, revision “ > 6.0”, serial number > Device 2: enabled, ID 3, device Hard Drive, start sector 18636800, sector > size 512, sector count 18636800, vendor “DEC ", product “RZ40 “, > revision “ 6.0”, serial number > Device 3: enabled, ID 4, device CDROM, start sector 37273600, sector size > 2048, sector count 148933, vendor “DEC ", product “RRD45“, revision “ > 6.0”, serial number > > I’ve also tried booting from a virtual CDROM, only, with no luck there, > either. In all cases, I get the following from SRM: > test scsi > T-STS-SCSI A - Data Trans test > ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare > T-ERR-SCSI A - id = 1 lun = 0 > > ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare > T-ERR-SCSI A - id = 3 lun = 0 > > ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare > T-ERR-SCSI A - id = 4 lun = 0 > ?? 002 SCSI 0x0008 > > > 84 FAIL > > Does anyone have an idea what might be causing this? Has anyone tried a v6 > SCSI2SD in a DEC 3000? > > Thanks! > - Alex I picked up a couple v6 boards for my AlphaStation 200 4/233, but haven’t tried to use them yet. Are you using the onboard SCSI, or a SCSI board? I’m ‘going to assume you’ve tried a different cable, and to get it working from actual physical drives? Have you tried turning the termination on, on the board? Is your SCSI Bus Terminated? You actually have RZ40’s in the system? I’m asking as I’m not actually familiar with that drive type, at least it’s not one I remember off the top fo my head. I usually use RZ29’s. On my v5.2 board on my VAXstation 4000/90 I think I went with basic 8GB drives, without a vendor string or product string.
SCSI2SD in a DEC 3000/300 - T-ERR-SCSI A
I’ve got a DEC 3000/300 system that has some SCSI drives with aging bearings installed. I’d like to be able to start to migrate some of my systems, like this, to flash media, of some kind, as even my large repository of SCSI disks is starting to dry up. Here is my SRM level info: DEC 3000 - M300 Digital Equipment Corporation VPP PAL V5.56-80800101/OSF PAL V1.45-80800201 - Built on 30-SEP-1996 09:18:31.84 As far as I have read, the SCSI2SD v6 2020 should be compatible with several varieties of DEC hardware, from the VAXen to the Alphas. However, I can’t seem to get anywhere useful with mine. I have the virtual disks configured as follows: >>> sh dev BOOTDEV ADDR DEVTYPENUMBYTES RM/FXWPDEVNAM REV --- --- ----- --- ESA0 08-00-2B-3F-4C-9A , TENBT DKA100 A/1/0 DISK 9.54GB FXRZ40 6.0 DKA300 A/3/0 DISK 9.54GB FXRZ40 6.0 DKA400 A/4/0 RODISK 305.01MB RM WPRRD456.0 All three disks are from the SCSI2SD. I have attempted to make the inquiry strings match the originals, as closely as possible. In the SCSI2SD utility, I have the following config: General page: all defaults, termination off (I have tried parity, scsi2 mode, and setting SCSI speed to sync, with no improvement) Device 1: enabled, ID 1, device Hard Drive, start sector 0, sector size 512, sector count 18636800, vendor “DEC ", product “RZ40 “, revision “ 6.0”, serial number Device 2: enabled, ID 3, device Hard Drive, start sector 18636800, sector size 512, sector count 18636800, vendor “DEC ", product “RZ40 “, revision “ 6.0”, serial number Device 3: enabled, ID 4, device CDROM, start sector 37273600, sector size 2048, sector count 148933, vendor “DEC ", product “RRD45“, revision “ 6.0”, serial number I’ve also tried booting from a virtual CDROM, only, with no luck there, either. In all cases, I get the following from SRM: >>> test scsi T-STS-SCSI A - Data Trans test ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare T-ERR-SCSI A - id = 1 lun = 0 ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare T-ERR-SCSI A - id = 3 lun = 0 ? T-ERR-SCSI A - Data Trans test - nondma/sync inq size miscompare T-ERR-SCSI A - id = 4 lun = 0 ?? 002 SCSI 0x0008 84 FAIL Does anyone have an idea what might be causing this? Has anyone tried a v6 SCSI2SD in a DEC 3000? Thanks! - Alex
