Recent content by iigs123

Take a look at the back. I believe this one is the heavy one: https://computers.popcorn.cx/apple/peripherals/printers/imagewriter-ii/imagewriter-ii-02.jpg I have the revised model and the power/serial plugs into the area where the paper is fed into the printer.

Darn. I have a purple VRAM or two as well, they are quite well made. The only other immediate thing I can think of is to clean the sockets well with deoxit or something.

are you able to set colors > 256? Perhaps tattletech is only reporting _current_ settings, not available or something.

Monochrome and color terms are basically the same speed on the LCII. Maybe the blinking cursor is causing more screen updates? I don't see an option to disable the blink.

I tried running this on an LCII - the terminal window flickers every second or so, and typing is very slow as well. It appears to be redrawing the window contents every second instead of waiting for changes. This was on System 7.1. Still, interesting progress being made.

Without SIMMs, onboard VRAM alone, the test is OK. With SIMMS: Video RAM Failure at address $F9080200! Failed data pattern = $FF0000!

i'll have to rerun it to get the error. I'm pretty certain its related to the SIMMs however since the onboard ram seems to be fine. I should probably rerun the VRAM test with no SIMMs to confirm. As far as I know the only source of the Antelope CLUT and djMEMC are other donor apple machines...

I forgot to add that I ran MacTest and it failed on the VRAM check, as I thought it would. I doubt I'll get a better logic analyzer to read the busses. The one I have is compatible with 5v logic. Really I was just trying to confirm that some signal was on the data lines instead of all low or...

Thanks again to everyone who supported me with repairing my Quadra 610 a while back. I'm back at this issue- screen issues when running in thousands of colors. The bottom half of the screen is corrupted. This 256 colors at any resolution works fine. Only using the onboard VRAM works fine. Here...

You can save the ROM banks to files using the built in monitor. Based on my notes I think this dumps the rom of the card in slot 7, first bank 0 as a file ROM0: call-151 lda #0 CFFF C700 # read slot 7 should activate it C0FA:0 1000<CC00.CFFFM # copy 1024bytes rom to loc 100 BSAVE...

I suspect a slightly different ROM too. The patched driver might not work 100% either. GSOS uses its own, faster driver instead of relying on the ROM code. I think the card generally works OK on the IIE even with some minor rom differences. I would give GGLabs some additional time. He is a...

Take a look: https://github.com/gorlik/a2scsi-rom I'm curious if the A2SCSI ROM is in fact slightly different and the drivers - perhaps even the patched one - don't detect the card. It would work fine in Prodos since there is no driver.

You can use Ciderpress - https://ciderpress2.com/ - to edit the disk images. This sounds like my experience with the A2SCSI & BlueSCSI. My memory might be fuzzy but I recall being able to use multiple images and/or partitions despite the driver error. I do recall it just didn't seem 'right'...

Also, is your BlueSCSI firmware up to date?

I used the A2SCSI card with my ROM3 a while back. Is the card in slot 7, and is it set to "your card" in the control panel? Your partitions must be 32MB to use in GSOS or ProDOS. I was able to boot and use a BlueSCSI with the card, however GSOS 6.0.4 always complained about SCSI drivers during...