Change font size   Print view

OS 6.1 New Operating System

Discussion board for Mackie's d8b Digital Console users.

Re: OS 6.1 New Operating System

Postby RJH_MUSIC » Tue Jul 20, 2021 3:33 am

The d8b was made in the mid to late 90's to mid 2000 so since if came out before win 2000 was released, my guess is win NT.

Low profile generic ATI Rage xl 8mb pci would not drive video at all.
ATI 128 AGP won't fit. Notch in connector missing

I have more that actually work in another box. I will check tomorrow for model numbers.
2 d8b's 5.1 OS all the plugins, Mackie 32.8 Bus, 2 iMAC 27", Apollo 8 Quad, Cubase 9, Logic Pro X, VEP 6, 4 TB of VSTi Libraries, 28 Roland, Yamaha & Korg Synths and Keyboards, NI Hardware and Software.. Plugins, Plugins, and the list goes on...
User avatar
RJH_MUSIC
Premium Member
Premium Member
 
Posts: 291
Joined: Fri Oct 26, 2012 4:24 pm
Location: Brookfield, CT

Re: OS 6.1 New Operating System

Postby RJH_MUSIC » Tue Jul 20, 2021 3:41 am

I would pay a fair sum to a programmer if needed. $ 500 US. After all said and done, I am spending that now each year in replacement parts. And parts are dwindling.
2 d8b's 5.1 OS all the plugins, Mackie 32.8 Bus, 2 iMAC 27", Apollo 8 Quad, Cubase 9, Logic Pro X, VEP 6, 4 TB of VSTi Libraries, 28 Roland, Yamaha & Korg Synths and Keyboards, NI Hardware and Software.. Plugins, Plugins, and the list goes on...
User avatar
RJH_MUSIC
Premium Member
Premium Member
 
Posts: 291
Joined: Fri Oct 26, 2012 4:24 pm
Location: Brookfield, CT

Re: OS 6.1 New Operating System

Postby doktor1360 » Tue Jul 20, 2021 6:50 pm

Acuma Labs were the last curator of the Mackie D8B operating system code base, if memory serves... it was assigned to them (after the Loud acquisition). That source code base exists somewhere in a repository, locating that is kinda the first issue. Then there's Micro$oft, abandoned or not, the kernel contains their code and that's something they don't/won't give up without some sort of compensation (at minimum)... that's just they way they conduct their business, and they're very protective of anything 'Windows', regardless of legacy...

But again, the largest looming obstacle here is actually locating that code and it's curator - any/all negotiations could then begin... and anything can happen from there... :geek:

Of course...
[Standard Mgmt Disclaimer] - "Your actual mileage may vary..."
--
Dok

"Too many guitars is just about right..." - [Anonymous Player]
User avatar
doktor1360
Premium Member
Premium Member
 
Posts: 487
Joined: Fri Mar 22, 2013 3:33 pm
Location: Marietta 30062, GA, United States

Re: OS 6.1 New Operating System

Postby Y-my-R » Wed Jul 21, 2021 2:37 am

That's very interesting about Acuma Labs being the last to touch the MackieOS. That explains why in the file "udos.mb" in the system5/Firmware folder on the MackieOS drive, has some text at the beginning of all that gibberish, that reads "Acuma Labs Operating System (Version 1.00)". I was wondering, why they'd have anything in the Firmware folder, and if maybe one of the plug-ins needs direct hardware access... but if they were the last "keeper", it all makes sense.

FWIW, I successlessly toyed around with replacing the "graphics.bpd" file in the system5/Drivers folder, in an attempt to get a different video card recognized.
Basically, I just grabbed all the .dll files from the NT4 driver for an NVidia GeGorce FX5200 card that I installed in the D8B rack, renamed them all to "graphics.bpd" and tried to boot the MackieOS with one after the other in the place of the original file with that name.
I didn't have much hope that this would work and it didn't. One of the DLLs gave a memory address error when attempting to use it this way, so that at least confirmed that the MackieOS "attempts" to load the driver from that location.

The next thing I'll try, is to put the original Cirrus Logic card back in, and try swapping the "graphics.bpd" file with dll's from the ATI Radeon VE driver (for different OS versions). If one of them starts, then I'd at least get an idea which of the dll's it is, and can try to figure out what it's for, and try with the "equivalent" dll for another video card.
Of course there's a good chance that there's other code in the MackieOS that needs to tie in with this driver, and/or it's possible that the driver was customized to work within the MackieOS and that no other driver has a chance to function like that... but I gotta start somewhere. And if I could somehow get a more common video card to work in the actual D8B hardware, then I also have a higher chance of emulating such a more common video card within a virtual machine.

