Previous Thread
Next Thread
Print Thread
Page 46 of 46 1 2 44 45 46
Re: Requirements? [Re: rfka01] #113159
04/18/18 09:29 PM
04/18/18 09:29 PM
Joined: Jan 2016
Posts: 28
B
bsdimp Offline
Member
bsdimp  Offline
Member
B
Joined: Jan 2016
Posts: 28
BTW, I've updated my Venix github thing with (a) a copy of all the VENIX manuals from bitkeeper's (thanks for the pointer). They cover both PRO and Rainbow version of VENIX! And they cover the missing system calls I'd worried about. and (b) I've started a write up for how to install on MAME.... It's still super incomplete. I need to rebuild MAME with the fixes to the boot roms, at the very least since it's not (yet) working...

Re: Requirements? [Re: Bavarese] #113160
04/19/18 01:34 AM
04/19/18 01:34 AM
Joined: Jan 2016
Posts: 28
B
bsdimp Offline
Member
bsdimp  Offline
Member
B
Joined: Jan 2016
Posts: 28
The latest git repo mame just built for me. And Venix boots for me now. Woot! However, shortly after it hangs while running fcheck... sometimes with Interrupts off message, other times it just hangs....

I've uploaded the image https://people.freebsd.org/~imp/venix-rd32.chd.xz if anybody wants to look at it.

mame64 rainbow -flop1 ~/mame/rb/flp/vbwsx1.img -hard1 ./venix-rd32.chd -nothrottle -frameskip 10

(both with and without the last args). Looking at the programs, they look good, as far as I can tell....

It seems like it's missing an interrupt, since the program hangs, and I can't ^C out of it, which is typical for a process in 'disk wait' and we'll never exit disk wait if we don't get an interrupt. Plus there's interrupt enable/disable issues. I'll have to find some time to look into that if someone doesn't beat me to it.

Last edited by bsdimp; 04/19/18 05:17 AM.
Re: Requirements? [Re: rfka01] #113161
04/19/18 12:41 PM
04/19/18 12:41 PM
Joined: Apr 2012
Posts: 180
Germany
B
Bavarese Offline
Senior Member
Bavarese  Offline
Senior Member
B
Joined: Apr 2012
Posts: 180
Germany
I 'copied a new boot loader' onto the CHD you uploaded - and the system started when i pressed 'W' in the Rainbow boot menu.

After that, things get odd. Observations:

- WUTIL 3.2 doesn't recognize the partition structure / and or identifier. It just shows GAP (for 'empty space').
Can't tell if Wutil was ever tested with BSW.

- MS-DOS 3.1 recognizes 'non MS-DOS partitions on the hard disk' at startup.

Sure the hard disk image has been correctly initialized?


A general problem is that older (DEC) tools are hard coded for 4 heads and a limited set of OEM hard disks, while newer tools rely on badly documented hd.structures (HOM, BOM, DPD, whatever).

I observed earlier that Wutil did not fill in the number of heads value when it should. It put in 0x00 and a divide by zero resulted - when later code tried to determine the cylinder #.


[Analysis of the Fschk crash] - - LOG

A quick look into 'error.log' reveals the last read is from sector number #15.

Sector numbers 1 to 12, then 10, 15, 15 are read (last one twice -> retry...?)

Code tries to write, but doesn't complete all of the necessary steps (set head, drive, sector in WD2010 controller) before 'fschk' runs into the woods.
The write isn't actually done.

I tested my hard disk code routines (hdc_write_sector, do_write() ) mainly on MS-DOS 3.x, so there can be access patterns i haven't covered (or race conditions).

'Interrupts off' (flickering in emulator) usually occurs after IRET (return from interrupt), when the stack is messed up.

You may turn on logging when you set 'log' to 1 in 'mess.ini'.

The ini file can be rebuilt with
>mess -showconfig > mess.ini

---- [EDIT]
@Bsdimp: what is the purpose of 'fcheck'?

@R.Belmont: may i ask if there is any news on the rewrite of WD2010...? smile

