On Fri, 3 Sep 2010, Jason Stevens wrote:
Well getting back to the start of the thread, what I've done here is
regressed the idle code to include an OLDVMS option which set the idle
timings and hook to the old pre 3.8-1 levels, allowing things like 4.2 BSD,
and other BSD's to idle
While discussing SIMH futures, Vince Mulhollon wrote:
I use a bash script that automates:
wget's some relevant papertape or whatever of diagnostic routine
runs a short expect script on simh pdp8 or whatever that executes the
diagnostic routine and saves the disk images etc.
md5sum the
Was this with or without the other vax idle patch (correcting interaction
with console and other background polling events) already applied?
Peter
No, I'll go ahead and try mixing all of them together
___
Simh mailing list
Was this with or without the other vax idle patch (correcting interaction
with console and other background polling events) already applied?
Peter
Great news, OSX is now idling at 15-20%.. It's certainly an improvement.
I'll up a patch that combines the regression (OLDVMS) and includes
On Fri, Sep 03, 2010 at 08:20:49AM -0400, Armistead, Jason wrote:
One potential problem would be accounting for any variation in the execution
behavior, e.g. if the time-of-day clock was read from the host or if network
interactions occur (assuming networking is enabled).
Yes sir, we can
In article 20100903113645.ga3...@mulhollon.com,
Vince Mulhollon vi...@mulhollon.com writes:
On Thu, Sep 02, 2010 at 02:00:34PM -0400, Jason Stevens wrote:
some kind of a 'test suite' to really verify that these emulators work
correctly.
My favorite solution over the years as the
In article 3d3fc9427c810d4c9ce9d722d942f0ae071ef...@uusmneg3.na.utcmail.com,
Armistead, Jason jason.armist...@otis.com writes:
One potential problem would be accounting for any variation in the
execution behavior, e.g. if the time-of-day clock was read from the host
or if network in
It seems to me that the low-level code that emulates the CPU would
be better served by unit tests for the individual instructions
that are emulated.
Even beyond that, the ability to boot and usefully use an OS and applications
on the emulated system (which combines I/O with instruction
In article b136ede3df5ec441b6f08e0a7ab872450ac9660...@ex2k7-cms-1.wmata.local,
Shoppa, Tim tsho...@wmata.com writes:
I do agree that someone who was into emulator writing for the fun
of software development, as opposed to the experimental industrial
archaeology of running old OS's and
This is exactly the sort of thing that unit tests are good at documenting.
The document is executable and therefore verifiable in its claims
about the underlying execution behavior.
The thought of an already existing generalized test language, that allows
documentation of minute details of the
In article b136ede3df5ec441b6f08e0a7ab872450ac9660...@ex2k7-cms-1.wmata.local,
Shoppa, Tim tsho...@wmata.com writes:
But I have to admit that I'm not familiar with a formalism that's
general enough to do all this and also auto-documents the emulated system.
It sounds like you're
11 matches
Mail list logo