Anyway... when looking at the gibberish that appears when opening the original graphics.bpd driver in an editor, it shows a list of video cards in clear text, that I think the driver itself should support (...not sure if there would be additional dll's etc. needed, though).
It also gives some information about turning some emulation on/off for some purpose, but I'd have to figure out where to do that, first.
It also showed a whole bunch of error messages in the code, related to "write combining", that arjepsen had mentioned was a holdup when trying to get a VM to work. So, yeah... it apparently checks for a bunch of that stuff and has error messages ready to go if it isn't right ;)

This is probably not particularly helpful, since I don't expect these cards to be "drop-in" replacements without modification of some code or settings (or they may not work at all), but here's the list of cards from the graphics.bpd driver file... at least there should be a "chance" to get any one of them working, with the driver that came with the D8B (sorry for this monstrous post):
________________________________

Directory file to map PCI device ID's to specific Nucleus driver
; files. This directory file lives in the same directory as all the
; driver files. The format is as follows:
;
; x vvvv:dddd<whitespace><filename>
;
; where vvvv is the PCI vendor ID in hex and dddd is the PCI device ID
; and <filename> is the name of the driver file for the device. The
; value of x should be a 1 if a VBE/AF driver is needed for emulation,
; or 0 if the driver is a pure NoBIOS Nucleus driver.

; ATI

1 1002:4158 mach32.drv ; Mach32
0 1002:4758 mach64gx.drv ; Mach64 GX
0 1002:4358 mach64gx.drv ; Mach64 CX
0 1002:4354 mach64.drv ; Mach64 CT
0 1002:5654 mach64.drv ; Mach64 VT
0 1002:5655 mach64.drv ; Mach64 VTB
0 1002:5656 mach64.drv ; Mach64 VT4
0 1002:4754 mach64.drv ; 3D Rage
0 1002:4754 mach64.drv ; 3D Rage II
0 1002:4755 mach64.drv ; 3D Rage II+
0 1002:4756 mach64.drv ; 3D Rage IIC (PCI)
0 1002:4765 mach64.drv ; 3D Rage IIC (PCI)
0 1002:4757 mach64.drv ; 3D Rage IIC (AGP)
0 1002:4759 mach64.drv ; 3D Rage IIC (AGP)
0 1002:475A mach64.drv ; 3D Rage IIC (AGP)
0 1002:4742 mach64.drv ; 3D Rage Pro
0 1002:4744 mach64.drv ; 3D Rage Pro
0 1002:4749 mach64.drv ; 3D Rage Pro
0 1002:4750 mach64.drv ; 3D Rage Pro
0 1002:4751 mach64.drv ; 3D Rage Pro
0 1002:4C42 mach64.drv ; 3D Rage LT Pro
0 1002:4C44 mach64.drv ; 3D Rage LT Pro
0 1002:4C47 mach64.drv ; 3D Rage LT Pro
0 1002:4C49 mach64.drv ; 3D Rage LT Pro
0 1002:4C50 mach64.drv ; 3D Rage LT Pro
0 1002:4C51 mach64.drv ; 3D Rage LT Pro
0 1002:4C4D mach64.drv ; Rage Mobility (M/M1/P)
0 1002:4C52 mach64.drv ; Rage Mobility (M/M1/P)
0 1002:474D mach64.drv ; Rage XL
0 1002:474E mach64.drv ; Rage XL
0 1002:474F mach64.drv ; Rage XL
0 1002:4752 mach64.drv ; Rage XL
0 1002:5245 rage128.drv ; Rage 128 (GL)
0 1002:5246 rage128.drv ; Rage 128 (GL)
0 1002:534B rage128.drv ; Rage 128 (GL) 4x
0 1002:534C rage128.drv ; Rage 128 (GL) 4x
0 1002:534D rage128.drv ; Rage 128 (GL) 4x
0 1002:534E rage128.drv ; Rage 128 (GL) 4x
0 1002:524B rage128.drv ; Rage 128 (VR)
0 1002:524C rage128.drv ; Rage 128 (VR)
0 1002:5345 rage128.drv ; Rage 128 (VR)
0 1002:5346 rage128.drv ; Rage 128 (VR)
0 1002:5347 rage128.drv ; Rage 128 (VR)
0 1002:5041 rage128.drv ; Rage 128 Pro (GL)
0 1002:5042 rage128.drv ; Rage 128 Pro (GL)
0 1002:5043 rage128.drv ; Rage 128 Pro (GL)
0 1002:5044 rage128.drv ; Rage 128 Pro (GL)
0 1002:5045 rage128.drv ; Rage 128 Pro (GL)
0 1002:5046 rage128.drv ; Rage 128 Pro (GL)
0 1002:5047 rage128.drv ; Rage 128 Pro (VR)
0 1002:5048 rage128.drv ; Rage 128 Pro (VR)
0 1002:5049 rage128.drv ; Rage 128 Pro (VR)
0 1002:504A rage128.drv ; Rage 128 Pro (VR)
0 1002:504B rage128.drv ; Rage 128 Pro (VR)
0 1002:504C rage128.drv ; Rage 128 Pro (VR)
0 1002:504E rage128.drv ; Rage 128 Pro (VR)
0 1002:504F rage128.drv ; Rage 128 Pro (VR)
0 1002:5050 rage128.drv ; Rage 128 Pro (VR)
0 1002:5051 rage128.drv ; Rage 128 Pro (VR)
0 1002:5052 rage128.drv ; Rage 128 Pro (VR)
0 1002:5053 rage128.drv ; Rage 128 Pro (VR)
0 1002:5054 rage128.drv ; Rage 128 Pro (VR)
0 1002:5055 rage128.drv ; Rage 128 Pro (VR)
0 1002:5056 rage128.drv ; Rage 128 Pro (VR)
0 1002:5057 rage128.drv ; Rage 128 Pro (VR)
0 1002:5058 rage128.drv ; Rage 128 Pro (VR)
0 1002:5446 rage128.drv ; Rage 128 Ultra
0 1002:544C rage128.drv ; Rage 128 Ultra
0 1002:5452 rage128.drv ; Rage 128 Ultra
0 1002:5453 rage128.drv ; Rage 128 Ultra
0 1002:5454 rage128.drv ; Rage 128 Ultra
0 1002:5455 rage128.drv ; Rage 128 Ultra
0 1002:4C45 rage128.drv ; Rage Mobility 128 (M3)
0 1002:4C46 rage128.drv ; Rage Mobility 128 (M3)
0 1002:4D46 rage128.drv ; Rage Mobility 128-D4x (M4)
0 1002:4D4C rage128.drv ; Rage Mobility 128-D4x (M4)
0 1002:5144 radeon.drv ; Radeon
0 1002:5145 radeon.drv ; Radeon
0 1002:5146 radeon.drv ; Radeon
0 1002:5147 radeon.drv ; Radeon
0 1002:5159 radeon.drv ; Radeon VE
0 1002:515A radeon.drv ; Radeon VE
0 1002:5157 radeon.drv ; Radeon 7500
0 1002:514C radeon.drv ; Radeon 8500
0 1002:4C59 radeon.drv ; Mobility Radeon
0 1002:4C5A radeon.drv ; Mobility Radeon
0 1002:4C57 radeon.drv ; Mobility Radeon 7500
0 1002:4C58 radeon.drv ; Mobility Radeon 7500

; Chips & Tech

1 102C:FF00 chips.drv ; 64300 WinGine (VLB)
1 102C:FF01 chips.drv ; 64310 WinGine (VLB)
1 102C:FF02 chips.drv ; 65530 (VLB)
1 102C:FF03 chips.drv ; 65535 (VLB)
1 102C:FF04 chips.drv ; 65540 (VLB)
1 102C:FF05 chips.drv ; 65545 (VLB)
1 102C:FF06 chips.drv ; 65546 (VLB)
0 102C:FF07 chips.drv ; 65548 (VLB)
0 102C:FF08 chips550.drv ; 65550 (VLB)
0 102C:FF09 chips550.drv ; 65554 (VLB)
0 102C:FF0A chips550.drv ; 65555 (VLB)
1 102C:00B8 chips.drv ; 64310 WinGine
1 102C:00D8 chips.drv ; 65545, 65546
0 102C:00DC chips.drv ; 65548
0 102C:00E0 chips550.drv ; 65550
0 102C:00E4 chips550.drv ; 65554
0 102C:00E5 chips550.drv ; 65555
1 102C:00F0 chips550.drv ; 68554
1 102C:00F4 chips550.drv ; 68554
1 102C:00F5 chips550.drv ; 68555
0 102C:00C0 chips550.drv ; 69000

; OAK

1 104E:0105 oak.drv ; Spitfire 64105
0 104E:0107 oak.drv ; Spitfire 64107
0 104E:0111 oak.drv ; Spitfire 64111
0 104E:0017 oak.drv ; Eon 64017
0 104E:0217 oak.drv ; Eon 64217
0 104E:0317 oak.drv ; Warp 5

; Trident

1 1023:9420 trident.drv ; TGUI9420
0 1023:9440 tri9440.drv ; TGUI9440
1 1023:9470 trident.drv ; TVG9470
1 1023:9320 tri9440.drv ; Cyber9320
0 1023:9660 tri9680.drv ; TGUI9660, TGUI9680
0 1023:9692 tri9680.drv ; TGUI9682, TGUI9685, Cyber938x
0 1023:9750 tri9750.drv ; 3DImage 975
0 1023:9397 tri9750.drv ; Cyber9397
0 1023:939A tri9750.drv ; Cyber9397
0 1023:9850 tri9750.drv ; 3DImage 985
0 1023:9880 tri9750.drv ; Blade 3D
0 1023:8400 tri9750.drv ; Blade 3D (VIA VT8501)
0 1023:8500 tri9750.drv ; Blade 3D (VIA VT8601)

; Tseng Labs

1 100C:FF00 tseng.drv ; ET3000 (ISA)
1 100C:FF01 tseng.drv ; ET4000 (ISA)
1 100C:FF02 tseng.drv ; ET4000/W32 (VLB)
1 100C:FF03 tseng.drv ; ET4000/W32i (VLB)
0 100C:FF04 tseng.drv ; ET4000/W32p (VLB)
1 100C:FF05 tseng.drv ; ET6000 (VLB)
0 100C:3202 tseng.drv ; ET4000/W32p
0 100C:3205 tseng.drv ; ET4000/W32p
0 100C:3206 tseng.drv ; ET4000/W32p
0 100C:3207 tseng.drv ; ET4000/W32p
0 100C:3208 tseng.drv ; ET6000, ET6100

; S3

1 107D:0000 s3io.drv ; 86c805PCI
1 5333:88B0 s3io.drv ; 86c928PCI
0 5333:88C0 s3mm.drv ; Vision 864
0 5333:88C1 s3mm.drv ; Vision 864
0 5333:88D0 s3mm.drv ; Vision 964
0 5333:88D1 s3mm.drv ; Vision 964
0 5333:8880 s3mm.drv ; Vision 868
0 5333:8890 s3mm.drv ; Vision 868
0 5333:88F0 s3mm.drv ; Vision 968
0 5333:8810 s3mm.drv ; Trio32, Trio64
0 5333:8811 s3mm.drv ; Trio64V+
0 5333:8814 s3mm.drv ; Trio64UV+
0 5333:8901 s3mm.drv ; Trio64V2/DX
0 5333:8812 s3mm.drv ; Aurora64V+
0 5333:5631 s3virge.drv ; Virge
0 5333:883D s3virge.drv ; Virge/VX
0 5333:8A01 s3virge.drv ; Virge/DX/GX
0 5333:8A10 s3virge.drv ; Virge/GX2
0 5333:8C03 s3virge.drv ; Virge/MX
0 5333:8904 trio3d.drv ; Trio3D
0 5333:8A13 trio3d.drv ; Trio3D/2X
0 5333:8A20 savage3d.drv ; Savage3D
0 5333:8A21 savage3d.drv ; Savage3D
0 5333:8A22 savage3d.drv ; Savage4
0 5333:8C10 savage3d.drv ; Savage/MX/IX
0 5333:8C11 savage3d.drv ; Savage/MX/IX
0 5333:8C12 savage3d.drv ; Savage/MX/IX
1 5333:8C22 savage3d.drv ; SuperSavage 128
1 5333:8C2A savage3d.drv ; SuperSavage 128
1 5333:8C2C savage3d.drv ; SuperSavage/IX
0 5333:8C2E savage3d.drv ; SuperSavage/IXC
0 5333:8C2F savage3d.drv ; SuperSavage/IXC
0 5333:9102 savage2k.drv ; Savage2000

; Avance Logic

1 1005:2301 avance.drv ; ALG2301
1 4005:2302 avance.drv ; ALG2302
1 4005:2064 avance.drv ; ALG2032, ALG2064
1 4005:2501 avance.drv ; ALG2564, ALG25128

; Macronix

1 10D9:0066 mxic.drv ; MXIC 86101
1 10D9:8888 mxic.drv ; MXIC 86200
0 10D9:8625 mxic250.drv ; MXIC 86250
0 10D9:8626 mxic251.drv ; MXIC 86251

; Cirrus Logic

0 1013:00A0 cirrus.drv ; CL-GD5430
0 1013:00A0 cirrus.drv ; CL-GD5440
0 1013:00A8 cirrus.drv ; CL-GD5434
0 1013:00AC cirrus.drv ; CL-GD5436
0 1013:00B8 cirrus.drv ; CL-GD5446
1 1013:1204 cirrus.drv ; CL-GD7541
1 1013:1200 cirrus.drv ; CL-GD7542
0 1013:FF0C cirrus.drv ; CL-GD7543 VLB
0 1013:1202 cirrus.drv ; CL-GD7543
1 1013:1210 cirrus.drv ; CL-GD7548
1 1013:0038 cirrus.drv ; CL-GD7548
0 1013:0040 cirrus.drv ; CL-GD7555

; Cirrus Logic Laguna

0 1013:00D0 cirr546x.drv ; Laguna 5462
0 1013:00D4 cirr546x.drv ; Laguna 5464
0 1013:00D6 cirr546x.drv ; Laguna 5465

; Compaq

1 0E11:3032 compaq.drv ; QVision 1280
1 0E11:3033 compaq.drv ; QVision 1280
1 0E11:3034 compaq.drv ; QVision 1280

; Number Nine

0 105D:2309 num9.drv ; Imagine 128 Series I
0 105D:2339 num9.drv ; Imagine 128 Series II
0 105D:493D num9.drv ; Ticket 2 Ride
0 105D:5348 num9.drv ; Revolution IV

; Weitek

0 100E:9001 weitek.drv ; P9000
0 100E:9100 weitek.drv ; P9100

; IIT

1 1061:0001 iit.drv ; AGX-01x

; ARK Logic

1 EDD8:FF00 ark.drv ; ARK1000VL (VLB)
0 EDD8:A091 ark.drv ; ARK1000PV
0 EDD8:A099 ark.drv ; ARK2000PV
0 EDD8:A0A1 ark.drv ; ARK2000MT
0 EDD8:A0A9 ark.drv ; Quadro64
0 EDD8:A0B1 ark.drv ; Quadro64
1 EDD8:A0C1 ark.drv ; Quadro64+
1 EDD8:A0C9 ark.drv ; Quadro64+

; Sierra

1 10A8:0000 sierra.drv ; Falcon/64
1 10A8:0004 sierra.drv ; Falcon/64
1 10A8:0005 sierra.drv ; Falcon/64
1 10A8:0006 sierra.drv ; Falcon/64
1 10A8:0007 sierra.drv ; SuperScaler 220

; Acer Labs

1 10B9:3145 acer.drv ; M3141, M3145
1 10B9:3147 acer.drv ; M3147V

; Matrox

1 102B:0518 matrox.drv ; MGA Ultima
1 102B:0D10 matrox.drv ; MGA Impression Plus
0 102B:0519 matrox.drv ; MGA Millennium
0 102B:051B matrox.drv ; MGA Millennium II
0 102B:051F matrox.drv ; MGA Millennium II (AGP)
0 102B:051A matrox.drv ; MGA Mystique
0 102B:051A matrox.drv ; MGA Mystique 220
0 102B:1000 mgag200.drv ; MGA-G100
0 102B:1001 mgag200.drv ; MGA-G100 (AGP)
0 102B:0520 mgag200.drv ; MGA-G200
0 102B:0521 mgag200.drv ; MGA-G200 (AGP)
0 102B:0525 mgag200.drv ; MGA-G400 (AGP)
0 102B:2527 mgag200.drv ; MGA-G550 (AGP)

; Alliance

1 1142:3210 alli6410.drv ; ProMotion 6410
0 1142:6422 alliat3d.drv ; ProMotion 6422
0 1142:6424 alliat3d.drv ; ProMotion AT24
0 1142:6425 alliat3d.drv ; ProMotion AT25
0 1142:643D alliat3d.drv ; ProMotion AT3D

; SiS

0 1039:0001 sis.drv ; 6201
0 1039:0002 sis.drv ; 6202
0 1039:0205 sis.drv ; 6205
0 1039:0204 sis.drv ; 6215
0 1039:0200 sis.drv ; 5597/5598
0 1039:6326 sis.drv ; 6326
0 1039:6306 sis530.drv ; 530
0 1039:0300 sis530.drv ; 300/305
0 1039:6300 sis530.drv ; 630/730

; NVIDIA

1 104A:0008 nvidia.drv ; STG2000
1 10DE:0008 nvidia.drv ; NV1
0 12D2:0018 nvidia.drv ; RIVA-128
0 10DE:0020 nvidia.drv ; RIVA-TNT
0 10DE:0028 nvidia.drv ; RIVA-TNT2
0 10DE:0029 nvidia.drv ; RIVA-TNT2 Ultra
0 10DE:002C nvidia.drv ; RIVA-TNT2 Vanta
0 10DE:002D nvidia.drv ; RIVA-TNT2 M64
0 10DE:00A0 nvidia.drv ; Aladdin TNT2
0 10DE:0100 nvidia.drv ; GeForce 256
0 10DE:0101 nvidia.drv ; GeForce DDR
0 10DE:0103 nvidia.drv ; Quadro
0 10DE:0110 nvidia.drv ; GeForce2 MX
0 10DE:0111 nvidia.drv ; GeForce2 MX
0 10DE:0112 nvidia.drv ; GeForce2 MX Mobile
0 10DE:0113 nvidia.drv ; Quadro2 MXR
0 10DE:01A0 nvidia.drv ; GeForce2 Integrated GPU
0 10DE:0150 nvidia.drv ; GeForce2 GTS
0 10DE:0151 nvidia.drv ; GeForce2 GTS
0 10DE:0152 nvidia.drv ; GeForce2 Ultra
0 10DE:0153 nvidia.drv ; Quadro2 Pro
0 10DE:0200 nvidia.drv ; GeForce3
0 10DE:0201 nvidia.drv ; GeForce3
0 10DE:0202 nvidia.drv ; GeForce3
0 10DE:0203 nvidia.drv ; Quadro DCC


; New boards we don't support yet
; GeForce4 MX 420
; GeForce4 MX 440
; GeForce4 MX 460
; GeForce4 Ti 4400
; GeForce4 Ti 4600
; Quadro4 NVS
; Quadro4 500 XGL
; Quadro4 550 XGL
; Quadro4 700 XGL
; Quadro4 750 XGL
; Quadro4 900 XGL

; NeoMagic

0 10C8:0000 neomagic.drv ; NM2070A
0 10C8:0001 neomagic.drv ; NM2070B
0 10C8:0002 neomagic.drv ; NM2090
0 10C8:0003 neomagic.drv ; NM2093
0 10C8:8003 neomagic.drv ; NM2097
0 10C8:0004 neomagic.drv ; NM2160
0 10C8:8004 neomagic.drv ; NM2160B
0 10C8:0005 neomagic.drv ; NM2200
0 10C8:0025 neomagic.drv ; NM2230
0 10C8:0006 neomagic.drv ; NM2360
0 10C8:0016 neomagic.drv ; NM2380

; Paradise/Phillips

0 101C:9710 philips.drv ; Pipeline 9710
0 101C:9712 philips.drv ; Pipeline 9712

; BrookTree

1 109E:2115 brookt.drv ; BtV 2115

; InteGraphics

1 10EA:1680 igs.drv ; IGA1680
1 10EA:1682 igs.drv ; IGA1682
1 10EA:1683 igs.drv ; IGA1683
0 10EA:2000 igs.drv ; CyberPro2000
0 10EA:2010 igs.drv ; CyberPro2010

; Chromatic Research

1 110B:0001 chromat.drv ; Mpact!

; 3DLabs

0 3D3D:0004 3dlabs.drv ; Permedia
0 3D3D:0007 3dlabs.drv ; Permedia 2
0 3D3D:0009 3dlabs.drv ; Permedia 2V
0 3D3D:000A perm3.drv ; Permedia 3
0 104C:3D04 3dlabs.drv ; Permedia
0 104C:3D07 3dlabs.drv ; Permedia 2
0 104C:3D09 3dlabs.drv ; Permedia 2V
0 104C:3D0A perm3.drv ; Permedia 3

; 3Dfx

0 121A:0003 3dfx.drv ; Banshee
0 121A:0005 3dfx.drv ; Voodoo3
0 121A:0009 3dfx.drv ; Voodoo4
0 121A:0009 3dfx.drv ; Voodoo5

; iXMICRO

1 10E0:9128 tt128.drv ; TwinTurbo 128
1 10E0:9135 tt1283d.drv ; TwinTurbo 128-3D

; Rendition

0 1163:0001 renditn.drv ; Verite V1000
0 1163:2000 renditn.drv ; Verite V2200

; WinBond

1 1050:9970 winbond.drv ; W9970CF

; Intel

0 8086:7800 intel.drv ; i740
0 003D:00D1 intel.drv ; i740 PCI
0 8086:7121 i810.drv ; i810
0 8086:7123 i810.drv ; i810/DC100
0 8086:7125 i810.drv ; i810E
0 8086:1132 i810.drv ; i815
0 8086:2562 i845.drv ; i845G

; Tritech

1 1292:FC04 tritech.drv ; TR25204

; Silicon Motion

1 126F:0910 smi.drv ; SM910

; Cyrix MediaGX

0 1078:FF00 mediagx.drv ; MediaGX/MediaGXi
0 1078:0104 mediagx.drv ; MediaGXm

; Sigma Designs

0 1236:6401 sigma.drv ; RealMagic 64GX
User avatar
Y-my-R
Premium Member
Premium Member
 
Posts: 590
Joined: Mon May 29, 2017 12:14 am
Location: Van Nuys, CA

Re: OS 6.1 New Operating System

Postby RJH_MUSIC » Wed Jul 21, 2021 3:01 am

That's okay. Great info. The ATI Sapphire card that works in my d8b is actually a Radron 7000 64mb DDR V/D V/O PCI. UGA Fort Worth but the GTI ports do not work I think that's funny because I was training you in a job milking TV on to HDMI not supported.

It is also possible that the low profile cards I bought which are only 8mb may not gave enough memory on them. They are Gesticulating ATI Rage XL 8mb PCI.

RH
2 d8b's 5.1 OS all the plugins, Mackie 32.8 Bus, 2 iMAC 27", Apollo 8 Quad, Cubase 9, Logic Pro X, VEP 6, 4 TB of VSTi Libraries, 28 Roland, Yamaha & Korg Synths and Keyboards, NI Hardware and Software.. Plugins, Plugins, and the list goes on...
User avatar
RJH_MUSIC
Premium Member
Premium Member
 
Posts: 291
Joined: Fri Oct 26, 2012 4:24 pm
Location: Brookfield, CT

Re: OS 6.1 New Operating System

Postby RJH_MUSIC » Wed Jul 21, 2021 3:07 am

Interesting that this card is listed on your list but it looks like mach64 refers to possibly 64mb? Since mine are 8mb maybe thar is why they don't work. It is also quite possible that the vendor on eBay sold me two cards that are bad
2 d8b's 5.1 OS all the plugins, Mackie 32.8 Bus, 2 iMAC 27", Apollo 8 Quad, Cubase 9, Logic Pro X, VEP 6, 4 TB of VSTi Libraries, 28 Roland, Yamaha & Korg Synths and Keyboards, NI Hardware and Software.. Plugins, Plugins, and the list goes on...
User avatar
RJH_MUSIC
Premium Member
Premium Member
 
Posts: 291
Joined: Fri Oct 26, 2012 4:24 pm
Location: Brookfield, CT

Re: OS 6.1 New Operating System

Postby Y-my-R » Wed Jul 21, 2021 3:33 am

If I remember right, Mach32 and Mach64 cards were ATI video card models. I'd guess they were using 32 bit or 64 bit of (bus) bandwidth, respectively (I don't think it's for the memory on those cards... those were pretty early, and 64 MB were still A LOT for a video card).

As mentioned, I don't think all the cards on that list will work as a drop-in replacement, but there's a chance that they might get recognized. However, I just found something that may point to this being more of a dead end, than I had expected:

The "graphics.bpd" file, that appears to be the video driver used by the D8B, has code in it that does a "ISV License" check/confirmation. So, this sort of thing:

https://docs.microsoft.com/en-us/dynami ... -licensing

Since the check for such an "independent software vendor license" happens from within the video driver code itself, I would assume that this means that Mackie paid a programmer to customize an existing driver for their purposes, and the programmer protected their work with such a license check.
Maybe Mackie just asked the programmer to to make the driver smaller and strip out anything that isn't necessary (which would likely strip out support for a lot of cards on that list) to make it smaller... but maybe customization was necessary to make it play nice with how the MackieOS presents its video stream to the hardware, or something.

If it's a customized video driver, then the Virtual Machine approach has very little chance of success. At least I'm not aware of VM software with the ability to customize their hardware virtualizations to the point of customizing the hardware configuration and response.

I'll play around with it a bit more, but this might point to the VM thing being a dead end...
User avatar
Y-my-R
Premium Member
Premium Member
 
Posts: 590
Joined: Mon May 29, 2017 12:14 am
Location: Van Nuys, CA

Re: OS 6.1 New Operating System

Postby doktor1360 » Wed Jul 21, 2021 3:55 am

RJH_MUSIC wrote:Interesting that this card is listed on your list but it looks like mach64 refers to possibly 64mb? Since mine are 8mb maybe thar is why they don't work. It is also quite possible that the vendor on eBay sold me two cards that are bad

That could be... I've never had a problem with any video card using the ATI Radeon 7000 series chipset in any of the Mackie gear (D8B/HDR), regardless of vendor - ATI, Sapphire, Diamond... all had 64MB graphics memory on board if that's of any assistance. As long as they're loading any stock driver of the MackieOS, it should work. Memory addressing when the .DLL loads is internally important - it'll know where in system RAM to find the support file(s) the link libraries are loading at startup. If you can, might wanna target that sweet spot of a Radeon 7000 chipset implementation w/ 64MB RAM support on the card. I'd be interested in those results, because if that works, it lets the Genie out of the Bottle of 'What Ifs'...
--
Dok

"Too many guitars is just about right..." - [Anonymous Player]
User avatar
doktor1360
Premium Member
Premium Member
 
Posts: 487
Joined: Fri Mar 22, 2013 3:33 pm
Location: Marietta 30062, GA, United States

Re: OS 6.1 New Operating System

Postby Y-my-R » Wed Jul 21, 2021 10:46 pm

Thanks Dok! That's useful info! I think depending on how the memory jarsets are set up, it might actually be important that the video card has exactly 64 MB of memory, so the memory addresses are exactly where expected... but not sure. (I remember reading something like that when reading up on 8086 processor structures and memory access over 20 years ago... but am really blurry on all that now).

I think what I said about the ISV License thing is probably wrong... I jumped to conclusions too quickly. Sorry!

Anyway, when trying to google for a VM that can emulate the Radeon 7000, I found this old thread, that describes pretty much every step I took so far and then some (but in a much better structured and readable way, with fewer words but more details than I shared... brevity was never my strength):

http://www.d8bforum.com/phpBB3/viewtopi ... t=10#p7090

Sounds like the author of that post, @elperroromel, tried exactly the same stuff I did so far, then got a bit further with the Vendor/Device IDs and then got stuck at the "write combining" thing @arjepsen had mention.
Well... maybe more video card emulation options are available today than in 2013, so I'll keep looking around.

I guess I'll post fewer of my brain-farts here, and will just keep trying on my end until I actually made any kind of progress. So, don't wonder if I go quiet on this thread for a while, but I'll keep experimenting with it silently in the background. There's a good chance that this will drag out for months on end, though, so don't hold your breath ;)

Thanks again for all the good info, everyone! I'll drop in again if I have anything worthwhile to report! :D
User avatar
Y-my-R
Premium Member
Premium Member
 
Posts: 590
Joined: Mon May 29, 2017 12:14 am
Location: Van Nuys, CA

Re: OS 6.1 New Operating System

Postby RJH_MUSIC » Thu Jul 22, 2021 4:49 am

Well I can confirm something you said about cards listed in the file not actually working. First, tonight I wrote down all of the models I have that work:

Cirrus Logic ky2 CLVGA 54 PCI. This was the original video card that came with my first d8b.
ATI Rage 128 8m AGP card that came with unit I purchased last weekend.

Here is the kicker- I ordered an ATI rage 128 ultra AGP card low profile from the eBay last week and it came today. So I installed it in my build unit and got a big smile on my face when the computer booted up and the screen came alive. Short lived, it got all the way to the loading the OS and stopped. Last message on the screen said remove the disk and press ESC to reboot. Loading System.

And that exact card is listed in the file you posted. I have a thought though. When I was reading the manual for the newer style motherboard it noted that the AGP card is designed to directly address system memory. I wonder if maybe there's not enough memory in the D8B to drive it and if I increase the memory might it work.
2 d8b's 5.1 OS all the plugins, Mackie 32.8 Bus, 2 iMAC 27", Apollo 8 Quad, Cubase 9, Logic Pro X, VEP 6, 4 TB of VSTi Libraries, 28 Roland, Yamaha & Korg Synths and Keyboards, NI Hardware and Software.. Plugins, Plugins, and the list goes on...
User avatar
RJH_MUSIC
Premium Member
Premium Member
 
Posts: 291
Joined: Fri Oct 26, 2012 4:24 pm
Location: Brookfield, CT

PreviousNext

Return to d8b Forum

Who is online

Users browsing this forum: Google [Bot] and 46 guests