headers
Apna-Loan | 9 Apr 2013 18:19
Picon
Favicon

Apply for loan <at> 2%...

Please Contact Us With This Email: apnapaisaloan.com12 <at> hotmail.com

Apna Paisa Loan Company , ? Are you in any financial mess or do you 

need a loan to start up your own business? at 2% rate? ; Email 

:apnapaisaloan.com12 <at> hotmail.com

(1) Full Names:
(2) State/Country:
(3)Amount needed as loan):
(4)Loan duration:
(5)Cell-Phone number:

Mr. Harsh Roongta
Permalink | Reply | 0 comments |
headers
Johnny Billquist | 4 Apr 2013 14:21
Picon

Building current

Trying to build current natively on a VAX today gives a whole bunch of 
errors of the form:

/usr/src/lib/libc/gen/getpass.c(189): warning: conversion of 'unsigned 
char' to 'int' is out of range [119]

Anyone else seen this? Is it local to VAX only, or something other 
platforms also see? I tried looking at the code, but my eyes rolled up 
almost immediately.

	Johnny

--

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt <at> softjar.se             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol
Permalink | Reply | 32 comments |
headers
Holm Tiffe | 30 Mar 2013 11:53
Picon
Favicon

ed to isntall NetBSD-6.1_RC2 on a VS3100 M38

HI,
I've got some Vaxstations lately and today I've tried to install
NetBSD-6.1_RC2 on a VS3100M38 with 24Mbytes of RAM.
Disk is an IBM DCAS 34330, 4Gbyte.

I can do what I want, the install.ram is crashing while labeling the disk,
regardless if I have overwritten the disk with zeros before ot not.

This is the last screen:

     Status: Command ended on signal
    Command: disklabel -w -r -f /tmp/disktab sd0 'DCAS-34330     '
     Hit enter to continue
--------------------------------------------------------------------------------
uid 0, pid 7, command disklabel, on /: file system full

/: write failed, file system is full
pid 7 (disklabel): user write of 9272 <at> 0x1a2000 at 67912 failed: 28

-----------

I had all kinds of similar errors in the tris before that, illegal
instrcutions and so on.

The disk is ok, OpenBSD is running fine on that beast and I'm unable to
install more RAM as the two boards that are currently in that machine to
get more than 24MB.

What is the right way to install NetBSD on such a M38?
(Continue reading)

Permalink | Reply | 22 comments |
headers
Johnny Billquist | 29 Mar 2013 04:50
Picon

Current on 86x0

Seems like the recent problems with device detection have been fixed, 
and a current build boots. This is nice.
So, here is how my simulated 8650 appears right now:

============

sim> boot rq/r5:8
Loading boot code from vmb.exe

 >> NetBSD/vax boot [1.11 Mon Apr 27 08:07:57 UTC 2009] <<
 >> Press any key to abort autoboot 5
nfs_open: must mount first.
open netbsd.vax: Device not configured
 > boot netbsd
2674084+172684 [212768+204148]=0x31cfc8
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
     2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013
     The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

NetBSD 6.99.18 (Puff) #5: Fri Mar 29 04:10:49 CET 2013
         root <at> GW.SoftJAR.SE:/usr/obj/sys/arch/vax/compile/Puff
VAX 8650
total memory = 65532 KB
avail memory = 59700 KB
mainbus0 (root)
cpu0 at mainbus0: KA865, S/N 1234, Rev. G, manufactured in simh.
cpu0: no FPA
cpu0: Physical memory layout:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mouse | 25 Mar 2013 00:53

Userland emulator

I've been playing with a VAX emulator I built.  The desire was to do a
build of the VAX world for my 1.4T tree, which is well before
cross-build support went in (even before the switch to ELF), on non-VAX
hardware.  I'm mentioning it here in case anyone else would find it
useful, either as-is or as a starting point.

Unlike emulators like simh, this one draws the simulator/simulated
boundary at the userland/kernel divide.  It emulates things userland
does; when userland does a syscall, it implements the syscall itself
rather than emulating a VAX implementation of the syscall.  (Loosely
put, you could call it WINE for 1.4T NetBSD/vax, though AIUI WINE
pushes the emulator/emulated divide even farther out, to the
library-routine API level.)

It has some issues, perhaps most notably that there's a lot of
protection stuff it doesn't implement - it basically assumes all
userland processes are running as root.  But that was enough for my
purposes.  There are also a bunch of userland-usable instructions it
doesn't implement, because nothing I've tried to run has used them; my
strategy has been to run stuff until the emulator reports something
unimplemented, at which point I then implement it and rerun.  It is
also known to have subtle issues with signal delivery; set -o emacs in
sh doesn't work as a result - sh is relatively demanding of SEGV.

There are doubtless lots of other issues (most of which I'm not aware
of, of course).

It's designed to have a statically-linked executable of the emulator
dropped into an otherwise-VAX tree, then run with something like
"chroot $VAX_ROOT /vax-emulator /bin/sh".  It has extensive tracing
(Continue reading)

Permalink | Reply | 16 comments |
headers
Holm Tiffe | 23 Mar 2013 00:06
Picon
Favicon

Re: VS3100 M76 Memory Question

Jan-Benedict Glaw wrote:

