From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
06-04-2012 04:50 PM
Ok, here
06-05-2012 08:34 PM
06-06-2012 08:54 AM
I'm glad you posted this!
So I'm not the only one with the starenge addiction to writing emulators in LabVIEW.
Check out my Commodore C64 written in LV:
Christian
06-06-2012 09:55 AM - edited 06-06-2012 09:59 AM
I saw that but only after writing the Apple][ emulator. I wanted to keep it secret until the Apple]['s 35th anniversary but tst almost figured it out in reply #17 of this thread. I will take a look at how you did it later. I will also post the code for this in case someone wants to finish it.
There is no sound yet and that might be difficult. The way sound works on the Apple][ is that accessing a specific memory location toggles a flip-flop that is connected to the speaker. This means that timing is critical since tones are created in software timed loops. The emulator runs much faster than the 1MHz Apple][ and getting it to run at that exact frequency without crazy jitter is not really possible.
Also writing to virtual disks does not work yet. Did you ever emulate the Commodore disk drive?
Another thing that doesn't work yet is the expansion RAM. The Apple bank switches the upper memory between RAM and ROM to get 64K of RAM. Some software requires that such as Copy II Plus.
And graphics are not done yet. Only text mode works right now. It won't be too difficult to add that except for high resolution mode. The way they did color was kind of strange. The color of the pixels depends on the pixels around them.
I could make the 6502 go much faster. I tried to keep the number of cycles the same as a real 6502. There are a few indexed addressing modes and branches where the number of cycles can vary. If I just execute the whole opcode in one state then it should be about five times faster.
If I ever get around to doing a 68000 emulator I will definately do it that way. I want to emulate an original "Fat Mac" which ran at 10MHz and see if I can get LabVIEW 1.0 to run on it. Is it even possible to get a copy of LabVIEW 1.0 anymore?
06-06-2012 10:04 AM
Steve Chandler wrote: I want to emulate an original "Fat Mac" which ran at 10MHz and see if I can get LabVIEW 1.0 to run on it.
That's just a whole another level of reentrancy.
06-06-2012 10:12 AM
@crossrulz wrote:
Steve Chandler wrote: I want to emulate an original "Fat Mac" which ran at 10MHz and see if I can get LabVIEW 1.0 to run on it.That's just a whole another level of reentrancy.
Especially if I could get the emulator to run on LabVIEW 1.0
06-07-2012 04:07 PM
@crossrulz wrote:
Steve Chandler wrote: I want to emulate an original "Fat Mac" which ran at 10MHz and see if I can get LabVIEW 1.0 to run on it.That's just a whole another level of reentrancy.
Sortof like this: http://www.youtube.com/watch?v=xP5-iIeKXE8 (Life on Life).
06-27-2012 10:02 AM
@Ben wrote:
@Steve Chandler wrote:
You know... At the risk of sounding like the Magic 8-Ball I cannot say how ironic it is that this should come up in the Eureka thread.
I missed the irony. Can you give me a hint?
Ben
The hint is in G502.lvlib:Get Instruction Microcode.vi