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 - fb39ca4
Pages: 1 ... 33 34 [35] 36 37 ... 126
511
« on: August 14, 2011, 02:22:48 pm »
You can also type this into command prompt:
telnet towel.blinkenlights.nl
It isn't the same version.
512
« on: August 14, 2011, 02:20:21 pm »
I downloaded it but never got around to installing it 
513
« on: August 14, 2011, 02:08:09 pm »
Good news, I fixed the crashing problems I was having. BMPtoC, which I used to convert sprites, for some reason put static in front of all the arrays it made, by removing that and replacing it with const, the game no longer crashes.
514
« on: August 14, 2011, 01:41:58 pm »
I suppose we could have a single function oc_cpu(bool), where true overclocks, while saving the original speed in a static variable, and false resets the cpu to its original state. Well, there's more than one overclocking clock frequency, so "bool" wouldn't do 
But I don't really see a need for a program to switch between more that two frequencies - 150mhz for maximum performance, and the default speed for otherwise.
515
« on: August 14, 2011, 01:38:20 pm »
Would it be possible to also have the choice of a prepaid credit card as a prize?
516
« on: August 14, 2011, 01:31:33 pm »
I just got that code from bwang's raycaster, I guess that was designed for os 1.1. I suppose we could have a single function oc_cpu(bool), where true overclocks, while saving the original speed in a static variable, and false resets the cpu to its original state.
Also, how about functions for accessing the timers (and RTC)?
517
« on: August 13, 2011, 11:41:09 pm »
What are some things you would like to see in the next version of ndless? I'm thinking more along the lines of functions and stuff, not major changes like a permanent installation.
Here's my first one:
void set_cpu_150_mhz() {
*(volatile unsigned*) 0x900B0000 = 0x00000002;
*(volatile unsigned*) 0x900B000C = 4;
}
void set_cpu_90_mhz() {
*(volatile unsigned*) 0x900B0000 = 0x00141002;
*(volatile unsigned*) 0x900B000C = 4;
}
518
« on: August 13, 2011, 11:33:00 pm »
Yes, DOOM is quite possible, and it will look a heck of a lot better on the prizm, compared to the nspire port. Remember, DOOM was written to run on 386 processors, which are around 33 mhz if I recall correctly.
519
« on: August 13, 2011, 11:08:44 pm »
I don't really see how that saves money, though. The dock connector contacts were just printed right on the circuit board anyways.
520
« on: August 13, 2011, 07:01:04 pm »
O.o That is really good.
521
« on: August 13, 2011, 06:57:52 pm »
You would use the commands in celtic to get the program names, and then use the menu function with the names converted into strings, and you have your menu.
Also, please do not double post, if you have something else to say, modify your latest post and add it in.
522
« on: August 13, 2011, 03:10:59 pm »
How will they get the lab station and wifi cradle to work now?
523
« on: August 13, 2011, 01:43:00 pm »
Lol nice!  I noticed you used the "toast" and not the "pop-tart" version of Nyan, though.
524
« on: August 13, 2011, 12:32:26 am »
We could simultaneously develop a z80 and a C version (for nspire, 68k, and casio (and possibly even HP if someone wants to port to that)), with the same features. I would be glad to help with the C version. (and the z80 version now that I am learning asm) Is this going to be in Axe or ASM?
525
« on: August 13, 2011, 12:23:40 am »
... and I'll be going with the iPhone 5 
Nnnnooooooooo!!! 
Almost everyone I've talked to that has an iPhone says that it's great at the beginning, but eventually it gets crappy. My best friend has had his less than a year and right now the vibrate button and function are kaputt, the screen is slightly unresponsive (enough to be annoying), and the calling quality has gone down since he got it.
It is the same with my ipod touch. The home button is unresponsive, sometimes I press it once and it registers as a double press, bringing up the app-switcher, other times I have to press it a few times to get it to register anything. When browsing the web, the whole thing often freezes up for a few seconds, and 50% of the time, the keyboard is laggy, I can type in a whole sentence and then a few seconds later, it will only then register the keypresses all at once. Not to mention it often gets very hot when playing 3D games (130F on the outside, over the cpu area.) I have to hold my hands away from that spot so I don't trap more heat in there. I have an Android -- a Samsung Captivate.
I'm pretty happy with it -- I've been stuffing all sorts of apps into it. Somebody actually made a metal-detecting app (and it actually (sort of) works).
How???
Pages: 1 ... 33 34 [35] 36 37 ... 126
|
Show Posts