> On Fri, 2013-03-22 19:25:24 +0100, Holm Tiffe <holm <at> freibergnet.de> wrote:
> > I'm currently have 16MB of Memory in the VS3100 M76, that are
> > some big double sided Modules, have four of them.
> > I can't look what kind it is, the machine is currently reformatting the
> > Disk..
> > 
> > In a antistatic bag I've got 8 pcs  additionally:
> > 
> > * 54-19145-AU * *A01* * AY33801071 *
> > 
> > "4 MEG MEM" is etched in the boards, a DIGITAL Logo and 5019144-01 also.
> > 
> > Should they work in the M76?
> > I've tested them, two of them seemed to work flawlessly, more is making all
> > kind of trouble, eg. Test repeating until "B" and than reboot loop at startup.
> > 
> > What is this for Memory? I don't think that they are all bad ...
> 
> I don't know if these modules are expected to work in the m76, but
> this, first of all, looks like a speed/timing issue. Please have a
> look at the memory ICs used on your (already-installed) memory modules
> and compare their speed with those of the new modules.
> 
> As a hint: http://www.schach-computer.info/wiki/images/f/ff/RAM.jpg
> 
> The "-70" indicated 70ns RAM. Though the '0' is omitted quite often.
> 
> MfG, JBG
(Continue reading)

Permalink | Reply | 0 comments |
headers
Holm Tiffe | 22 Mar 2013 19:25
Picon
Favicon

VS3100 M76 Memory Question

I'm currently have 16MB of Memory in the VS3100 M76, that are
some big double sided Modules, have four of them.
I can't look what kind it is, the machine is currently reformatting the
Disk..

In a antistatic bag I've got 8 pcs  additionally:

* 54-19145-AU * *A01* * AY33801071 *

"4 MEG MEM" is etched in the boards, a DIGITAL Logo and 5019144-01 also.

Should they work in the M76?
I've tested them, two of them seemed to work flawlessly, more is making all
kind of trouble, eg. Test repeating until "B" and than reboot loop at startup.

What is this for Memory? I don't think that they are all bad ...

Regards,
Holm
--

-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
  www.tsht.de, info <at> tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741
Permalink | Reply | 0 comments |
headers
Johnny Billquist | 21 Mar 2013 21:45
Picon

installboot is broken

I just went through some fiddling around with simh, since it recently 
started implementing 86x0 emulation.
Of course I wanted to test all my code that I've done for NetBSD on this 
simulation, to see what happens,

I failed. And the reason is that installboot is broken. installboot does 
not use the data from the primary boot block that it is given, for data 
in block 0. Instead installboot creates its own block 0 content. This 
works on the MicroVAXen, because of how VMB on those machine work. It 
does not work an older VAXen, because VMB acts in a different way.
Block 0 of the primary bootstrap is correct, but block 0 as done by 
installboot is not.
In the past, disklabel was used to write the boot block, and disklabel 
didn't try to be clever. We need to go back to this solution again.

Does anyone feel like fixing, or should I go and try figuring out 
exactly which parts of block 0 to pick from disk and from primary 
bootstrap to merge, to actually get a correct block 0?

	Johnny
Permalink | Reply | 63 comments |
headers
Holm Tiffe | 21 Mar 2013 20:10
Picon
Favicon

VS3100 M76

Hi,
I've got some VS3100s, 2 M38 and one M76.
Today I've cleaned the M76, put a new battey on the DS1287A, the internal
was empty, and tried to netboot NetBSD6.
I think I boot the generic kernel (don't know this exactly for now because
of the experiments with this rtVAX in the past, but I've renamed a kernel
namend netbsd.vax.generic to netbsd.vax on my disk).
I get this:

>>> b esa0

-ESA0
>> NetBSD/vax boot [Jan  6 2002 22:13:30] <<
>> Press any key to abort autoboot 0
Trying BOOTP
Using IP address: 192.168.50.22
myip: vs3176 (192.168.50.22)
root addr=192.168.50.50 path=/data/home/exports/rtvax
2587200+174320 [244+211280+200960stray interrupt: vector 0x28, ipl 31
stray interrupt: vector 0x28, ipl 31
stray interrupt: vector 0x28, ipl 31
stray interrupt: vector 0x28, ipl 31
stray interrupt: vector 0x28, ipl 31

...what's this?

>>> test 50

KA43-A  V1.2          
ID 08-00-2B-23-C2-5A
(Continue reading)

Permalink | Reply | 2 comments |
headers
info | 19 Mar 2013 04:53
Picon

congratulations

Open The Attachment and read.
Attachment (s.docx): application/octet-stream, 11 KiB
Permalink | Reply | 0 comments |
headers
romanis | 7 Mar 2013 11:00
Picon
Picon

VaxStation 2000 and MFM Drive

Hello,

i've got hands on a VaxStation 2000, with 14 MB RAM, but without monitor or harddrive. Fortunately i have an
old 20 MB RLL Harddrive, which i could format with the ROM Test 70 command. (It has 782 cyl, 2 heads, and as a
MFM drive 17 sec/track - 12 MB formatted). I can see the drive from an netbooted NetBSD, make an
installboot, copy the kernel, etc. But i cannot bootstrap from it. I would like to bootstrap from MFM and
then use a bigger SCSI harddrive to hold the root-filesystem, etc.

KA410-B V2.3

F_..E...D...C...B...A...9...8...7...6...5...4_..3_..2_..1...

 ?  E  0040  0000.0005
 ?  C  0080  0000.4001
 ?  6  00A0  0000.4001

 83 BOOT SYS
?02 EXT HLT
    PC = 000014C2
>>> boot dua0

-DUA0

%VMB-F-ERR, PC = 00000765
%VMB-I-STS, R0 = 000008C2
 84 FAIL
>>>

Are there known compatibility issues with non-dec MFM drives and booting? 
maybe i did an error in specifing the disk as an RD51?
(Continue reading)

Permalink | Reply | 1 comment |

Gmane