Last edited by Bavarese; 04/19/18 04:57 PM.
Re: Requirements? [Re: rfka01] #113173
04/21/18 02:31 AM
04/21/18 02:31 AM
Joined: Jan 2016
Posts: 28
B
bsdimp Offline
Member
bsdimp  Offline
Member
B
Joined: Jan 2016
Posts: 28
fcheck checks the filesystem to make sure that it's still self-consistent... It should just be reading all the meta-data from the filesystem, but not the data blocks...

Re: Requirements? [Re: rfka01] #113720
07/29/18 09:15 AM
07/29/18 09:15 AM
Joined: Apr 2012
Posts: 180
Germany
B
Bavarese Offline
Senior Member
Bavarese  Offline
Senior Member
B
Joined: Apr 2012
Posts: 180
Germany
I received several requests on how to set up Windows 1 on the Rainbow-100 B, so let me share some info.

First, it seems that DEC Windows for the Rainbow was never offically endorsed / released and the main SETUP is missing from all archives. The whole thing looks like a hard-wired, runtime version of Windows.

We haven't figured out how to connect a serial mouse (neither with 1.03 nor with the older version floating around). This is consistent with the Rainbow FAQ. There could be a dongle involved.


I believe it was on port #1 (not the crippled serial printer port) and hardware handshake is necessary (-> FDXB mode in SET UP).

The keyboard [cursor keys + Enter] may be used to move the mouse, but that's not really pleasant... smirk


Windows 1.03 -for DEC Rainbow- had the serial Microsoft Mouse hard coded in the main executable (the 2-button version).

The older Windows release 1.02 (or was it 1.01...?) had an unemulated, proprietary 'DEC serial mouse' built-in [basically a reprogrammed Logitech C-7 mouse].

Mouse drivers from older archives are PC-specific and thus useless (dissamblies show Windows *.DRV files poke PC - I/O ranges not valid on the Rainbow).



Here are some hints to get Windows working - somehow

You'll need a hard disk loaded with MS-DOS 3.1x from Suitable Solutions (think so) and the 7220 Color Graphics Expansion (i don't have), as well as >= 128 K RAM (more is better).
The 7220 Graphics Card can be enabled via DIP switches in emulation. You'll have to choose one of the 'side-by-side' configurations in 'video options' (so you'll see 2 screens, one for text, one for graphics).

1) Bsdimp put up a repository of a 'cleaned' version (version 1.03 minus useless *.DRV driver files):
https://github.com/bsdimp/rainbow100/tree/master/decwin

Decompress the files on a DEC hard disk to folder C:\WINDOWS. Hard disk must be enabled before boot.


2) start the game 'pacman.zip' (and quit / F10) ... before you start Windows 1. This is an unresolved initialization bug in our graphics card emulation
Link:
http://oldcomputers.dyndns.org/public/pub/mirror/os2site/sw/dec/rainbow/msdos/games/pacman.zip

Otherwise a blank screen appears with unresponsive controls.

AJR fixed the serial interface (in MAME/MESS >= 0.196) after my Windows experiments - so things might have improved (from an emulation perspective).

I tried to debug the case without success, so i'd be really happy if someone figures out what inhibits the first Windows start (see 2) or how to exactly set up a mouse.

[Bavarese]

P.S.: an updated introductory PDF (-> covers non-obvious steps like the complicated MS-DOS 3.x setup):
Dropbox link: First steps with the DEC Rainbow 100-B (April 2018 edition)
[April 2018 edition]

Windows 1.x + 2.x Apps
http://toastytech.com/guis/win1x2x.html

PC-centric history about Windows 1 (Premiere Edition)
https://winworldpc.com/product/windows-10/final

Last edited by Bavarese; 07/29/18 11:26 AM.
Page 46 of 46 1 2 44 45 46

Who's Online Now
0 registered members (), 82 guests, and 2 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,575
Posts112,038
Members4,812
Most Online225
May 26th, 2014
Powered by UBB.threads™ PHP Forum Software 7.6.1.1
(Release build 20180111)
Page Time: 0.038s Queries: 16 (0.022s) Memory: 5.6827 MB (Peak: 5.8671 MB) Zlib enabled. Server Time: 2018-09-24 01:37:48 UTC