Search results

I did replace the RAM board and got the same results. But of course this is only half of the ram.

I figured, unfortunately I don't have that kind of equipment.

Another update here.... I decided to play some "chip roulette" and start swapping out some logic ICs. Since I was getting parity errors I figured I would start with those. I replaced all the 74F280ANs, 9-bit parity IC. All I could find were 74F280BN, I assume these are compatible. I also...

Turns out I had my resistor arrays in backwards... doh! Working now that I reversed them all.

Have you tried formatting a disk in 1571 mode? (double sided). It's possible the top head is failing. I've had this happen on a number of 1571s.

Trying to figure out why my BlueSCSI is not working. (Not sure the version but it's an STM controller) Pentium 133 MoBo running Windows 98. Tried two different SCSI cards: Adaptec AHA-1510A(ISA) and AHA-2930 (PCI) The images are mounting ok according to the LOG file. The 2930 BIOS hangs...

Small update from my end.... I finally got around to installing a new (old) memory controller into my "bad" board. As suspected it has helped to stabilize the board but it still gives me the parity or opcode errors. I swapped RAM boards between my two cards with no success. (both boards test...

Awesome, nice work! So glad you got it going. I'm glad I found this thread, you've been an enormous help. I don't think I'd be as far along in my own troubleshooting with out it. I have a memory controller on route, but will be a couple of weeks yet. For comparison, here is my setup and...

That's great! Looking forward to the results.

Thanks! Well...one board appears to be working perfectly. I'm hoping the memory controller will help stabilize the other board to troubleshoot further. At this stage suspecting bad RAM. Would be an easy fix if that is the case.

Ah...got it...thanks. So I swapped memory controllers....did not fix it however errors were less erratic. Instead of the spamming the screen with Opcode messages I only received one and was able to continue. Then I got "A HARDWARE ERROR (PARITY CHECK) has occurred" First time seeing that...

NM, figured out how to remove that LCC socket, easier than PLCC! Yes, it gets very hot, so does the co-processer actually. Let me know where you're getting those memory controllers from. I see some on ebay.

Assuming that's the ic next to the CPU (left)? How do you remove those? same as the PLCC? Also, where are you buying those R8207-16? I picked up some 287s (now both my cards have a co-processor) and was going to grab a few 286 CPUs (on eBay) they are cheap enough with higher clock rates...

Here is the manual... Sorry some of the pages are skewed. My scanner is a pain, without having to manual scan every page this was the best version I could get before I gave up. I posted it to Archive.org. https://archive.org/details/orchid-pcturbo-286e-user-manual

Sorry for the delay...wanted to do some more testing to be sure, finally got around to it. So with the flakey board, it seems to only crash when I launch programs. Almost nothing seems to load completely, all with he same message about not being compatible...Opcode...etc.. The only program I...

One thing I've discovered, that illegal opcode message is a PCTurbo error message and not produced by DOS.

I understand what you are saying. For sure IO was mapped to 208h in this case. Does the mapping hold on a warm reset (CTRL+ALT+DEL)? Might explain a few things. It was definitely more consistent with the other board, as in the photo, the turbochk.com fails. But of course this could be...

Thanks! Sorry for the lengthy message but…. You started a rabbit hole of testing...lol... and frankly a hole of utter confusion. So, interestingly enough, I did not try the "bad board" using the default config. doh! Poor troubleshooting on my end. Since the "working" board seemed to function...

Just want to add to my previous message...a little more troubleshooting on my end... My working card, usually on the first boot (and a few subsequent) will restart the machine as soon as the DISK CACHE is executed. I wonder if this is just a bug, as I believe it uses all of the native RAM for...

yeah...I originally had DOS 4.01 installed...it would just hang every time. I was able to get it to launch with the original system disk (DOS 2.11) but I want it to load from hard disk and the HD support on that version is limited at best. I was able to get it going on DOS 3.3 (smaller...