Search results

@JDW Thanks for all your hard work testing!!!!! Soon I will produce versions 0.7a,b,c..... where I incrementally apply more changes to further isolate the problem. The reason for the mouse pointer problem is not immediately obvious to me. I will think further about this. Regading the CPU speed...

@techknight Glad to hear from you that everything is fine after the hurricane. Please take your time and don't feel pressured to do anything until you're ready. @JDW Hmm, too bad 0.6c/d didn't work for you. I'm wondering, is this a hardware issue? I will be getting new boards made soon with the...

@JDW Yeah, that's what I meant. Let me know if 0.6b has the issue and then I can start investigating each of the 0.6b changes in turn

@JDW now just to confirm, 0.6d never worked, but 0.6a does? Can you try 0.5b? That has the changes to the startup sequence, where the problem is likely occurring. If I can pinpoint the issue to be between 0.6a and 0.6b then I can look more carefully at what was changed and try to isolate the...

Damn, I was hoping for a more positive result. One thing I was thinking about is that I have the update program using the ASCII versions of all the Win32 APIs whereas you're on a Japanese-language machine. The error relating to the directory (and certainly the messed up text) may have to do with...

Okay!! I’ve got some new firmwares ready. There are four versions, 0.6a through 0.6d. I recommend trying 0.6d! If it works well then there’s no need to try any of the others. Here’s a description of the versions: 0.6a - basically the same as “old robust.” Sound isn’t great but everything else...

Voltage shouldn't matter too much. If the Mac works at 4.75 volts, the card probably will too. It's basically all CMOS. Anyway I've got this new board revision just about done: It has the ability to be powered from the USB port as I mentioned earlier. Also, I frequently worry about issues...

Hmm, like I said I will be rebasing my changes incrementally onto the "old robust" that seemed to work for everyone and developing versions 0.6a, 0.6b, 0.6c, 0.6d... which will add back the features incrementally to find what's wrong. I suspect the issue here relates to the new reset code but...

Hmm, I think I am going to re-base all of my changes onto the "old robust" since that build was quite stable. I will do this in the next few days and I will hopefully produce a series of firmware updates that will incrementally add my changes so we can see where things are breaking. In...

Hmm, let me know if reflashing the firmware helps. If not, maybe you can try reverting to an older version such as the “old robust” and see if that fixes anything.

@JDW Thanks!! I really appreciate your hard work testing. I'm glad it's working well, but one thing I'm unsure of is whether the sound is completely fixed. I have increased the I/O slowdown interval from around 35 microseconds to around 200 microseconds (0.2 milliseconds). That's responsible...

This firmware I just posted also has a refactor of the interface between the 25 MHz "slave port" and 8/16 MHz "master controller" of the fast bus-to-PDS bus interface. This was in the interest of reducing the size of the logic. The XC95144XL CPLD used on the WarpSE offers a fairly regular and...

@JDW Hmm, seems like clock-gated slowdown is not ready for prime time. I think that's causing the crash. At least on my setup, the crash is random. I power cycled my SE test bench a bunch of times and was eventually able to get the same 0000000F 00000002 error to happen after a number of tries...

Old one simply shouldn't be used for testing anymore. Maybe you can refer to it by date, but I am not inclined to come up with a versioning system at this time. We should never go back to the old firmware anyway since there have been a lot of changes under the hood. Just throw the old one away...

@JDW Interesting findings! Attached is a new firmware with SCSI slowed down. Are the mouse and boot issues fixed with this?

Oops!! Wait a sec--the firmware I just posted is not the actual latest version. Here's the correct latest revision with the changes I mentioned in the above post. Oh and one more thing. These recent firmware versions since I added "PDS-synchronized slowdown" require 4 MB of RAM in the Mac SE. I...

New firmware is attached! In this version, the slowdown takes effect for longer as I previously mentioned. SCSI is also not slowed down so let's try fast scsi again. @JDW @techknight @JTRetro @ppuskari @Crutch Can we find any issues with this firmware? Is the sound quality as good as stock...

Okay! I just got finished trying the slowdown method I described before with the clock gating. It’s much closer to stock speed! Stock: New slowdown always enabled: The current method makes it hard to fix that last 0.001 but it shouldn’t matter. I’ll tweak it a little more soon. However even...

Yessss and it would improve performance but it requires a much more complicated bus bridge between the fast and PDS buses. Right now, the WarpSE can only put out an address/data onto the PDS that the fast CPU is driving at that moment. The bridge can latch the address/data and save it for later...

I think the ultimate solution is gonna be to develop a slowdown function in the accelerator that exactly mimics the speed of the Mac SE. That will fix any and all speed-dependent problems, no matter the OS. The origin of the sound problem is that the CPU is too fast and writes to the whole...