Jump to content

Lorin Millsap

Members
  • Posts

    195
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by Lorin Millsap

  1. This probably belongs in the feature request. What you are trying to do should work on real hardware, but I don’t believe the emulator supports keyboard or mouse commands. Sent from my iPhone using Tapatalk
  2. So question. Not against people learning, but why are you attempting to clone a product we haven’t released yet? Sent from my iPhone using Tapatalk
  3. Kevin’s video is the one. There was no announce until the board with the changes was actually working. Sent from my iPhone using Tapatalk
  4. Well to clarify on that, the emulator hasn’t been updated because Micheal hasn’t received an updated board yet. However official announcements to the real hardware have been announced and that is the relevant and current data. Yes the emulator does need to be updated but it’s not getting updated till the person writing the emulator has the real hardware and can make sure that the emulator and real hardware behave the same. Much of this has very much been affected by the global circumstances. We would like to be moving much more quickly but sometimes we have to wait for updated components. Sent from my iPhone using Tapatalk
  5. You are basing that on obsolete information. The X16 uses addresses $00 and $01 for banking control freeing up the VIA for better uses. Sent from my iPhone using Tapatalk
  6. In theory sometimes you can but if you are thinking it’s faster you are very mistaken. Our logic on the x16 has propagation delays under 10ns. An EEPROM is going to be in the 50-150ns range depending on the speed. On your logic chip choices, understand at the speed and timing we are running at you need stuff much faster than the LS and HC series. Also trace routing, proper power delivery, ringing, etc are all factors that will hurt your project. Sent from my iPhone using Tapatalk
  7. This has already been brought up, and the technical reasons why it can’t be done have been throughly broken down. This isn’t going to happen and the design is set. Sent from my iPhone using Tapatalk
  8. Ok, this is a violation and we are going to have to remove it for several reasons. The first is that the KERNAL and BASIC are proprietary code and as such any software that contains that proprietary code in whole or part is not allowed. Secondly, must such software should leave the ROMs untouched and instead load from the SD card. You don't add custom software to most BIOS systems and likewise you shouldn't indiscriminately add code to the OS ROM unless it provides real world functionality without breaking compatibility. As a whole we are not interested in micromanaging what users can and cannot do, so long as it doesn't introduce legal or ethical issues. We simply cannot allow users to distribute or alter the code we are licensing from Cloanto or Microsoft or any other entities. Before you include any code in your projects make sure you check and understand the license agreement to see what you are or are not permitted to do. Never assume that something is open source unless explicitly stated. Making custom ROMs as a rule is allowed. So long as it doesn't violate any license agreements. However some custom ROMs may overall be harmful to the community if they break compatibility, or if they risk hardlocking the physical system.
  9. We are not releasing schematics until after product release. Sent from my iPhone using Tapatalk
  10. Well I’m not opposed to having it in ROM and to a large part I agree with certain parts of the program. It relying on the KERNAL under the conditions that it doesn’t create redundant code. For example the screen draw routines may as well be the KERNAL ones and if you are testing the IEC bus you might as well be using the integrated routines to do so. Likewise if you are reading the PS/2 keyboard or mouse the KERNAL routines should be used. If you are testing certain things in a way that differs from the normal methods then you would write your own routines. Sent from my iPhone using Tapatalk
  11. There is not and we would very much welcome one. Sent from my iPhone using Tapatalk
  12. If the Pi has 5v tolerant IO it will work directly. If they are 3.3v only then you will need to use transceivers to shift the voltage. Sent from my iPhone using Tapatalk
  13. Ok. I guess I did misunderstand the question. Sorry if I confused or mislead. Sent from my iPhone using Tapatalk
  14. You can add any custom layout via the SD card. Sent from my iPhone using Tapatalk
  15. I don’t know if Frank has seen this or not but in the conversations about why the specific one was choosen, a couple big items. It was chosen because it is low cost with a large amount of RAM in it. If you look at most FPGAs that have large RAM they are almost always big expensive FPGAs. In the same product line there was another FPGA that had double the RAM but it was way more costly and was a BGA chip which would require outside manufacturing to assemble. This is bad for low volume test modules which are needed to even develop the system and none of us have the capability to handle those in house. Needless to say the VERA we have designed now is what we are sticking with. Limitations and all. It is for programmers to work with the systems limitations and either adjust the design to fit, or figure out clever tricks to work around them. Sent from my iPhone using Tapatalk
  16. That’s not really possible as that’s not how the vERA works. Sent from my iPhone using Tapatalk
  17. Yuck. There are reasons laptop form factor won out because it accomplishes those goals more elegantly. But that’s not part of our project goals. Sent from my iPhone using Tapatalk
  18. I’m gonna so no it’s not useful or attractive. The team is not seriously considering that route. Especially as it does not reduce the footprint. Necessity is the mother of invention. Here there is no necessity to reduce the height. Sent from my iPhone using Tapatalk
  19. The case is already less high. Sent from my iPhone using Tapatalk
  20. Splitting the options especially during startup is expensive. Even if a smaller case was used it does nothing unless the board is smaller too. So now you are talking two versions of the board. Making more variations is always more expensive as a whole. Sent from my iPhone using Tapatalk
  21. Your screen handles that. Sent from my iPhone using Tapatalk
  22. Why would you need a CRT? Any LCD with a VGA input will work. No need to overcomplicate it. Sent from my iPhone using Tapatalk
  23. Almost all modern displays even if they don’t state so, do support 640x480. It’s not hindsight. A lot of thought was put into that. Sent from my iPhone using Tapatalk
  24. That’s because there isn’t enough VRAM to do 640x480 in 256 color mode. The only way you could do it in 640x480 is to do it in text mode which is debatable that is even a GUI. Or to reduce the color depth. Sent from my iPhone using Tapatalk
  25. We already have GEOS. It’s not fully working because priorities. But it is there. The draw routines we have in ROM are very fast Sent from my iPhone using Tapatalk
×
×
  • Create New...

Important Information

Please review our Terms of Use