I was wondering if anybody remembers which networking vendors supported
StarLAN 1, or 802.3e / 1Base5, back in the 1980s? Hoping to get product
names and/or model numbers.
I've come across some references to Western Digital, Micom-Interlan,
Cross Comm Corp (Massachusetts), and Fox Research (later DCA?) possibly
having offered products to bridge StarLAN to Ethernet. But in the few
cases where I've seen a model (ex. Cross Comm 487 Series) I haven't been
able to get past blurbs in Info World.
I have one host interface, expect more to arrive shortly, and would love
to track down a bridge/switch/router that might allow me to make them
reachable from Ethernet.
Thanks,
--Steve.
On Aug 17, 2020, at 12:43 AM, Tom Hunter via cctalk
<cctalk at classiccmp.org> wrote:
> >
> > Has SIMH been ported to a low overhead (instant-on) platform?
>
> I use NetBSD on a surplus HP ProLiant DL360p Gen8, NetBSD 9.0-stable
> boots in just a few seconds. The hardware itself takes a couple minutes
> to go through its bootstrap process, however. (I should have considered
> setting up ESXi and installing NetBSD atop that to avoid the hardware
> boot process, since I'm regularly rebuilding and updating NetBSD?)
It's funny, but it seems to be true that the pricier hardware takes longer
to POST. I bought several AMD AM1 CPUs / motherboards when a set only
cost $50 and I use them as routers running NetBSD. From power on to
booting the kernel is less than three seconds. Getting to fully multiuser
is less than 30 seconds, even with DHCP.
> Oh yeah, NetBSD 9.0-stable 64-bit also only takes a few seconds to boot
> on a Raspberry Pi 3B+. It's easy enough to just throw on an SD card and
> try out. Alas the Raspberry Pi 4 isn't supported yet by NetBSD, though I
> think it's coming along. An RPi4 with 4 or 8GB of RAM should be a very
> nice turnkey SIMH server.
Yes, the Pis boot very quickly. The Pi 4 is supported, but just not in
NetBSD 9. The Pi 4 takes a wee bit longer to boot because it uses UEFI,
but I think the difference in performance is well worth the extra few
seconds.
https://github.com/pftf/RPi4https://twitter.com/AnachronistJohn/status/1287628712981049345
A bonus is that you can boot directly off of USB attached storage
(although I'm still loading UEFI and the kernel off of the SD card).
SIMH runs very well on the Pi 4.
John
Classic Computer Fans,
Technically this isn't a classic OS, but I suspect its lineage goes back far
enough to be of interest. Has anyone tried out UniSys ClearPath OS/2200
Express?
https://www.UniSys.com/offerings/clearpath-forward/clearpath-forward-produc…
I normally don't run Windows at home, but have set up a Windows 7 VM to try
it out. It includes a few PDFs, including basic startup and shutdown
procedures. I haven't found any intro to OS/2200 type docs yet. If anyone
knows of any, please let me know. It looks like it could be an interesting
system, if I can ever learn my way around.
--
Kevin
http://www.RawFedDogs.nethttp://www.Lassie.xyzhttp://www.WacoAgilityGroup.org
Bruceville, TX
What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
>
> Date: Mon, 17 Aug 2020 00:22:52 -0700
> From: Brendan Shanks <brendan at bslabs.net>
> Subject: Sun/3-powered 737 flight sim
>
> Something that I thought the folks here would appreciate: a fellow in
> Dubai is trying to keep a full-motion Boeing 737-300 sim (from 1991)
> running.
> The main host machine is a Sun/3E, connected over Ethernet to the operator
> workstation which has 2 Sun/3Es each with a cgtwo powering a CRT touch
> screen. One of the Sun VME SCSI/Ethernet boards died, and he?s been unable
> to find a (working) replacement board.
>
> There?s also a big rack of Concurrent hardware running OS/32, and some
> newer PCs for visuals and TCAS.
>
> Plenty of pictures and a video tour of all the hardware at:
> <
> https://www.reddit.com/r/BSD/comments/i8c8u7/how_do_i_emulate_a_sun_3e_comp…
> <
> https://www.reddit.com/r/BSD/comments/i8c8u7/how_do_i_emulate_a_sun_3e_comp…
> >>
>
> Brendan
>
I have a Sun 3/E, including a SCSI/Ethernet board, that ran fine the last
time it was powered on. There is a collector in southern Germany who also
has a 3/E board set. I didn't see any contact information for the simulator
owners.
--
Michael Thompson
Greetings.
I would like to solve a mistery regarding graphical user interface on a Sun
Ultra 10+ Creator3D UPA graphics card, running OpenBSD 6.7/sparc64.
Everything works fine with Solaris 10. Did anybody manage to get X running
on openBSD? Sparc64 support is somehow bogus so I feel that if I talk to
them, there will be no answer.
Here is what I am trying to do and hope will help others:
- installed openBSD on two Sun Ultra 10 machines: one machine full install
(with X packages), the other without X, but xenocara compiled later;
- Configured /etc/X11/xorg.conf as described in attached file 1;
The same issues were observed for both Xorg and xenocara, so I suspect
there's something wrong with sunffb:
- /var/log/Xorg.0.log shows everything is in order (except for a xaa
warning) as described in attached file 2;
- at each startx (without system reboot), X registers a new display :0
:1 :2 :3 and so on. It never falls back to :0 unless I tell it
manually to do so: startx -- :0 - so at this time, for both machines the
attached file 2 is "/var/log/Xorg.10.log" (last X session);
- startx says "Unknown boardID[000000ff], assuming FFB2, DoubleRES,
Z-buffer, Single-buffered.";
- dmesg is shown in attached file 3;
- GUI starts, as confirmed by ps aux;
- Screen becomes white, the previous black text becomes yellow. Window
manager (wmaker) is running;
- if creator0 kernel flag is set to 1 (disable accel), some blue dots
appear instead of yellow text, but still no graphics;
- I tried both default, 28.636 and 29.5 "Option" "ReferenceClock" according
to xorg.conf manual - Xorg.0.log reports this option is never used;
- if I start X11vnc, I can get a vnc client connection but the screen is
white - so I suspect there is some wrong memory mapping: sunffb is using
some bogus memory location while x11vnc is reading from somewhere else.
Did anyone encounter this problem?
Please advise.
Best wishes,
Vasile Buruiana (bvasea!gmail[]com)
____________________________
Attached file 1: /etc/X11/xorg.conf
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "Xinerama" "On"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection
Section "Module"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "Protocol" "wskbd"
Option "Device" "/dev/wskbd0"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "SunMouse"
Option "Device" "/dev/tty00"
Option "BaudRate" "1200"
EndSection
Section "Monitor"
Identifier "Monitor"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 31.5-60
VertRefresh 50-70
EndSection
Section "Device"
Identifier "creator0"
# Driver "wsfb"
# Option "device" "/dev/ttyC0"
Driver "sunffb"
Option "ReferenceClock" "28.636"
# Option "UseFBDev" "true"
# Option "accel" "True"
VendorName "Elite3D"
BoardName "SUNW"
# Option "device" "/dev/console"
EndSection
Section "Screen"
Identifier "Screen0"
Device "creator0"
Monitor "Monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
FbBpp 32
Weight 8 8 8
EndSubSection
EndSection
__________________________________________________________
attached file 2: /var/log/Xorg.10.log
__________________________________________________________
[ 3904.433] (--) Using wscons driver on /dev/ttyD0
[ 3904.476]
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
[ 3904.477] Build Operating System: OpenBSD 6.7 sparc64
[ 3904.479] Current Operating System: OpenBSD frectie.seprom.ro 6.7
GENERIC#306 sparc64
[ 3904.482] Build Date: 16 August 2020 02:14:23AM
[ 3904.482]
[ 3904.483] Current version of pixman: 0.38.4
[ 3904.483] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3904.484] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3904.489] (==) Log file: "/var/log/Xorg.10.log", Time: Sun Aug 16
10:31:31 2020
[ 3904.493] (==) Using config file: "/etc/X11/xorg.conf"
[ 3904.493] (==) Using system config directory
"/usr/X11R6/share/X11/xorg.conf.d"
[ 3904.496] Parse error on line 10 of section Files in file
/etc/X11/xorg.conf
Ignoring obsolete keyword "RgbPath".
[ 3904.499] (==) ServerLayout "X.org Configured"
[ 3904.499] (**) |-->Screen "Screen0" (0)
[ 3904.499] (**) | |-->Monitor "Monitor"
[ 3904.505] (**) | |-->Device "creator0"
[ 3904.505] (**) |-->Input Device "Mouse0"
[ 3904.506] (**) |-->Input Device "Keyboard0"
[ 3904.507] (**) Option "Xinerama" "On"
[ 3904.507] (==) Automatically adding devices
[ 3904.507] (==) Automatically enabling devices
[ 3904.507] (==) Not automatically adding GPU devices
[ 3904.508] (**) Xinerama: enabled
[ 3904.508] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 3904.509] (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not
exist.
[ 3904.509] Entry deleted from font path.
[ 3904.510] (**) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/75dpi/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[ 3904.510] (==) ModulePath set to "/usr/X11R6/lib/modules"
[ 3904.510] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse'
or 'vmmouse' will be disabled.
[ 3904.510] (WW) Disabling Mouse0
[ 3904.511] (WW) Disabling Keyboard0
[ 3904.511] (II) Loader magic: 0xeefafa6010
[ 3904.511] (II) Module ABI versions:
[ 3904.511] X.Org ANSI C Emulation: 0.4
[ 3904.511] X.Org Video Driver: 24.1
[ 3904.511] X.Org XInput driver : 24.1
[ 3904.511] X.Org Server Extension : 10.0
[ 3904.520] (--) PCI:*(1 at 0:2:0) 1002:4750:0000:0000 rev 92, Mem @
0xe1000000/16777216, 0xe2000000/4096, I/O @ 0x00000000/256, BIOS @
0x????????/131072
[ 3904.521] (II) "glx" will be loaded by default.
[ 3904.521] (II) LoadModule: "glx"
[ 3904.526] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[ 3904.559] (II) Module glx: vendor="X.Org Foundation"
[ 3904.559] compiled for 1.20.8, module version = 1.0.0
[ 3904.559] ABI class: X.Org Server Extension, version 10.0
[ 3904.560] (II) LoadModule: "sunffb"
[ 3904.563] (II) Loading /usr/X11R6/lib/modules/drivers/sunffb_drv.so
[ 3904.564] (II) Module sunffb: vendor="X.Org Foundation"
[ 3904.565] compiled for 1.20.8, module version = 1.2.2
[ 3904.565] Module class: X.Org Video Driver
[ 3904.565] ABI class: X.Org Video Driver, version 24.1
[ 3904.565] (II) SUNFFB: driver for Creator, Creator 3D and Elite 3D
[ 3904.565] (WW) Falling back to old probe method for sunffb
[ 3904.567] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card
support
[ 3904.568] (**) SUNFFB(0): RGB weight 888
[ 3904.568] (==) SUNFFB(0): Default visual is TrueColor
[ 3904.569] (==) SUNFFB(0): Using gamma correction (1.0, 1.0, 1.0)
[ 3904.569] (==) SUNFFB(0): Using HW cursor
[ 3904.569] (II) Loading sub module "fb"
[ 3904.569] (II) LoadModule: "fb"
[ 3904.576] (II) Loading /usr/X11R6/lib/modules/libfb.so
[ 3904.579] (II) Module fb: vendor="X.Org Foundation"
[ 3904.579] compiled for 1.20.8, module version = 1.0.0
[ 3904.579] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3904.579] (II) Loading sub module "xaa"
[ 3904.579] (II) LoadModule: "xaa"
[ 3904.592] (WW) Warning, couldn't open module xaa
[ 3904.592] (EE) SUNFFB: Failed to load module "xaa" (module does not
exist, 0)
[ 3904.592] (II) SUNFFB(0): Loading XAA failed, acceleration disabled
[ 3904.592] (II) Loading sub module "ramdac"
[ 3904.592] (II) LoadModule: "ramdac"
[ 3904.593] (II) Module "ramdac" already built-in
[ 3904.593] (II) Loading sub module "dbe"
[ 3904.593] (II) LoadModule: "dbe"
[ 3904.593] (II) Module "dbe" already built-in
[ 3904.593] (==) SUNFFB(0): DPI set to (96, 96)
[ 3904.598] (II) creator0: Unknown boardID[000000ff], assuming FFB2,
DoubleRES, Z-buffer, Single-buffered.
[ 3904.600] (II) creator0: BT9068 (PAC1) ramdac detected (with normal
cursor control)
[ 3904.601] (II) creator0: Detected Creator/Creator3D
[ 3904.606] (==) SUNFFB(0): Backing store enabled
[ 3904.606] (==) SUNFFB(0): Silken mouse enabled
[ 3904.609] (==) SUNFFB(0): DPMS enabled
[ 3904.610] (WW) SUNFFB(0): Option "ReferenceClock" is not used
[ 3904.610] (II) Initializing extension Generic Event Extension
[ 3904.616] (II) Initializing extension SHAPE
[ 3904.622] (II) Initializing extension MIT-SHM
[ 3904.628] (II) Initializing extension XInputExtension
[ 3904.634] (II) Initializing extension XTEST
[ 3904.640] (II) Initializing extension BIG-REQUESTS
[ 3904.646] (II) Initializing extension SYNC
[ 3904.652] (II) Initializing extension XKEYBOARD
[ 3904.657] (II) Initializing extension XC-MISC
[ 3904.663] (II) Initializing extension SECURITY
[ 3904.669] (II) Initializing extension XINERAMA
[ 3904.669] (II) Initializing extension XFIXES
[ 3904.675] (II) Initializing extension RENDER
[ 3904.681] (II) Initializing extension RANDR
[ 3904.681] (II) Initializing extension COMPOSITE
[ 3904.687] (II) Initializing extension DAMAGE
[ 3904.693] (II) Initializing extension MIT-SCREEN-SAVER
[ 3904.698] (II) Initializing extension DOUBLE-BUFFER
[ 3904.704] (II) Initializing extension RECORD
[ 3904.710] (II) Initializing extension DPMS
[ 3904.715] (II) Initializing extension Present
[ 3904.721] (II) Initializing extension DRI3
[ 3904.721] (II) Initializing extension X-Resource
[ 3904.727] (II) Initializing extension XVideo
[ 3904.732] (II) Initializing extension XVideo-MotionCompensation
[ 3904.732] (II) Initializing extension GLX
[ 3904.739] (II) AIGLX: Screen 0 is not DRI2 capable
[ 3904.868] (II) IGLX: Loaded and initialized swrast
[ 3904.868] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 3904.868] (II) Initializing extension XFree86-VidModeExtension
[ 3904.874] (II) Initializing extension XFree86-DGA
[ 3904.879] (II) Initializing extension XFree86-DRI
[ 3904.879] (II) Initializing extension DRI2
[ 3907.959] (II) config/wscons: checking input device /dev/wskbd
[ 3907.959] (II) wskbd: using layout us
[ 3907.960] (II) LoadModule: "kbd"
[ 3907.965] (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.so
[ 3907.968] (II) Module kbd: vendor="X.Org Foundation"
[ 3907.968] compiled for 1.20.8, module version = 1.9.0
[ 3907.968] Module class: X.Org XInput Driver
[ 3907.968] ABI class: X.Org XInput driver, version 24.1
[ 3907.968] (II) Using input driver 'kbd' for '/dev/wskbd'
[ 3907.969] (**) /dev/wskbd: always reports core events
[ 3907.970] (**) /dev/wskbd: always reports core events
[ 3907.970] (**) Option "Protocol" "standard"
[ 3907.971] (**) Option "XkbRules" "base"
[ 3907.971] (**) Option "XkbModel" "pc105"
[ 3907.971] (**) Option "XkbLayout" "us"
[ 3907.971] (II) XINPUT: Adding extended input device "/dev/wskbd" (type:
KEYBOARD, id 6)
[ 3907.977] (II) config/wscons: checking input device /dev/wsmouse
[ 3907.978] (II) LoadModule: "ws"
[ 3907.983] (II) Loading /usr/X11R6/lib/modules/input/ws_drv.so
[ 3907.985] (II) Module ws: vendor="X.Org Foundation"
[ 3907.985] compiled for 1.20.8, module version = 1.3.0
[ 3907.985] Module class: X.Org XInput Driver
[ 3907.985] ABI class: X.Org XInput driver, version 24.1
[ 3907.985] (II) Using input driver 'ws' for '/dev/wsmouse'
[ 3907.985] (**) /dev/wsmouse: always reports core events
[ 3907.986] (II) ws: /dev/wsmouse: debuglevel 0
[ 3907.986] (**) Option "Device" "/dev/wsmouse"
[ 3907.986] (**) ws: /dev/wsmouse: ZAxisMapping: buttons 4 and 5
[ 3907.986] (**) ws: /dev/wsmouse: WAxisMapping: buttons 6 and 7
[ 3907.986] (**) ws: /dev/wsmouse: associated screen: 0
[ 3907.987] (II) ws: /dev/wsmouse: minimum x position: 0
[ 3907.987] (II) ws: /dev/wsmouse: maximum x position: 1151
[ 3907.987] (II) ws: /dev/wsmouse: minimum y position: 0
[ 3907.988] (II) ws: /dev/wsmouse: maximum y position: 899
[ 3907.988] (==) ws: /dev/wsmouse: Buttons: 7
[ 3907.988] (**) ws: /dev/wsmouse: YAxisMapping: buttons 4 and 5
[ 3907.988] (II) XINPUT: Adding extended input device "/dev/wsmouse"
(type: MOUSE, id 7)
[ 3907.992] (**) /dev/wsmouse: (accel) keeping acceleration scheme 1
[ 3907.992] (**) /dev/wsmouse: (accel) acceleration profile 0
[ 3907.993] (**) /dev/wsmouse: (accel) acceleration factor: 2.000
[ 3907.993] (**) /dev/wsmouse: (accel) acceleration threshold: 4
[ 3908.018] (EE) Failed to open authorization file
"/root/.serverauth.68zMtvOjbh": Permission denied
[ 3918.136] (II) UnloadModule: "ws"
[ 3918.138] (II) UnloadModule: "kbd"
__________________________________________________________
attached file 3: dmesg output
__________________________________________________________
console is keyboard/display
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2020 OpenBSD. All rights reserved.
https://www.OpenBSD.org
OpenBSD 6.7 (GENERIC) #306: Thu May 7 18:19:56 MDT 2020
deraadt at sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC
real mem = 1073741824 (1024MB)
avail mem = 1038467072 (990MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root: Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz)
cpu0 at mainbus0: SUNW,UltraSPARC-IIi (rev 9.1) @ 440 MHz
cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 2048K external
(64 b/l)
psycho0 at mainbus0 addr 0xfffc4000: SUNW,sabre, impl 0, version 0, ign 7c0
psycho0: bus range 0-2, PCI bus 0
psycho0: dvma map c0000000-dfffffff
pci0 at psycho0
ppb0 at pci0 dev 1 function 1 "Sun Simba" rev 0x13
pci1 at ppb0 bus 1
ebus0 at pci1 dev 1 function 0 "Sun PCIO EBus2" rev 0x01
auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003,
72c000-72c003, 72f000-72f003
power0 at ebus0 addr 724000-724003 ivec 0x25
"SUNW,pll" at ebus0 addr 504000-504002 not configured
sab0 at ebus0 addr 400000-40007f ivec 0x2b: rev 3.2
sabtty0 at sab0 port 0
sabtty1 at sab0 port 1
comkbd0 at ebus0 addr 3083f8-3083ff ivec 0x29: layout 34
wskbd0 at comkbd0: console keyboard
comms0 at ebus0 addr 3062f8-3062ff ivec 0x2a
wsmouse0 at comms0 mux 0
lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 700000-70000f ivec 0x22:
polled
"fdthree" at ebus0 addr 3023f0-3023f7, 706000-70600f, 720000-720003 ivec
0x27 not configured
clock1 at ebus0 addr 0-1fff: mk48t59
"flashprom" at ebus0 addr 0-fffff not configured
audioce0 at ebus0 addr 200000-2000ff, 702000-70200f, 704000-70400f,
722000-722003 ivec 0x23 ivec 0x24: nvaddrs 0
audio0 at audioce0
hme0 at pci1 dev 1 function 1 "Sun HME" rev 0x01: ivec 0x7e1, address
08:00:20:c0:ff:ef
nsphy0 at hme0 phy 1: DP83840 10/100 PHY, rev. 1
machfb0 at pci1 dev 2 function 0 "ATI Mach64" rev 0x5c
machfb0: ATY,GT-C, 1152x900
wsdisplay0 at machfb0 mux 1
wsdisplay0: screen 0 added (std, sun emulation)
pciide0 at pci1 dev 3 function 0 "CMD Technology PCI0646" rev 0x03: DMA,
channel 0 configured to native-PCI, channel 1 configured to native-PCI
pciide0: using ivec 0x7e0 for native-PCI interrupt
wd0 at pciide0 channel 0 drive 0: <Maxtor 6Y080P0>
wd0: 16-sector PIO, LBA, 78167MB, 160086528 sectors
wd1 at pciide0 channel 0 drive 1: <WDC WD800JB-00JJC0>
wd1: 16-sector PIO, LBA, 76319MB, 156301488 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
wd1(pciide0:0:1): using PIO mode 4, DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: <ASUS, DRW-1608P3S, 1.06> removable
wd2 at pciide0 channel 1 drive 1: <WDC WD1600AAJB-00J3A0>
wd2: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
wd2(pciide0:1:1): using PIO mode 4, DMA mode 2
ppb1 at pci0 dev 1 function 0 "Sun Simba" rev 0x13
pci2 at ppb1 bus 2
creator0 at mainbus0 addr 0xfebee000: Elite3D, model SUNW,XXX-XXXX, dac 0,
1152x900
wsdisplay1 at creator0 mux 1: console (std, sun emulation), using wskbd0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
bootpath: /pci at 1f,0/pci at 1,1/ide at 3,0/disk at 0,0
root on wd0a (1f60d5c98cb9f231.a) swap on wd0b dump on wd0b
_____________________________________________________________
Hi Jules,
Still interested to find out about powering the Melcor SC-635?
I got one and succeeded to power it from 2.2 to 3.0V
There is a switching regulator on the PCB (AS1930 from Astec International) that generates negative voltages (as referred to the negative side of the battery: -12.4V , -4.8V , and -2.0V
At 2.4V, the current drain varies from 71mA (idle mode) to 185mA (all LED segments lit). For some strange reason, this current rises to 211mA when the C/CE key is pressed
I will design a substitute power supply based on a single Li-ion battery with step-down regulator to deliver 2.4V
Best regards
Francois
Something that I thought the folks here would appreciate: a fellow in Dubai is trying to keep a full-motion Boeing 737-300 sim (from 1991) running.
The main host machine is a Sun/3E, connected over Ethernet to the operator workstation which has 2 Sun/3Es each with a cgtwo powering a CRT touch screen. One of the Sun VME SCSI/Ethernet boards died, and he?s been unable to find a (working) replacement board.
There?s also a big rack of Concurrent hardware running OS/32, and some newer PCs for visuals and TCAS.
Plenty of pictures and a video tour of all the hardware at:
<https://www.reddit.com/r/BSD/comments/i8c8u7/how_do_i_emulate_a_sun_3e_comp… <https://www.reddit.com/r/BSD/comments/i8c8u7/how_do_i_emulate_a_sun_3e_comp…>>
Brendan
I currently have 3 Stride 420 boards in various state of repair, one presumably fully functional,? and would need an OS set for these.
Anyone have actual floppies or IMD images of either ucsd.p or Liason OS for these machines, or even just CP/M 68K ?
There are disk iimages under the header "Stride"? on the web and Bitsavers,? but these are actually for the previous generation machines ( Sage II and IV)
Jos
> From: Peter Van Peborgh
> From: Antonio Carlini
> From: Jim Stephens
Everyone: please DO NOT send messsages to CCTalk/CCTech with no Subject: line
in the header: that results in un-linked, and thus un-clickable, entries in
the archive (which some of, like me, use to read the list), e.g.:
http://www.classiccmp.org/pipermail/cctalk/2020-August/date.html
Thank you.
Noel
I'm getting back to trying to restore my MicroVax II.? Existing
controllers are ESDI and MFM, disks hard to find.
So I would like to convert a brand-new DQ703 I have to SQ706 so I can
mount SCSI disks.
I understand it is just? a prom change.
Does anybody have any info, or perhaps a PROM image?
cheers,
Nigel
--
Nigel Johnson, MSc., MIEEE, VE3ID/G4AJQ/VA3MCU
Amateur Radio, the origin of the open-source concept!
Skype: TILBURY2591 nw.johnson at ieee.org
Hi All,
I'm looking for the following parts to configure my TU56 for use with a
TD8-E:
G742 (Positive Logic Jumper Card)
M960 (TU56/TD8-E Command Cable Connector)
M961 (TU56/TD8-E Data Cable Connector)
7008447 cable
H716 PSU
I'm happy to buy or trade, if there's anything you're looking for feel
free to ask.
Regards,
-Tom
mosst at sdf.org
SDF Public Access UNIX System - https://sdf.org
Looking for someone in the LA area who knows how to properly pack and a few
ship vintage items to be mailed to me. A computer, monitor and parts.
The seller is not experienced in this and as a result the first thing that
I got from him (A Model 33 Teletype top) was trashed. I don't want the
stress of explaining or worrying about the next batch of stuff. So I turn
to you, the vintage computing community to help.
You get:
Teletype Model 35 that I am told is in very nice shape. I'd love to take
it myself but shipping is too expensive and difficult. The Pedestal is
branded SDS, as in the old Sigma S7 computer. Xerox bought them out and
sold the Sigma afterwards. That would date the Teletype in the late 60's
or so. This would be a nice museum piece. I am told the Model 35 is
practically unused.
I get
You pack and ship properly (you supply boxes and bubble wrap) a late 70's
business PC, display terminal, and a TTY Model 33 pedestal (I already have
the TTY itself). I anticipate the computer will be heavy and delicate and
will need to be partially disassembled to add a little padding to the
inside and to intelligently check out what you're dealing with. I am
experienced in shipping this kind of stuff, and if it was me, I would
expect it to take someone in LA area three or four hours to get the
materials at the store, box, disassemble/sure up, pack, go to the post
office, ship etc. I want it mailed USPS as I live in a rural area and
they're the best here.
This is the community, do I have a taker? If so contact me privately
through https://www.vintagecomputer.net/contact.cfm. My timeline is next
two weeks if possible.
Thanks
BIll Degnan
kennettclassic.comvintagecomputer.net
P.S. I will likely have a line to more cool stuff in LA area from this
guy. You might want to check out what else he has, that in and of itself
might make this venture worth it.
Many of you have seen this on ebay already:? item 224117176901
I'm on the east coast so it is out of my reach.
It appears to be a complete Data Translation data acquisition system
including the software!? Someone please rescue this!
Doug
Here's a photo of one of the restored PLATO terminals (which had the plasma display)
Does the power supply for the PLASMA look like the one in this photo of one of the terminals with the covers off?
----- Original Message -----
From: Aaron Woolfson
To: paulkoning at comcast.net ; uban at ubanproductions.com ; cctalk at classiccmp.org
Sent: Thursday, August 13, 2020 1:50 PM
Subject: Re: DEC VRE01 terminal documentation
Hi Tom.
Thanks for your message. Well, the Plasma panels use a pretty unique. I'm attaching the precise waveforms that the Plasma Panel expects to see in order to achieve the illumination of the dot. And while this may not be exactly or precisely what you're looking for, this will explain much about the technology involved. The fact that you can see any illumination at all is perhaps the most important part - beacuse the gas is probably there, and the "actuation" voltage might just not be high enough, or the sustainer voltage might have an issue.
The power supplies were manufactured by Electro Plasma and were typically separate from the actual unit itself. I am going to see whether I can find the schematics for those power supplies, which discuss the characteristics .
Also, check to see whether the back of the plasma panel itself has an edge connector that is similar to the attached TYCO specified connector. That might give you some insights into where to go.
When I gave all my equipment and test gear to the LCM up in Seattle, I am pretty sure that they also got a lot of the original manuals and notes that had been hand written. But I typically had scans of most everything. I will see what I can find....
----- Original Message -----
Subject: Re: DEC VRE01 terminal documentation
Date: Thu, 13 Aug 2020 16:38:39 -0400
From: Paul Koning <paulkoning at comcast.net>
You may want to see if the PLATO terminal documentation is any help, look on Bitsavers under University of Illinois. Those plasma display power supplies are hairy devices; the panel is actually a memory device and the power supply produces a high voltage AC waveform to make that work. Those panels normally light up around the rim; the fact you see that briefly but not sustained gives some hope that adjusting may be all that is needed.
That's quite a display; the usual plasma panels were 8 inches square, 512 by 512 pixels. I'm guessing this is a 1k by 1k pixel display, which I have seen once or twice, at SAI in San Diego in some military displays.
I know a plasma terminal expert; I've forwarded your message to him.
paul
> On Aug 13, 2020, at 3:23 PM, Tom Uban via cctalk <cctalk at classiccmp.org> wrote:
>
> I have a DEC VRE01 terminal that I bought NIB years ago. For those who don't know about this model,
> it has a flat plasma (orange/black) display of about 17". It worked when I bought it, but now, years
> later, I tried powering it up and the light comes on for a moment and goes out. I suspect a power
> supply issue, but bitsavers does not seem to have this one.
>
> Does anyone have schematic (or other) documentation for it?
>
> --tnx
> --tom
Hi All,
I'm going to be attempting to repair, both cosmetically and operationally, a
circuit board that had a strip of 12 volt trace "blown off" of it by a
short. The fiberglass is clean and there was no solder resist in the
affected area. I'm considering using 3M 1183 adhesive tinned foil tape for
the job. Has anyone else done this? Could you recommend this or another
product? Any tips?
Thanks,
Bill Sudbrink
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Greetings, everyone...
Does anybody know where I can source card edge connectors (with eyelets
or pins on the other side, hopefully) that would fit individual wings in
a Qbus board?
Carlos.
I found/scanned/OCR'd the "Technical data" flyer for HP-UX 7.0 (from 1989).
It's at: http://www.sieler.com/hp/other/hp_ux_7_0.html
Shortly after this, HP quietly dropped the "real time" portion of HP-UX,
and in later years no one at HP seemed to know it had ever been there.
Stan
?Tom,
Grant moved shortly after this Kit offering, over a decade ago.
That kit is OVER (Grant no longer offering).
Participate in the S100computers Group: http://www.s100computers.com/
Join the List at Google Group: S100Computers
https://groups.google.com
Grant special ordered the metal fabrication, at that time, from the original metal fabricators (Optima, $$), who have gone thru mergers & off-shoring.
Mike Douglas looked into that chassis possibility ? but was cost prohibitive (>$300).
Mike Douglas offers BOTH the Altair Clone (you referenced) AND
the Altair 8800c Kits (November 2018). This case he had fabricated is a close look-a-like, but Lighter in weight. Still the case alone is $300 .
This case does not have the internal Optima sub chassis (weight) and rails.
?https://deramp.com/altair_8800c.html
Suggest you look at Mike?s multiple vintage computer offerings (web site) AND
https://deramp.com/
His YouTube Videos (deramp5113). Here is the Altair 8800c, shown November 2018
https://youtu.be/Q5LjkL5b4n8
greg
w9gb
==
From: Tom Hunter <ccth6600 at gmail.com>
To: "General Discussion? <cctalk at classiccmp.org>
Subject: Altair 8800 reproduction
About 10 years ago Grant Stockly in Anchorage Alaska produced high quality
MITS Altair 8800 reproductions in kit form. The website still exists:
http://www.altairkit.com/
I have tried to contact Grant but did not get a reply. Does anyone know if
these kits are still available? Is Grant on this forum?
Alternatively is somebody else making complete Altair 8800 kits? I have
found people making individual boards but not a complete kit.
There is also the Altair 8800 clone which is based on a PIC microcontroller
emulating the entire original Altair 8800. It is cute but not the real thing.
Thanks
Tom Hunter
Sent from iPad Air
Sorry for duplicate emails. Paul did I send you copies of the power supply manuals?
One more photo of the power supply. I beleieve that the illumination activation needed to be 109-115 volts, and the sustainer needed to be 74-78 volts.
----- Original Message -----
From: Aaron Woolfson
To: Aaron Woolfson ; paulkoning at comcast.net ; uban at ubanproductions.com ; cctalk at classiccmp.org
Sent: Thursday, August 13, 2020 1:55 PM
Subject: Re: DEC VRE01 terminal documentation
I am crossing my fingers that I stil have the scans of these somewhere, or photocopies.... these are copies of the original manuals. DigiVue sent me their only originals, which I made copies of and sent back to them at some point....
I am crossing my fingers that I stil have the scans of these somewhere, or photocopies.... these are copies of the original manuals. DigiVue sent me their only originals, which I made copies of and sent back to them at some point....
----- Original Message -----
From: Aaron Woolfson
To: Aaron Woolfson ; paulkoning at comcast.net ; uban at ubanproductions.com ; cctalk at classiccmp.org
Sent: Thursday, August 13, 2020 1:53 PM
Subject: Re: DEC VRE01 terminal documentation
Here's a photo of one of the restored PLATO terminals (which had the plasma display)
Does the power supply for the PLASMA look like the one in this photo of one of the terminals with the covers off?
----- Original Message -----
From: Aaron Woolfson
To: paulkoning at comcast.net ; uban at ubanproductions.com ; cctalk at classiccmp.org
Sent: Thursday, August 13, 2020 1:50 PM
Subject: Re: DEC VRE01 terminal documentation
Hi Tom.
Thanks for your message. Well, the Plasma panels use a pretty unique. I'm attaching the precise waveforms that the Plasma Panel expects to see in order to achieve the illumination of the dot. And while this may not be exactly or precisely what you're looking for, this will explain much about the technology involved. The fact that you can see any illumination at all is perhaps the most important part - beacuse the gas is probably there, and the "actuation" voltage might just not be high enough, or the sustainer voltage might have an issue.
The power supplies were manufactured by Electro Plasma and were typically separate from the actual unit itself. I am going to see whether I can find the schematics for those power supplies, which discuss the characteristics .
Also, check to see whether the back of the plasma panel itself has an edge connector that is similar to the attached TYCO specified connector. That might give you some insights into where to go.
When I gave all my equipment and test gear to the LCM up in Seattle, I am pretty sure that they also got a lot of the original manuals and notes that had been hand written. But I typically had scans of most everything. I will see what I can find....
----- Original Message -----
Subject: Re: DEC VRE01 terminal documentation
Date: Thu, 13 Aug 2020 16:38:39 -0400
From: Paul Koning <paulkoning at comcast.net>
You may want to see if the PLATO terminal documentation is any help, look on Bitsavers under University of Illinois. Those plasma display power supplies are hairy devices; the panel is actually a memory device and the power supply produces a high voltage AC waveform to make that work. Those panels normally light up around the rim; the fact you see that briefly but not sustained gives some hope that adjusting may be all that is needed.
That's quite a display; the usual plasma panels were 8 inches square, 512 by 512 pixels. I'm guessing this is a 1k by 1k pixel display, which I have seen once or twice, at SAI in San Diego in some military displays.
I know a plasma terminal expert; I've forwarded your message to him.
paul
> On Aug 13, 2020, at 3:23 PM, Tom Uban via cctalk <cctalk at classiccmp.org> wrote:
>
> I have a DEC VRE01 terminal that I bought NIB years ago. For those who don't know about this model,
> it has a flat plasma (orange/black) display of about 17". It worked when I bought it, but now, years
> later, I tried powering it up and the light comes on for a moment and goes out. I suspect a power
> supply issue, but bitsavers does not seem to have this one.
>
> Does anyone have schematic (or other) documentation for it?
>
> --tnx
> --tom
Hi Tom.
Thanks for your message. Well, the Plasma panels use a pretty unique. I'm attaching the precise waveforms that the Plasma Panel expects to see in order to achieve the illumination of the dot. And while this may not be exactly or precisely what you're looking for, this will explain much about the technology involved. The fact that you can see any illumination at all is perhaps the most important part - beacuse the gas is probably there, and the "actuation" voltage might just not be high enough, or the sustainer voltage might have an issue.
The power supplies were manufactured by Electro Plasma and were typically separate from the actual unit itself. I am going to see whether I can find the schematics for those power supplies, which discuss the characteristics .
Also, check to see whether the back of the plasma panel itself has an edge connector that is similar to the attached TYCO specified connector. That might give you some insights into where to go.
When I gave all my equipment and test gear to the LCM up in Seattle, I am pretty sure that they also got a lot of the original manuals and notes that had been hand written. But I typically had scans of most everything. I will see what I can find....
----- Original Message -----
Subject: Re: DEC VRE01 terminal documentation
Date: Thu, 13 Aug 2020 16:38:39 -0400
From: Paul Koning <paulkoning at comcast.net>
You may want to see if the PLATO terminal documentation is any help, look on Bitsavers under University of Illinois. Those plasma display power supplies are hairy devices; the panel is actually a memory device and the power supply produces a high voltage AC waveform to make that work. Those panels normally light up around the rim; the fact you see that briefly but not sustained gives some hope that adjusting may be all that is needed.
That's quite a display; the usual plasma panels were 8 inches square, 512 by 512 pixels. I'm guessing this is a 1k by 1k pixel display, which I have seen once or twice, at SAI in San Diego in some military displays.
I know a plasma terminal expert; I've forwarded your message to him.
paul
> On Aug 13, 2020, at 3:23 PM, Tom Uban via cctalk <cctalk at classiccmp.org> wrote:
>
> I have a DEC VRE01 terminal that I bought NIB years ago. For those who don't know about this model,
> it has a flat plasma (orange/black) display of about 17". It worked when I bought it, but now, years
> later, I tried powering it up and the light comes on for a moment and goes out. I suspect a power
> supply issue, but bitsavers does not seem to have this one.
>
> Does anyone have schematic (or other) documentation for it?
>
> --tnx
> --tom
All ?
??????????????? I?m cleaning out my shop (I?m swimming in stuff so I will be creating a ?to go? list at some point), and this week I was going through boxes of magazine articles I saved. One is an article by Bob Meister that appeared in the July 1996 issue of Circuit Cellar with an LSI-11 simulator program. I was able to locate the C-source and get it to compile properly after some tweaking.
??????????????? The article says that he had to create a custom RT-11 driver for it, and it implies that it can use an image of an diskette, but it really doesn?t say what kind (assuming RX01).
I wanted to pose this to the group to see if anyone ever heard of this program, used it, or otherwise knows Bob (email address in the article is no longer valid) so I can try to fill in the blanks a bit.
Thanks!
Rich
--
Rich Cini
http://www.classiccmp.org/cinihttp://www.classiccmp.org/altair32