This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - thepenguin77
Pages: 1 2 3 [4] 5 6 ... 108
46
« on: January 01, 2014, 04:51:24 pm »
Symbolic works perfect if you have Omnicalc, which is awesome by the way. So install Omnicalc and enable it in zStart. You don't need to do anything about Symbolic, just have the app on your calc. Problem solved. 
Little explanation : Omnicalc integrates Symbolic's functionality through its own parser hook without any chaining so you only need to enable Omnicalc to have both. Since zStart automatically sets up Omnicalc and chains to it during its init sequence, you basically have Symbolic natively.
Well, in my opinion, problem solved 
47
« on: December 30, 2013, 06:42:20 pm »
 I don't suppose there's any way to do that in axe?
No way to do what?
48
« on: December 29, 2013, 09:19:24 pm »
I used this example program to enable a key hook to password protect the memory menu. When I open zStart and click "Parser chain" from the program settigs menu it displays "Can't chain to zStart". Is this supposed to happen? I thought this was supposed to chain zStart's hooks to the ones already enabled.
"Can't chain to zStart" means that there is no parser hook currently in place. That tutorial deals with the rawkeyhook which is entirely different. If you're not using the parser hook, then this feature is of no use. (Currently there's no way to chain key hooks. However, zStart only uses the rawkeyHook. If you use the getCSC hook, there will be no interference.)
49
« on: December 23, 2013, 09:58:30 pm »
I have a suggestion: Add a hook that will make it so that if you do prgmPRGM (where prgmPRGM is Axe source) on the homescreen, it will compile the Axe source and run the binary if successful.
Good work, as always, thepenguin.
That actually makes a lot of sense. I'll probably do that. (Whenever the next update comes ) I found a bug today with the latest version (v1.3.013). My program now has ~35 labels and glitches when I use ON-VARS.
Congratulations, you found the first bug. That menu used to scroll, I don't know what happened.
50
« on: December 23, 2013, 09:50:23 pm »
So for PWM it will really be 36,000 writes to the link port per second? And if I am doing PWM at 18KHz, won't the noise from that be audible?
From my experience, 18KHz is about the minimum frequency you can use and not be able to hear it. If I moved my head around, I could hear doppler effects, but sitting still it sounded fine. I was 18 when I decided this, so take that as a reference because the younger you are, the higher the frequency you can hear. If you use 20KHz, you should be safe with all age groups. Edit: Also, what really sucks when you start doing sound is that you find out that not all calculators run at the same clock rate. Your range is basically 14.5MHz - 17.0MHz
51
« on: December 23, 2013, 09:45:10 pm »
Well, I thought about it, and I can basically sum up why I don't use libraries in two points: - I don't like to have dependencies (especially when the dependency is bigger than my program)
- I get a sense of pride from writing my own routines
It really all comes down to the fact that I want to be able to deliver a single file to people that will run all by itself. I'm ok with requiring a shell to run because almost all asm games do, but I don't want people to have to install a specific shell. Also, a reason people may not want to use the DCS GUI libs is because they want to remain 100% basic. I mean, if you're going to use DCS for your GUI, why stop there? Why not go full on and make a completely hybrid asm/basic game? I think it's the idea of not using any asm resources that keeps people away from the GUI.
52
« on: December 22, 2013, 07:35:45 pm »
I've explained this many times before. I don't remember where and I don't feel like finding it, but there's a really good explanation out there somewhere. Probably in either the trusound or truvid threads.
The basic idea is that you need to use pulse width modulation to approximate different voltages. You're going to be flipping the link port 18,000 times per second. This means you're going to send 18,000 groups of ON OFF. Now, the timing of your ON OFF determines the approximate voltage. 50% ON 50% OFF is of course the middle voltage. 0 100, 33 67, 67 33, 100 0 gets you 2 bits of output with 4 possible positions. The more voltages you have the better it's going to sound obviously. I think in trusound I used something like 250 steps.
To finally play your music, just run through the data and output the correctly timed ON and OFF pulses. The main downside to this is that depending on how you implement it, it takes 30%-100% of the cpu power just to play music.
53
« on: December 18, 2013, 08:07:30 pm »
You must not think of flash and RAM as two separate memories. Memory $0000-$7FFF is flash, and $8000-$FFFF is RAM.
To make a flash page available, just write its number to port 6 to put it in $4000-$7FFF, and port 5 to put it in $0000-$3FFF (a flash page is 16384 = $3FFF bytes).
When code of an app is executed, all addresses between $4000 and $7FFF refers to its own code (since it always takes one full page), so if you want to copy something in RAM, only a ldir instruction is enough.
Also, port (05) maps 0xC000 - 0xFFFF, not 0x0000 - 0x3FFF. For your purposes, just consider 0x0000 - 0x3FFF to always be page 0.
54
« on: December 18, 2013, 08:01:07 pm »
It just don't work with normal USB cables.
Yeah, zStart is not the only app to refuse to be sent through USB. I got that problem too with TI-Boy SE (which is a problem considering the size of the apps it produces ). This is why I asked if DieGoldeneEnte used USB or SilverLink, to see if USB is the problem or not.
What? How is that even possible? My only guess as to what would cause this is that the hooks are interfering with the transfer process. If you turn off the main "Install" flag in zStart it might send.
55
« on: November 19, 2013, 09:36:42 am »
Question: Is it true that ZStart and Doors CS7 no longer conflicts with each others? TheCoder1998 just said that on IRC, but I couldn't find any info about such update/fix. 
Kerm may have fixed DCS (I don't know). The way it used to work is that the first time you ran DCS, it would chain to zStart as it was supposed to. But the second time you ran DCS it would chain to itself rendering zStart (or any other program it was trying to chain to) out of the chain. You can chain to DCS from zStart, but I don't know how well that is actually going to work.
56
« on: November 14, 2013, 11:26:50 pm »
I can't really contribute at all to this list considering I haven't even seen a CSE in real life.
57
« on: November 14, 2013, 11:13:17 pm »
I'm just going to bug you about making an 84+CSE version of zStart, in case you haven't been bugged about it enough yet. It would be quite nice. If you wanted any assistance porting it or testing it, I would offer my help.
I'm probably never going to own a CSE, so someone besides me is going to have to do it. I'll answer any questions said person has along the way and even find the OS entry points, but I don't want to actually do the porting.
58
« on: November 14, 2013, 05:10:19 pm »
LOL you'd actually have to look with an hex editor for this one. 
Actually, you don't. Try opening an OS with notepad and you'll see what I mean. (.8xp files are binary though)
59
« on: November 14, 2013, 04:15:06 pm »
It was the signing, I believe.
It was indeed. For whatever reason, after TI signs the OS they add " -- CONVERT 2.6 --" at the very end. I forgot to do this.
60
« on: November 12, 2013, 03:54:01 pm »
Oh, alright. I guess I misunderstood. Your algorithm is a lot more complex than what I had originally realized. 
Pages: 1 2 3 [4] 5 6 ... 108
|
Show Posts