00:00:00 --- log: started retro/08.07.22 01:13:48 --- quit: Raystm2 ("Should have paid the bill.") 02:26:54 --- quit: nighty^ (Read error: 104 (Connection reset by peer)) 02:31:15 http://www.apple.com/downloads/dashboard/developer/retroforth.html 02:39:48 --- join: Raystm2 (i=Ray@unaffiliated/raystm2) joined #retro 02:39:48 --- mode: ChanServ set +o Raystm2 08:21:13 --- quit: virl (Remote closed the connection) 13:13:22 --- join: virl (n=virl__@chello062178085149.1.12.vie.surfer.at) joined #retro 14:23:58 the dashboard widget is now listed on apple's site and dashboardwidgets.com 14:27:18 Hi crc. What's a Dashboardwidget? I go to find out. 14:37:12 http://en.wikipedia.org/wiki/Dashboard_(software) 14:42:07 I was just there. How neat. I'm not really that familure with things Apple. 14:42:09 it's my preferred way of running retro on the mac 14:42:13 Thats really neat. 14:42:20 Yes. 14:42:21 there are widget systems for Windows 14:42:33 I may support Yahoo's one soon 14:42:49 I guess it's much like the plug-ins for browsers. 14:43:00 Does Mac still use Hypercard? 14:43:02 and KDE4 is apparently planning to support dashboard widgets in the future 14:43:04 no 14:43:16 cool. 14:43:21 hypercard has been dead for years now 14:43:25 I see. 14:44:11 I only know about it at all because I was using Python's version, something with a name similar or actually -- Python-card Prototype. 14:44:58 It was a fairly easy to understand way of connecting your proggy to system resources, IIRC. 14:45:57 I trashed the 36" monitor. :( 14:46:38 Someone stuck a folding chair behind the couch where Raymond's phone charger was plugged in. 14:47:17 The chair pulled the plug out some and shorted the contacts and that blew out the high-voltage section of the monitor in another room. :( 14:47:44 :( 14:48:01 I 'loved' that thing. Even tho it was only 800x600, it was great for coding in bed. :) 14:49:27 Nan and I have re-arranged out tiny appartment. 14:49:42 We are using about a third of our bedroom for storage. 14:50:13 At the half point, I have two coffee tables along side of the bed. 14:51:20 I've got the Pentium4 and 2 pentium twos ( don't know why I always thought they were P1's) and room for the Pentium 1 and Pentium 3. 14:51:45 Now I need a Mac! :) 14:52:33 I ruined both p2 CDdrives by having a monitor across the top of both for 2-3 years now. :) 14:52:38 oops :) 14:52:45 oops :( 14:54:00 RE: the blog. specifically the noted-listing... 14:54:28 As the search for information goes on, I realize the mistakes I have made. 14:55:02 I think I need to come up with paragraph that states that it is a living document and in the nature of the blog... 14:55:27 I'm going to have to repeat information further in the posts and also add corrections to the comments. 14:56:18 Specifically I speak to opcode 66h. 14:56:38 I keep finding information that goes both ways about it's usage. 14:57:26 Randle Hyde of Art of Assembler fame states it's usage with a push opcode where 66h is changing 32bit code to 16. 14:58:09 The documents of Intel states that it can be used in both directions, dependant on the default usage of the opcode it's used with. 14:58:44 Chuck uses it to transfer the second stage boot loader over the first stage. 14:58:59 The opcode for this rep mov reads... 14:59:09 F3 66 A5. 14:59:13 F3 == rep 14:59:23 A5 == movsd 14:59:35 Being that D is for dword 14:59:56 66 is supposed to change that to word. 15:00:28 if that's true then only half the second stage gets loaded, and infact only up to and included this very command. 15:01:06 But I know that's not true because of a test that is accomplished to decide if this is a warm or cold boot. 15:02:19 I like doing this research. I feel like I'm actually learning something for once. 15:04:50 I got tired of mucking around in low-level issues 15:05:15 I'm not there yet. I've not mucked much. :) 15:06:12 I'm hopping to learn enough to answer some of the booting issues. All of which pertain to either floppy or in most cases display. 15:06:51 Also, I'd like to get to the point where I can disassemble the 2.0a. 15:07:22 I can read colorforth in a dump. That's not an issue. I could for many years now. But the assembler stuff is all new to me. 15:08:08 The listing is supposed to help me link back all of the words in an entire system to the lowest level code. 15:08:16 That is my current challenge. :) 15:09:16 * Raystm2 reading another tutorial on booting. 15:10:47 I've recently learned that on boot the number of the boot drive is in DL reg. Chuck doesn't seem to use that in any situation, prefering to use DMA to load the first stage. 15:11:30 And then CM abandons the DMA/Floppy driver and creates a new one in stage two. 15:12:51 Tathi has mentioned that CM abandons all of the color defs, recreating them in bytecoded source. 15:13:27 There may be a few refinements to the system that can come out of a well researched listing. 15:39:47 probably 15:53:48 okay. Now I know the 66h and 67h mechanisms. 15:56:03 Depending on the default size bit setting of the segment register, the Operand size prefix makes the current opcode it is used with as the oposite size to the default size bit. 16:17:05 --- quit: ChanServ (clarke.freenode.net irc.freenode.net) 16:17:30 --- join: ChanServ (ChanServ@services.) joined #retro 16:17:30 --- mode: irc.freenode.net set +o ChanServ 20:24:00 --- join: nighty^ (n=nighty@210.188.173.246) joined #retro 23:59:59 --- log: ended retro/08.07.22