Re[2]: [MSX] IDE-CF: No enough memory
And, by the way, IDE CF won't work in your MSX2+, because it needs 128 KB RAM at least in order to work properly (due to MSXDOS2, that needs 128 KB). It works fine in my MSX2+ :) But I think it's because I upgraded internal memory to 512K :) Hey Eduardo, if I'll go visit Spain, I will upgrade your MSX2+ while you wait :) ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Hi Laurens, But, Javi, isn't the CF-IDE just extremely cool??? ^_^ Yep, that's exactly why I bought it. :) Really, I still love it :) small, silent, no external power supply... You tell me about that... This is how my MSX looked like when I was still living in Spain. Notice the mess behind the computer: http://www.ag0ny.com/misc/terminal-linux-msx.jpg Now there's just the IDE-CF cartridge, *WITH A SMALLER CARTRIDGE INSERTED INTO IT* (the CF memory card). What could be more MSX-like? ;) Regards, -- Javi Lavandeira - http://www.ag0ny.com ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
This is mine, still a lot of stuff around it, even with that CF-IDE. What I want now is Internet with it. (should work, if I know how-to) with an external modem on the IDE-RS232, but I rather want to use my cable-internet like I do with that PC next to the MSX. (Ethernet connection) http://home.planet.nl/~hapzee/My_MSX.htm Greetz, Hapzee - Original Message - From: Javi Lavandeira [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, August 28, 2004 9:14 AM Subject: Re: [MSX] IDE-CF: No enough memory Hi Laurens, But, Javi, isn't the CF-IDE just extremely cool??? ^_^ Yep, that's exactly why I bought it. :) Really, I still love it :) small, silent, no external power supply... You tell me about that... This is how my MSX looked like when I was still living in Spain. Notice the mess behind the computer: http://www.ag0ny.com/misc/terminal-linux-msx.jpg Now there's just the IDE-CF cartridge, *WITH A SMALLER CARTRIDGE INSERTED INTO IT* (the CF memory card). What could be more MSX-like? ;) Regards, -- Javi Lavandeira - http://www.ag0ny.com ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Javi Lavandeira wrote: You tell me about that... This is how my MSX looked like when I was still living in Spain. Notice the mess behind the computer: http://www.ag0ny.com/misc/terminal-linux-msx.jpg Heh, yeah, that looks familiar. Not only the mess behind the MSX by the way, but also the small cabinet-thing on the right. Seems they have IKEA in Spain as well ;p. Now there's just the IDE-CF cartridge, *WITH A SMALLER CARTRIDGE INSERTED INTO IT* (the CF memory card). What could be more MSX-like? ;) ^_^ Hapzee: what you could also do is connect your MSX to your PC via RS232, and let the latter act as a server (bridge is the proper word, I think). Then you can use your broadband connection. I did it already with Uzix some time ago. Been chatting on IRC with Zica on my MSX (it was a bit slow though -_-;; probably because everything in Uzix is C). ~Grauw -- Ushiko-san! Kimi wa doushite, Ushiko-san!! ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
RE: [MSX] IDE-CF: No enough memory
Hapzee: what you could also do is connect your MSX to your PC via RS232, and let the latter act as a server (bridge is the proper word, I think). Then you can use your broadband connection. I did it already with Uzix some time ago. Been chatting on IRC with Zica on my MSX (it was a bit slow though -_-;; probably because everything in Uzix is C). Yeah, I already did that. I did it successfully with Linux and Windows NT 5.x. By the way, it wasn't slow at all, at least in R800 mode :P ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Yes, but some CF cards give a lot of problems. I am using 16 MB CFs, and they are the best for my needs. I had some strange errors with other cards too! If it is bigger than 32 MB you should create partitions, so you will have to boot from floppy. And, by the way, IDE CF won't work in your MSX2+, because it needs 128 KB RAM at least in order to work properly (due to MSXDOS2, that needs 128 KB). Regards, Edward Robsy From: Maico Arts [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [MSX] IDE-CF: No enough memory Date: Fri, 27 Aug 2004 07:37:31 +0200 If memory serves well, you should press DEL or some key to bypass CF bootup and boot normally from diskette. With the fdisk you should do the partitioning and then all should work normally. Greetings Maico Arts MSX-NBNO - Original Message - From: Javi Lavandeira [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 27, 2004 3:42 AM Subject: [MSX] IDE-CF: No enough memory Hi all, I received today my IDE-CF, but I'm having some trouble with it. The problem is that if I boot the computer with a memory card in the master slot, the computer always hangs with the following error: No enough memory. These are the things I've found out: - Booting the MSX without a memory card inserted, the interface's BIOS says that it cannot find a master device and the computer boots normally. - Booting with a memory card in the master slot, I get the No enough memory error message in a FS-A1ST (expanded to 512Kb) and a FS-A1GT. I've tried also an FS-A1WX (64Kb) and I don't get the error message, but the floppy disk in this computer is broken, so I couldn't do more testing. - Flashing the BIOS works correctly when I boot the computer without a memory card. - The No enough memory error appears regardless of the slot where the cartridge is inserted. My hardware is: - Panasonic FS-A1ST (512Kb)/A1GT/A1WX - CF ATA-IDE, BIOS 2.21 - 128Mb CF card (detected as TOSHIBA THNCF128MA at boot) - Nothing else connected to the computer Any ideas on what can be causing the problem? Regards, PS: I posted this same message on Sunrise's forum too. -- Javi Lavandeira - http://www.ag0ny.com ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx -- This message was sent with an unlicensed evaluation version of Novell NetMail. Please see http://www.netmail.com/ for details. -- This message was sent with an unlicensed evaluation version of Novell NetMail. Please see http://www.netmail.com/ for details. ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx _ Reparaciones, servicios a domicilio, empresas, profesionales... Todo en la guía telefónica de QDQ. http://qdq.msn.es/msn.cfm ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Eduardo Robsy Petrus wrote: Yes, but some CF cards give a lot of problems. I am using 16 MB CFs, and they are the best for my needs. I had some strange errors with other cards too! If it is bigger than 32 MB you should create partitions, so you will have to boot from floppy. Have you tried another brand CF cart? Sunrise advises against using CF carts 32MB because the chance for incompatibilities is much bigger for those. However I can imagine some (cheap-ass ;)) CF carts could still give trouble. If that doesn't work either though I'm rather starting to think along the lines of the CF-IDE being broken. Oh, and PS, you'd need to initialize the damn thing indeed (floppy drive necessary). If you don't, it might very well execute some random uninitialized code causing the error to appear? Initializing can be done on your MSX2+, because you don't need DOS2 for that (keep DEL pressed to skip loading DOS2, keep INS pressed to skip loading the IDE-BIOS entirely). ~Grauw -- Ushiko-san! Kimi wa doushite, Ushiko-san!! ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Hello, Have you tried another brand CF cart? Sunrise advises against using CF carts 32MB because the chance for incompatibilities is much bigger for those. However I can imagine some (cheap-ass ;)) CF carts could still give trouble. If that doesn't work either though I'm rather starting to think along the lines of the CF-IDE being broken. My test showed me that a 16mb lexar CF card did not work when it was the only installed cf card. When using this card as a second card, it worked like a charm. Oh, and PS, you'd need to initialize the damn thing indeed (floppy drive necessary). If you don't, it might very well execute some random uninitialized code causing the error to appear? Initializing can be done on your MSX2+, because you don't need DOS2 for that (keep DEL pressed to skip loading DOS2, keep INS pressed to skip loading the IDE-BIOS entirely). That is what I was telling. The code executed will probably be the bootsector of the card, which contains pc-code. Same problem occurs when booting from a diskette which was formatted on a pc. Greetings Maico Arts MSX NBNO -- This message was sent with an unlicensed evaluation version of Novell NetMail. Please see http://www.netmail.com/ for details. ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Hi Maico, If memory serves well, you should press DEL or some key to bypass CF bootup and boot normally from diskette. With the fdisk you should do the partitioning and then all should work normally. Your memory serves you very well. Booting while pressing DEL the computer started correctly and I was able to partition/format the card from a floppy disk. I remembered that I had to do something like this (because I had an IDE+RS232 before), but I was pressing INS instead of DEL at boot. ;) Thanks for the help, -- Javi Lavandeira - http://www.ag0ny.com ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Javi Lavandeira wrote: Your memory serves you very well. Booting while pressing DEL the computer started correctly and I was able to partition/format the card from a floppy disk. I remembered that I had to do something like this (because I had an IDE+RS232 before), but I was pressing INS instead of DEL at boot. ;) Thanks for the help, Javi Lavandeira - http://www.ag0ny.com But, Javi, isn't the CF-IDE just extremely cool??? ^_^ Really, I still love it :) small, silent, no external power supply... Not to mention that you can take it with you without having to be really careful -- http://www.sandisk.com/pressrelease/20040823.htm :) ~Grauw -- Ushiko-san! Kimi wa doushite, Ushiko-san!! ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Yes, it is one of the best hardware pieces around! Now I use a PC notebook with a PCMCIA CF adapter, and a Turbo-R GT with the CF IDE adapter and the MegaFlashSCC cart to upload what I code for MSX in my PC. Nice combination! It makes MSX development and debugging faster! Regards, Edward Robsy From: Laurens Holst [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [MSX] IDE-CF: No enough memory Date: Fri, 27 Aug 2004 21:14:37 +0200 Javi Lavandeira wrote: Your memory serves you very well. Booting while pressing DEL the computer started correctly and I was able to partition/format the card from a floppy disk. I remembered that I had to do something like this (because I had an IDE+RS232 before), but I was pressing INS instead of DEL at boot. ;) Thanks for the help, Javi Lavandeira - http://www.ag0ny.com But, Javi, isn't the CF-IDE just extremely cool??? ^_^ Really, I still love it :) small, silent, no external power supply... Not to mention that you can take it with you without having to be really careful -- http://www.sandisk.com/pressrelease/20040823.htm :) ~Grauw -- Ushiko-san! Kimi wa doushite, Ushiko-san!! ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx _ Horóscopo, tarot, numerología... Escucha lo que te dicen los astros. http://astrocentro.msn.es/ ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Laurens Holst wrote: Sunrise advises against using CF carts 32MB because the chance for incompatibilities is much bigger for those. No probs with my Kodak (Toshiba) 16MB cart. The thing with 32MB carts is that you can't partition them with FDISK, but a normal 'big floppy' format can be done without problems. IIRC, I got the No enough memory when my SCSI interface was in a higher or lower (can't remember) slot than the IDE interface (I use a CF Adapter + normal IDE interface). But since the OP specified nothing else was connected to his turboR, that can't be the problem... Greetz, Patriek ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
Hello, IIRC, I got the No enough memory when my SCSI interface was in a higher or lower (can't remember) slot than the IDE interface (I use a CF Adapter + normal IDE interface). But since the OP specified nothing else was connected to his turboR, that can't be the problem... The BERT scsi interface is known for this problem too: I have several diskinterfaces and especially when connecting more than one to the MSX you can get this kind of trouble. The BERT interface must be the first one to use. With the exception of the internal diskinterface for the floppydrive of my TurboR GT. Most of the time you have to be carefull with the use of the driveletters... Greetings Maico Arts MSX NBNO -- This message was sent with an unlicensed evaluation version of Novell NetMail. Please see http://www.netmail.com/ for details. ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
[MSX] IDE-CF: No enough memory
Hi all, I received today my IDE-CF, but I'm having some trouble with it. The problem is that if I boot the computer with a memory card in the master slot, the computer always hangs with the following error: No enough memory. These are the things I've found out: - Booting the MSX without a memory card inserted, the interface's BIOS says that it cannot find a master device and the computer boots normally. - Booting with a memory card in the master slot, I get the No enough memory error message in a FS-A1ST (expanded to 512Kb) and a FS-A1GT. I've tried also an FS-A1WX (64Kb) and I don't get the error message, but the floppy disk in this computer is broken, so I couldn't do more testing. - Flashing the BIOS works correctly when I boot the computer without a memory card. - The No enough memory error appears regardless of the slot where the cartridge is inserted. My hardware is: - Panasonic FS-A1ST (512Kb)/A1GT/A1WX - CF ATA-IDE, BIOS 2.21 - 128Mb CF card (detected as TOSHIBA THNCF128MA at boot) - Nothing else connected to the computer Any ideas on what can be causing the problem? Regards, PS: I posted this same message on Sunrise's forum too. -- Javi Lavandeira - http://www.ag0ny.com ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] IDE-CF: No enough memory
If memory serves well, you should press DEL or some key to bypass CF bootup and boot normally from diskette. With the fdisk you should do the partitioning and then all should work normally. Greetings Maico Arts MSX-NBNO - Original Message - From: Javi Lavandeira [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, August 27, 2004 3:42 AM Subject: [MSX] IDE-CF: No enough memory Hi all, I received today my IDE-CF, but I'm having some trouble with it. The problem is that if I boot the computer with a memory card in the master slot, the computer always hangs with the following error: No enough memory. These are the things I've found out: - Booting the MSX without a memory card inserted, the interface's BIOS says that it cannot find a master device and the computer boots normally. - Booting with a memory card in the master slot, I get the No enough memory error message in a FS-A1ST (expanded to 512Kb) and a FS-A1GT. I've tried also an FS-A1WX (64Kb) and I don't get the error message, but the floppy disk in this computer is broken, so I couldn't do more testing. - Flashing the BIOS works correctly when I boot the computer without a memory card. - The No enough memory error appears regardless of the slot where the cartridge is inserted. My hardware is: - Panasonic FS-A1ST (512Kb)/A1GT/A1WX - CF ATA-IDE, BIOS 2.21 - 128Mb CF card (detected as TOSHIBA THNCF128MA at boot) - Nothing else connected to the computer Any ideas on what can be causing the problem? Regards, PS: I posted this same message on Sunrise's forum too. -- Javi Lavandeira - http://www.ag0ny.com ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx -- This message was sent with an unlicensed evaluation version of Novell NetMail. Please see http://www.netmail.com/ for details. -- This message was sent with an unlicensed evaluation version of Novell NetMail. Please see http://www.netmail.com/ for details. ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
[MSX] SVI738 memory slot change
Hi How can one change the slot where the svi keeps its main ram from slot 1 to 3-2 or anything else for that matter. JP --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.545 / Virus Database: 339 - Release Date: 27/11/2003 ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
[MSX] About memory usage in (Disk)BASIC
Hi ppl, here is a lightweight question for those who are in summer holidays and have therefore a lot of time for MSX investigation. It is about how the memory is used in the BASIC environment when disk interface is present. MSX2 Technical Handbook says that it is as follows: - Up to HIMEM (HFC4A), normal BASIC memory. - From BLDCHK+1 (HF377+1), BLOAD/BSAVE routines, 25 bytes. This variable points to the same address as HIMEM. - From FCBBASE (HF353), space for disk FCBs of disk files opened by BASIC (this area is 37*7 bytes, so a maximum of MAXFILES=6 can be used, FCB 0 is used for BLOAD/BSAVE). Note that this is not the same as the FCBs area in the normal BASIC memory (267 bytes * (MAXFILES+1)) - From HIMSAV (HF349), the general disk work area starts. This area exists also in DOS mode. I have seen that this scheme is followed exactly in this way in DOS 1. However in DOS 2 it is different: - Up to HIMEM (HFC4A), normal BASIC memory. - From HIMEM to HIMSAV there is an apparently unused area of 525 bytes. - From HIMSAV, the general disk work area starts. BLDCHK+1 and FCBSAVE point to somewhere into this area. And the question is: what is this 525 bytes ghost area for? May it be reused for BASIC programs (doing a CLEAR up to the address pointed by HIMSAV) safely? 525 bytes is really much memory when using the BASIC environment. OK, so go for it, the first person replying this question will earn 100 points! *** XXIV MSX USERS MEETING IN BARCELONA: DECEMBER ??th 2003 *** - Konami Man - AKA Nestor Soriano (^^)v http://www.konamiman.com- [EMAIL PROTECTED] ICQ#: 18281450 Itoshii hito no tame ni Ima nani ga dekiru ka na? Kanawanai yume wa nai yo! Massugu ni shinjiteru - ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
[MSX] Memory mappers in MSX2+ machines?
Hi! For openMSX machine configurations we need to be 100% sure if (or which of) the MSX2+ machines (or MSX2 machines with 64kB RAM) have a memory mapper or not... So, if you happen to own an original, unmodified MSX2 or MSX2+ with 64kB of main RAM, please do the following test for us: 1) start the machine to basic (without any device in the cartridge slots) 2) type a simple line in basic like this: 10 PRINT HELLO 3) type: OUT HFE,2 4) type LIST and please check what the result is (and remember this). It either shows nothing (then it has a mapper) or shows the just entered program (then it has no mapper). Now we doublecheck: 5) type OUT HFE,1 6) type LIST Now the program should be back in case it disappeared. Please e-mail me with the results: machine brand name and type (e.g.: Panasonic FS-A1WX) and the results of the test. Thanks in advance! -- Grtjs, Manuel PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ ) PPS: Visit my homepage at http://manuel.msxnet.org/ ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
[MSX] Max memory for a Turbo-R ST
Hi, just a question to keep the mailing list alive :) I have a TR ST with a 30 pins 1MB Simm in it (and no, I don't know who made it). So when I boot the comp it say's 1024Kb, it disables the default internal 256kb memory of the comp. But the question is, can I replace the 1MB Simm with a 4MB Simm ? Regards, Sandy -- Generation MSX http://www.generation-msx.nl ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] Sunrise memory expansions.
Hi I do not know the pirce for making such hardware, but it does seem strange that a 4M mapper is more expencive than a IDE interface? JP On 12 Aug 2002 22:18:03 +0200, in local.msx.int you wrote: Hi all, I had see the information over memory expansions, from Ivan Latorre at 8.11.02. Ivan Latorre wrote: It seems that MSX memory expansions are quite hard to find .. The new version of the 4MB card ( LPE-4M-V2 ) is now available at 75 euros without limitations. You can see it in http://lpadial.aamsx.org/page3.HTM For buy in the Nederland area please contact with Rinus Stoker. Greets, Leonardo Padial. ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Re: [MSX] Sunrise memory expansions
- Original Message - From: Ivan Latorre [EMAIL PROTECTED] To: International MSX Mailing List [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Monday, August 12, 2002 1:01 AM Subject: [MSX] Sunrise memory expansions Hi Ivan, I was wondering; has Sunrise ever thought in producing/selling MSX memory expansions? MoonSound, Graphics9000, IDE and RS232C cartridges, slot expanders, ... but, what about memory expansions? Nowadays you can find lots of roms on the Internet that require more than 128 Kbytes of RAM (and also think in the standard 64 Kbytes of RAM built in MSX2+ computers...). It seems that MSX memory expansions are quite hard to find so it can be an interesting product... Leonardo Padial has made a wide variaty of RAM expansions. In fact he even has made a 512 kB special memoryexpansion for games ROMS, called FLASHG. He also makes conventional memoryexpansions from 512 kB up to 4 MB. He is currently working on bigger memory-expansions based on a whole new concept. This is based on the LPE-MAPPER which can be used for all sorts of expansions, including DSP chips and modern memory-expansions (like DIMM, SDRAM etc). You can contact Leonardo at [EMAIL PROTECTED] Gerrit ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
RE:[MSX] Sunrise memory expansions.
Hi all, I had see the information over memory expansions, from Ivan Latorre at 8.11.02. Ivan Latorre wrote: It seems that MSX memory expansions are quite hard to find .. The new version of the 4MB card ( LPE-4M-V2 ) is now available at 75 euros without limitations. You can see it in http://lpadial.aamsx.org/page3.HTM For buy in the Nederland area please contact with Rinus Stoker. Greets, Leonardo Padial. ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
[MSX] Sunrise memory expansions
Hi I was wondering; has Sunrise ever thought in producing/selling MSX memory expansions? MoonSound, Graphics9000, IDE and RS232C cartridges, slot expanders, ... but, what about memory expansions? Nowadays you can find lots of roms on the Internet that require more than 128 Kbytes of RAM (and also think in the standard 64 Kbytes of RAM built in MSX2+ computers...). It seems that MSX memory expansions are quite hard to find so it can be an interesting product... Just giving ideas ;) Ivan ___ MSX mailing list ([EMAIL PROTECTED]) Info page: http://lists.stack.nl/mailman/listinfo/msx
Memory upgrade for WAVY70
Hi Does anyone have the schematics to expand (internally) the memory of Sanyo MSX2+ computers? I've seen some of them upgraded to 128/256/512 Kb. Greets -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: Memory upgrade for WAVY70
128kb upgrade is simple. The machine already have a place on it's PCB for a aditional 64kb memory bank. To have more than 128kb you will need to make a circuit to control the bigger mapper. Cya MSXers ... - Original Message - From: Ivan Latorre [EMAIL PROTECTED] To: International MSX Mailing List [EMAIL PROTECTED] Sent: Sunday, October 28, 2001 10:01 AM Subject: Memory upgrade for WAVY70 Hi Does anyone have the schematics to expand (internally) the memory of Sanyo MSX2+ computers? I've seen some of them upgraded to 128/256/512 Kb. Greets -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Memory expansion for WAVY70
Hi Does anyone have the schematics to expand (internally) the memory of Sanyo MSX2+ computers? I've seen some of them upgraded to 128/256/512 Kb. Greets -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
MSX memory
Are msx machines usually upgradable, as far as RAM? I have a Sony F1XD, which comes with 64KB of RAM, and it won't let me play Zanac Ex (among other things), which is killing me :) If they are, where's a good place to buy another 64KB? -- ak Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd all be running around in darkened rooms, munching pills and listening to repetitive music. --- Unknown -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: MSX memory
MSX machines are memory upgradable yes. Two methods: - solder in extra memory ic's,relative easy for machines with already a memory mapper in place. - place a memory mapper in a cartridge slot. Well supported by most cracked MSX games. Hard too find, not for sale new as far as i know. If you are the soldering type, check my webpage in the diy section for ideas, and Philips MSX-2 examples. www.msxhans.msx2.com - Original Message - From: Jack O'Lantern [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 05, 2001 09:08 Subject: MSX memory Are msx machines usually upgradable, as far as RAM? I have a Sony F1XD, which comes with 64KB of RAM, and it won't let me play Zanac Ex (among other things), which is killing me :) If they are, where's a good place to buy another 64KB? -- ak Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd all be running around in darkened rooms, munching pills and listening to repetitive music. --- Unknown -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: MSX memory
Thanks for all the info, I'll definitely look at it in detail once I get home. As a side question, is it possible to remove memory IC from one machine and put it in another (solder, if necessary)? I have a toshiba msx1 which I really don't need; I'd like move its RAM into the Sony if possible. - Original Message - From: Hans Otten [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 05, 2001 4:06 AM Subject: Re: MSX memory MSX machines are memory upgradable yes. Two methods: - solder in extra memory ic's,relative easy for machines with already a memory mapper in place. - place a memory mapper in a cartridge slot. Well supported by most cracked MSX games. Hard too find, not for sale new as far as i know. If you are the soldering type, check my webpage in the diy section for ideas, and Philips MSX-2 examples. www.msxhans.msx2.com - Original Message - From: Jack O'Lantern [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 05, 2001 09:08 Subject: MSX memory Are msx machines usually upgradable, as far as RAM? I have a Sony F1XD, which comes with 64KB of RAM, and it won't let me play Zanac Ex (among other things), which is killing me :) If they are, where's a good place to buy another 64KB? -- ak Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd all be running around in darkened rooms, munching pills and listening to repetitive music. --- Unknown -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: MSX memory
That depends. Most MSX-1 machines use the same dynamic memory chips. As do MSX-2 (but larger capacity). So open the machine and check! - Original Message - From: Akop Karapetyan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 05, 2001 21:23 Subject: Re: MSX memory Thanks for all the info, I'll definitely look at it in detail once I get home. As a side question, is it possible to remove memory IC from one machine and put it in another (solder, if necessary)? I have a toshiba msx1 which I really don't need; I'd like move its RAM into the Sony if possible. - Original Message - From: Hans Otten [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 05, 2001 4:06 AM Subject: Re: MSX memory MSX machines are memory upgradable yes. Two methods: - solder in extra memory ic's,relative easy for machines with already a memory mapper in place. - place a memory mapper in a cartridge slot. Well supported by most cracked MSX games. Hard too find, not for sale new as far as i know. If you are the soldering type, check my webpage in the diy section for ideas, and Philips MSX-2 examples. www.msxhans.msx2.com - Original Message - From: Jack O'Lantern [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 05, 2001 09:08 Subject: MSX memory Are msx machines usually upgradable, as far as RAM? I have a Sony F1XD, which comes with 64KB of RAM, and it won't let me play Zanac Ex (among other things), which is killing me :) If they are, where's a good place to buy another 64KB? -- ak Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd all be running around in darkened rooms, munching pills and listening to repetitive music. --- Unknown -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: MSX memory
Think this better, memory is cheap and easy to find At 12:23 05/10/2001 -0700, you wrote: Thanks for all the info, I'll definitely look at it in detail once I get home. As a side question, is it possible to remove memory IC from one machine and put it in another (solder, if necessary)? I have a toshiba msx1 which I really don't need; I'd like move its RAM into the Sony if possible. - Original Message - From: Hans Otten [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 05, 2001 4:06 AM Subject: Re: MSX memory MSX machines are memory upgradable yes. Two methods: - solder in extra memory ic's,relative easy for machines with already a memory mapper in place. - place a memory mapper in a cartridge slot. Well supported by most cracked MSX games. Hard too find, not for sale new as far as i know. If you are the soldering type, check my webpage in the diy section for ideas, and Philips MSX-2 examples. www.msxhans.msx2.com - Original Message - From: Jack O'Lantern [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, October 05, 2001 09:08 Subject: MSX memory Are msx machines usually upgradable, as far as RAM? I have a Sony F1XD, which comes with 64KB of RAM, and it won't let me play Zanac Ex (among other things), which is killing me :) If they are, where's a good place to buy another 64KB? -- ak Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd all be running around in darkened rooms, munching pills and listening to repetitive music. --- Unknown -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: DOS2 freeing R800 DRAM memory
Please note that you can also advise your ST users to boot the ST in DOS1 mode. That will also free the 32kB of RAM used by DOS2 itself. True, but I'd have to rewrite all the file functions for DOS1 and wouldn't be able to support subdirectories anymore :( I hate DOS1 file functions... Dos2 means harddisk. ROMs are large. ~Grauw -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: DOS2 freeing R800 DRAM memory
] Please note that you can also advise your ST users to boot the ST in DOS1 ] mode. That will also free the 32kB of RAM used by DOS2 itself. ] ] True, but I'd have to rewrite all the file functions for DOS1 and wouldn't ] be able to support subdirectories anymore :( ] I hate DOS1 file functions... I have a small library with the most important file-functions that runs on top of DOS1 and DOS2. If DOS2 is present, it will use the underlying DOS2 functions and if DOS2 is not present it will use the old fashioned DOS1 functions. The functions in the library are in DOS2 style. Though, you can only keep 1 file open at the same time. So, it is something like 'open file, read from file, close file'. If you want, I can send this library to your private email adress. Kind regards, Alex Wulms -- Visit The MSX Plaza (http://www.inter.nl.net/users/A.P.Wulms) for info on XelaSoft, Merlasoft, Quadrivium, SD-Snatcher on fMSX, the MSX Hardware list, XSA Disk images, documentation, Japanese MSX news from Ikeda and lots more. -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: DOS2 freeing R800 DRAM memory
Alex Wulms wrote: The utility romturbo.com switches to R800 ROM mode and makes the 64kB RAM available to the normal pool of free RAM. Brilliant ^_^ But I can mail you ramturbo.com and romturbo.com if you want to investigate them. It is ofcourse nice to have this functionality integrated in your emulator. I already found them on FuNET, but thanks anyway :) Please note that you can also advise your ST users to boot the ST in DOS1 mode. That will also free the 32kB of RAM used by DOS2 itself. True, but I'd have to rewrite all the file functions for DOS1 and wouldn't be able to support subdirectories anymore :( I hate DOS1 file functions... Greetz, Patriek -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: DOS2 freeing R800 DRAM memory
] Alex Wulms: ] The utility is indeed something wonderfull. Though, freeing the memory ] only works when you have disabled the dos2 ramdisk and when you have not ] loaded memman. ] ] So is this util called 'romturbo.com' and 'ramturbo.com'? Else I'm afraid I ] don't know which util was discussed. :/ It is indeed romturbo.com and ramturbo.com. The utility romturbo.com switches to R800 ROM mode and makes the 64kB RAM available to the normal pool of free RAM. The utility ramturbo.com copies the ROM blocks back to the upper 64kB of RAM, removes the 64kB from the normal pool of free RAM switches back to R800 RAM mode. ] ] ] So how does the ROM get there in the first place?! There must be some ] ] routine in the BIOS that gets it there??? ] That is correct. ] ] Do you know which routine that is? No. But I can mail you ramturbo.com and romturbo.com if you want to investigate them. It is ofcourse nice to have this functionality integrated in your emulator. Please note that you can also advise your ST users to boot the ST in DOS1 mode. That will also free the 32kB of RAM used by DOS2 itself. In that case, you only have to make a very simple modification to your emulator: If MSX turbo R booted in DOS2 mode: keep your memory management as it is. If booted in DOS1 mode: switch to R800 ROM mode and search all available memory yourself. In that case, you do not need to worry about (re)allocating DOS2 memory segments and the whole lot. Though, you may still want to copy the ROMS back to upper memory before exiting the emulator. Just as a courtesy to the user... Kind regards, Alex Wulms -- Visit The MSX Plaza (http://www.inter.nl.net/users/A.P.Wulms) for info on XelaSoft, Merlasoft, Quadrivium, SD-Snatcher on fMSX, the MSX Hardware list, XSA Disk images, documentation, Japanese MSX news from Ikeda and lots more. -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: DOS2 freeing R800 DRAM memory
] Alex Wulms wrote: ] ] My idea is to: ] ] 1. switch to R800 ROM mode ] ] 2. copy the DOS2 system area to the upper 2 segments ] ] 3. execute some stuff, using the 'freed' 64kB. ] ] 4. copy the DOS2 system area back to the original position ] ] 5. switch to R800 DRAM mode ] ] Ofcourse the interrupts are switched off during steps 2-4. ] There is already a utility which does this. I think this was discussed in ] the mailinglist a few weeks ago. ] ] If I understood correctly that utility does NOT relocate the DOS2 segments ] into what previously was DRAM-mode memory. And does NOT free up the extra ] 64kB to DOS2 memory managment. ] If it does, it must also patch DOS2 to use the relocated system data ] area. So are you sure it does exactly what my idea was??? ] (Or I could be wrong and this utility is something wonderful) The utility is indeed something wonderfull. Though, freeing the memory only works when you have disabled the dos2 ramdisk and when you have not loaded memman. ] ] You must copy the ROMs back explicitly (while still in ROM mode). ] ] So how does the ROM get there in the first place?! There must be some ] routine in the BIOS that gets it there??? That is correct. Kind regards, Alex Wulms -- Visit The MSX Plaza (http://www.inter.nl.net/users/A.P.Wulms) for info on XelaSoft, Merlasoft, Quadrivium, SD-Snatcher on fMSX, the MSX Hardware list, XSA Disk images, documentation, Japanese MSX news from Ikeda and lots more. -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: DOS2 freeing R800 DRAM memory
Alex Wulms: The utility is indeed something wonderfull. Though, freeing the memory only works when you have disabled the dos2 ramdisk and when you have not loaded memman. So is this util called 'romturbo.com' and 'ramturbo.com'? Else I'm afraid I don't know which util was discussed. :/ ] So how does the ROM get there in the first place?! There must be some ] routine in the BIOS that gets it there??? That is correct. Do you know which routine that is? Greetz, Patriek -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: DOS2 freeing R800 DRAM memory
] My idea is to: ] 1. switch to R800 ROM mode ] 2. copy the DOS2 system area to the upper 2 segments ] 3. execute some stuff, using the 'freed' 64kB. ] 4. copy the DOS2 system area back to the original position ] 5. switch to R800 DRAM mode ] Ofcourse the interrupts are switched off during steps 2-4. There is already a utility which does this. I think this was discussed in the mailinglist a few weeks ago. ] ] I'm assuming switching to R800 DRAM mode will cause the ROM to be copied to ] DRAM again? Wrong assumption. You must copy the ROMs back explicitly (while still in ROM mode). ] ] I'm not 100% sure this would work, but it sounds like a good idea. What do ] you guys think? Nice idea. Though, why do you want to re-invent the weel while it already exists? Kind regards, Alex Wulms -- Visit The MSX Plaza (http://www.inter.nl.net/users/A.P.Wulms) for info on XelaSoft, Merlasoft, Quadrivium, SD-Snatcher on fMSX, the MSX Hardware list, XSA Disk images, documentation, Japanese MSX news from Ikeda and lots more. -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: DOS2 freeing R800 DRAM memory
Alex Wulms wrote: ] My idea is to: ] 1. switch to R800 ROM mode ] 2. copy the DOS2 system area to the upper 2 segments ] 3. execute some stuff, using the 'freed' 64kB. ] 4. copy the DOS2 system area back to the original position ] 5. switch to R800 DRAM mode ] Ofcourse the interrupts are switched off during steps 2-4. There is already a utility which does this. I think this was discussed in the mailinglist a few weeks ago. If I understood correctly that utility does NOT relocate the DOS2 segments into what previously was DRAM-mode memory. And does NOT free up the extra 64kB to DOS2 memory managment. If it does, it must also patch DOS2 to use the relocated system data area. So are you sure it does exactly what my idea was??? (Or I could be wrong and this utility is something wonderful) You must copy the ROMs back explicitly (while still in ROM mode). So how does the ROM get there in the first place?! There must be some routine in the BIOS that gets it there??? Greetz, Patriek -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
DOS2 freeing R800 DRAM memory
Hi all, I'm really trying to get some extra memory for turboR ST users, because they can't use GEM v0.7 at all. The problem is the 64kB which is used for R800 DRAM mode located above the DOS2 system area. My idea is to: 1. switch to R800 ROM mode 2. copy the DOS2 system area to the upper 2 segments 3. execute some stuff, using the 'freed' 64kB. 4. copy the DOS2 system area back to the original position 5. switch to R800 DRAM mode Ofcourse the interrupts are switched off during steps 2-4. I'm assuming switching to R800 DRAM mode will cause the ROM to be copied to DRAM again? I'm not 100% sure this would work, but it sounds like a good idea. What do you guys think? Greetz, Patriek -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
RE: Memory question
Slot expanders are available. Sunrise still sells them www.msx.ch, maybe they will ship internationally. -Original Message- From: Brendan Cross [mailto:[EMAIL PROTECTED]] Sent: 24 May 2001 21:23 To: [EMAIL PROTECTED] Subject: Re: Memory question And for my next sarcasm brilliant /sarcasm question... where would I get a RAM-expansion cartridge? Also, where could I get a cartslot splitter? I have a feeling that two cartridge slots will all too soon become too little for me. ^.^ _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: Memory question
Hans Otten wrote: Many articles on memory upgrade (not all translated, so check the figures) on my website www.geocities.com/msxhans Also check www.hansoranje.demon.nl You can also buy an external memory expansion cartridge. Greets -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
RE: Memory question
True, much easier, less risk! -Original Message- From: Ivan Latorre [mailto:[EMAIL PROTECTED]] Sent: 24 May 2001 18:18 To: [EMAIL PROTECTED] Subject: Re: Memory question Hans Otten wrote: Many articles on memory upgrade (not all translated, so check the figures) on my website www.geocities.com/msxhans Also check www.hansoranje.demon.nl You can also buy an external memory expansion cartridge. Greets -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: Memory question
And for my next sarcasm brilliant /sarcasm question... where would I get a RAM-expansion cartridge? Also, where could I get a cartslot splitter? I have a feeling that two cartridge slots will all too soon become too little for me. ^.^ _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: Memory question
Brendan Cross wrote: And for my next sarcasm brilliant /sarcasm question... where would I get a RAM-expansion cartridge? Ese Artists' Factory: http://www.hat.hi-ho.ne.jp/tujikawa/ese/ Contact: Kazuhiro Tsujikawa mailto:[EMAIL PROTECTED] Product Name: Nice Memory Ukkarikun Memory size: 4 MB Description: Cartridge with label (=circuit board+plastic case+label) Price: About 114 US dollars Tsujikawa doesn´t reply e-mails very fast. LPE Electronics Contact: Leonardo Padial mailto:[EMAIL PROTECTED] Memory size: 1MB or 4MB Description: Circuit board only (without platic case) Price: 1MB about 50 US dollars, 4MB about 60,5 US dollars Terra Network System Product name: AddRam2 Memory size: 4 MB Description: Cartridge (circuit board+plastic case) Price: TNS ceased the production of AddRam2. I don't know if Takamichi Suzukawa still has stock of them. Ask him if you are interested mailto:[EMAIL PROTECTED] Also, where could I get a cartslot splitter? I Sunrise: http://www.msx.ch Leonardo Padial: mailto:[EMAIL PROTECTED] Ademir Carchano: http://www.carchano.com.br/expansor.htm (I don´t know if Mini Slot Expansor is still being sold). have a feeling that two cartridge slots will all too soon become too little for me. ^.^ And for me! :-/ Greets -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Memory question
This is probably a stupid question, but... how do I upgrade the memory on my MSX2? If possible, I'd like to upgrade it to 4MB. ^.^ It's an NMS-8250, with, built-in, 128KB ram 128KB VRAM. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
RE: Memory question
Many articles on memory upgrade (not all translated, so check the figures) on my website www.geocities.com/msxhans Also check www.hansoranje.demon.nl -Original Message- From: Brendan Cross [mailto:[EMAIL PROTECTED]] Sent: 24 May 2001 03:32 To: [EMAIL PROTECTED] Subject: Memory question This is probably a stupid question, but... how do I upgrade the memory on my MSX2? If possible, I'd like to upgrade it to 4MB. ^.^ It's an NMS-8250, with, built-in, 128KB ram 128KB VRAM. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
How much memory does your MSX have?
Hi, We have started a new poll in aamsx.org, focused on the specifications for the development of new games. This time what we want to know is: How much memory does your MSX have? If you have an *EXTERNAL* memory expansion, please *DON'T* count that memory in the answer. We want to know only about the internal mapper (even if it has been upgraded). The poll is, as usual, at: http://www.aamsx.org Regards, -- [EMAIL PROTECTED] - http://www.aamsx.org -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
More memory in Panasonic MSX2+
Hello I was wondering if it´s possible to expand internally the RAM of Panasonic MSX2+ computers (they only have 64 KB). If it is possible; does anyone have the schematics? Many thanks -- For info, see http://www.stack.nl/~wynke/MSX/listinfo.html
Re: memory testing
I'm looking for a program to extensively test the memory of my msx, because I want to know if the 2 Mb of memory, I build in my 8250 is working properly. http://www.adrpage.cjb.net/msxsoft.html Look for "TestRAM". Adriano Camargo Rodrigues da Cunha ([EMAIL PROTECTED]) Engenharia de Computacao - UNICAMP http://www.adrpage.cjb.net http://if.you.dont.like.msx.usuck.com * My HD has 1Mb of bad sectors and 100Mb of bad-windows. * Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/
Re: memory testing
At 16:23 27-9-00 -0300, you wrote: I'm looking for a program to extensively test the memory of my msx, because I want to know if the 2 Mb of memory, I build in my 8250 is working properly. http://www.adrpage.cjb.net/msxsoft.html Look for "TestRAM". I made a pretty thourough tester too. If you want it, send me a private mail, so I can send it to you. GreeTz, BiFi Visit my Home Page at www.bifi.msxnet.org mail me at: [EMAIL PROTECTED] FTP: ftp.bifi.msxnet.org ICQ #36126979 Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/
Re: memory testing
I'm looking for a program to extensively test the memory of my msx, because I want to know if the 2 Mb of memory, I build in my 8250 is working properly. http://www.adrpage.cjb.net/msxsoft.html Look for "TestRAM". Ï already got that program through email, but thanx for the reply Greetings Richard Adriano Camargo Rodrigues da Cunha ([EMAIL PROTECTED]) Engenharia de Computacao - UNICAMP http://www.adrpage.cjb.net http://if.you.dont.like.msx.usuck.com * My HD has 1Mb of bad sectors and 100Mb of bad-windows. * Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/ Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/
Re: memory testing
Ï already got that program through email, but thanx for the reply Did you check out MAPTEST4.COM? It was the program used by Digital KC. Best regards, Manuel --- Pre-PS: After 29/9/2000, I cannot use this address anymore. Therefore, from 25/9/2000, please send all mail to [EMAIL PROTECTED], my always- valid address. I can also read that mail from here in Japan. Thank you. PS: MSX 4 EVER! (Questions? See: http://www.faq.msxnet.org/ ) PPS: Visit my home page at http://bilderbeek.cjb.net/ Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/
Re: memory testing
Ï already got that program through email, but thanx for the reply Did you check out MAPTEST4.COM? It was the program used by Digital KC. No, I used testram.com - no errors are found, so I think its oke. But where can I find maptest4.com ? greetings Richard Best regards, Manuel --- Pre-PS: After 29/9/2000, I cannot use this address anymore. Therefore, from 25/9/2000, please send all mail to [EMAIL PROTECTED], my always- valid address. I can also read that mail from here in Japan. Thank you. PS: MSX 4 EVER! (Questions? See: http://www.faq.msxnet.org/ ) PPS: Visit my home page at http://bilderbeek.cjb.net/ Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/ Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/
Re: memory testing
Did you check out MAPTEST4.COM? It was the program used by Digital KC. No, I used testram.com - no errors are found, so I think its oke. But where can I find maptest4.com ? I don't know! I got it from Maico Arts (mail him?). I cannot send it to you know, since I have no access to my harddisk. I also had MAPTEST3.BIN, an earlier version (non DOS as you can see), that one I got with my MSX2 after Alwin Henseler built in the Memory Mapper. Best regards, Manuel --- Pre-PS: After 29/9/2000, I cannot use this address anymore. Therefore, from 25/9/2000, please send all mail to [EMAIL PROTECTED], my always- valid address. I can also read that mail from here in Japan. Thank you. PS: MSX 4 EVER! (Questions? See: http://www.faq.msxnet.org/ ) PPS: Visit my home page at http://bilderbeek.cjb.net/ Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/
memory testing
Hello I'm looking for a program to extensively test the memory of my msx, because I want to know if the 2 Mb of memory, I build in my 8250 is working properly. Is there a program that reads/writes different patterns into the memory, to see if its reliable? Greetings Richard Problems? contact [EMAIL PROTECTED] See also http://www.faq.msxnet.org/
Turbo-R Memory Expansion
Hi there, i have a big problem !!! My Turbo-R isn;t working anymore : But i found the problem, there is a wire not connected anymore from the memory expansion to the R800, it has to be a pin in the range of 31 - 50. Can somebody please help me ?? Is there somebody who knows how to build in a internal memory expansion in a Turbo-R ST ? Then give me an e-mail with the pin number... Regards, Sandy Pleyte Generation MSX MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in the body (not the subject) of the message. Problems? contact [EMAIL PROTECTED] More information on MSX can be found in the following places: The MSX faq: http://www.faq.msxnet.org/ The MSX newsgroup: comp.sys.msx The MSX IRC channel: #MSX on Undernet
Re: Turbo-R Memory Expansion
-- Van: Sandy Pleyte [EMAIL PROTECTED] Aan: [EMAIL PROTECTED] Onderwerp: Turbo-R Memory Expansion Datum: maandag 8 mei 2000 20:20 Hi there, i have a big problem !!! My Turbo-R isn;t working anymore : At least you have a Turbo R ! But i found the problem, there is a wire not connected anymore from the memory expansion to the R800, it has to be a pin in the range of 31 - 50. Can somebody please help me ?? Is there somebody who knows how to build in a internal memory expansion in a Turbo-R ST ? Then give me an e-mail with the pin number... Regards, Sandy Pleyte Generation MSX MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in the body (not the subject) of the message. Problems? contact [EMAIL PROTECTED] More information on MSX can be found in the following places: The MSX faq: http://www.faq.msxnet.org/ The MSX newsgroup: comp.sys.msx The MSX IRC channel: #MSX on Undernet MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in the body (not the subject) of the message. Problems? contact [EMAIL PROTECTED] More information on MSX can be found in the following places: The MSX faq: http://www.faq.msxnet.org/ The MSX newsgroup: comp.sys.msx The MSX IRC channel: #MSX on Undernet
Re: Turbo-R Memory Expansion
-Original Message- From: Sandy Pleyte [EMAIL PROTECTED] To: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Monday, May 08, 2000 20:23 Subject: Turbo-R Memory Expansion Hi there, i have a big problem !!! My Turbo-R isn;t working anymore : But i found the problem, there is a wire not connected anymore from the memory expansion to the R800, it has to be a pin in the range of 31 - 50. Can somebody please help me ?? Is there somebody who knows how to build in a internal memory expansion in a Turbo-R ST ? Then give me an e-mail with the pin number... I think I could help.. I have an F1-ST with build in 1MB (30 pins PC simm) but I haven't done it myself.. please gimme a day or 2 and I'll send you the schematics. Greetz, Patsie MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in the body (not the subject) of the message. Problems? contact [EMAIL PROTECTED] More information on MSX can be found in the following places: The MSX faq: http://www.faq.msxnet.org/ The MSX newsgroup: comp.sys.msx The MSX IRC channel: #MSX on Undernet
DOS 2 memory management...
ppl. Here's the story... SCC-Blaffer NT does not support DOS2. d-fader has no docs whatsoever using DOS2. So he has a question... Well... Here it is... Bank 0..7 are filled with data Blaffer needs. Now is my question: Can I still use these banks while DOS2 stores itselfs in bank 8 en 9 (when having 128K)?? And can someone give me good docs about DOS2 memory management, with a few examples if possible?? thanks... mzl. d.fader.twz. --- Get free personalized email at http://www.iname.com MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: DOS 2 memory management...
ppl. Here's the story... SCC-Blaffer NT does not support DOS2. d-fader has no docs whatsoever using DOS2. So he has a question... Well... Here it is... Bank 0..7 are filled with data Blaffer needs. Now is my question: Can I still use these banks while DOS2 stores itselfs in bank 8 en 9 (when having 128K)?? And can someone give me good docs about DOS2 memory management, with a few examples if possible?? Have you checked the docs mentioned in the DOS2-section of the FAQ? Grtjs, Manuel ((m)ICQ UIN 41947405) PS: MSX 4 EVER! (Questions? See: http://www.faq.msxnet.org/) PPS: Visit my homepage at http://www.sci.kun.nl/marie/home/manuelbi/ MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: DOS 2 memory management...
Have you checked the docs mentioned in the DOS2-section of the FAQ? He's right. Those docs are the official ones of ASCII describing all you need. Look in the Application Manual, section 4 or so (if I'm not mistaking). Ah, well, just check the index. Those docs are all I have about Dos2, and I have to say, they are sufficient. Great job ASCII!!! If you really, really, really want it, I can send you some example of Dos2 managementroutines if you'd like to... But I'll have to run upstairs for them, find, select, save, copy, copy, paste, post them, so please save me the trouble and say the Dos2 docs are sufficient or else try to find the Dos2 memroutines in some other source. To answer your question: Bank 0..7 are filled with data Blaffer needs. Now is my question: Can I still use these banks while DOS2 stores itselfs in bank 8 en 9 (when having 128K)?? Yes, you can use them. Dos2 always stores itself in the upper 2 segments of the primary (=currently selected) mapper. But beware!!! USE THE DOS2 MEMORY-MANAGEMENT ROUTINES!!! Otherwise it will not work. Maybe on your system (with no TSR or other programs running), but not on other systems with, for example, a disk-cache program like LUNA installed. ~Grauw -- email me: [EMAIL PROTECTED] or ICQ: 10196372 visit the Datax homepage at http://datax.cjb.net/ MSX fair Bussum / MSX Marathon homepage: http://msxfair.cjb.net/ MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
RE: Memory Mapper mirror effect?
-Original Message- From: Laurens Holst [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, September 16, 1998 8:52 PM To: [EMAIL PROTECTED] Subject: Re: Memory Mapper mirror effect? Anyone knows if there are memory mappers with mirror effect (i.e., for example, a 128k mapper (8 pages), if I select page 16, I'll get page 8). I don't know any, but maybe there is... All mappers do this 'mirroring'... If they didn't then it would not be possible to detect the mappersize... (only legal mappersize-detection is done by using the mirror-effect). It would be possible if selecting a page that doesn't exist results in selecting memory that is not present. Then data written to an address in that page can not be read back. In fact. it would be simpler then: 10 i=0 20 out hfe,i:d=peek(h8000):pokeh8000,d xor 255 30 if peek(h8000)d xor 255 then 100 40 pokeh8000,d 50 if peek(h8000)d then 100 60 i=i+1:if i=256 then 100 70 goto 20 100 print i;:print " pages of mapper RAM" Well, something like this... Greetz, Patrick MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory Mapper mirror effect?
Anyone knows if there are memory mappers with mirror effect (i.e., for example, a 128k mapper (8 pages), if I select page 16, I'll get page 8). I don't know any, but maybe there is... All mappers do this 'mirroring'... If they didn't then it would not be possible to detect the mappersize... (only legal mappersize-detection is done by using the mirror-effect). No! This is not the correct way to detect the mapper size!!! As a matter of fact, the turbo-R does not have 2^x mapper pages accessible when running in R800-dram mode!!! 4 pages are reserved to store bios, basic and kanji (thought these were the ones) in to speed up the execution, because ROM is not as fast as RAM. The access to these pages is disabled by hardware. Even a turbo-R has the 'mirror' effect, but you can not say that this is the only thing you have to look at to determine the number of mapper pages. By the way, there is a trick to alter these pages: * switch to R800-ROM and these pages are accessible * make changes (e.g. replace KANJI with KUN, I use this method now and then) * and switch back to R800-DRAM H... Here comes a nice thing, not related to this subject, but I have noticed that access to the internal ram of the turbo-R is faster than access to external memory/ram. So it is faster to run KUN-Basic in place of the kanji-ram-place than from an rom-module in a cartridge slot. Another thing is : data that has to be accessed a lot should be in the internal ram of the turbo-R. Not only because of the slot-switching, but because of the access time too! Greetings from Erik Maas p.s. I don't know what kind of program is under development, but I hope the mapper MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory Mapper mirror effect?
Anyone knows if there are memory mappers with mirror effect (i.e., for example, a 128k mapper (8 pages), if I select page 16, I'll get page 8). I don't know any, but maybe there is... All mappers do this 'mirroring'... If they didn't then it would not be possible to detect the mappersize... (only legal mappersize-detection is done by using the mirror-effect). ~Grauw -- email me: [EMAIL PROTECTED] or ICQ: 10196372 visit the Datax homepage at http://datax.cjb.net/ MSX fair Bussum / MSX Marathon homepage: http://msxfair.cjb.net/ MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Memory Mapper mirror effect?
Hi, folks. Anyone knows if there are memory mappers with mirror effect (i.e., for example, a 128k mapper (8 pages), if I select page 16, I'll get page 8). I don't know any, but maybe there is... Thanks, Adriano Camargo Rodrigues da Cunha ([EMAIL PROTECTED]) Engenharia de Computacao - UNICAMP http://www.adrpage.cjb.net MSX-TR:I have one.And you? * Suicide is like saying to God - You can't fire me ! I am quiting! * MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory Mapper mirror effect?
On Wed, 15 Sep 1999, Adriano Camargo Rodrigues da Cunha wrote: Anyone knows if there are memory mappers with mirror effect (i.e., for example, a 128k mapper (8 pages), if I select page 16, I'll get page 8). I don't know any, but maybe there is... Sure there is! I don't know how Turbo-R's Mapper works, but standard mappers have mirror effect. If you select block 16, you'll get block 0, and the same will happen if you select block 8. (blocks are numbered from 0 to 7). But the most interesting is to select the same block in different RAM pages. You can write a byte in one address, and in another address the same byte appears! Really cool! Greetings from Brazil! - Marco Antonio Simon Dal Pozhttp://www.lsi.usp.br/~mdalpoz [EMAIL PROTECTED] "Apple" (c) Copyright 1767, Sir Isaac Newton MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [off] memory management in the PC
Cesar Cardoso wrote: Remember guys, this is valid only on MS/PC/DR/OpenDOS, Windows 3.x, Windows 9x. Other systems (Linux, BSD family, Windows NT I think, Solaris/Linux, OS/2) don't need to do all this tricks. ...because they never use the real mode they give you a bunch of virtual mem. and you never worry about where it is allocated... btw, win9x can do it as well although the manager ssuucckkss!!.. greetz akai! MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
[off] memory management in the PC
On Thu, 26 Aug 1999, Giovanni R. Nunes wrote:
And don't forget! What means "pia" in portuguese? :)
That's easy, "pia" means "boy" or "child".
Someone asked about PC memory management in real mode. There are
three ways to do it:
1) XMS: with this method you can access the pc bios to copy blocks
from high memory to low memory (and the other way too). This is slow since
it requires the use of "rep movsd" or equivalent.
2) EMS: in this one you can map the high memory in the low memory,
the same way we do in the Memory Mapper or the MegaRAM. This is slow since
it puts the processor in virtual86 mode, and the "in" and "out" opcodes
can get as much as twelve times slower.
3) UMB: this option lets you manage the hole between 640kb and
1Mb, but it should not be used to let this space free for LOADHIGH
device drivers.
In short, memory management in the PC sucks.
Ricardo Bittencourt http://www.lsi.usp.br/~ricardo
[EMAIL PROTECTED] "Ricardo is subtle, but malicious he is not"
-- Uniao contra o forward - crie suas proprias piadas --
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [off] memory management in the PC
Ricardo Bittencourt Vidigal Leitao wrote: Someone asked about PC memory management in real mode. There are three ways to do it: In short, memory management in the PC sucks. Remember guys, this is valid only on MS/PC/DR/OpenDOS, Windows 3.x, Windows 9x. Other systems (Linux, BSD family, Windows NT I think, Solaris/Linux, OS/2) don't need to do all this tricks. -- Cesar "You can't declare Life as virtual. Declare it as real" MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [off] memory management in the PC
] On Thu, 26 Aug 1999, Giovanni R. Nunes wrote: ] ]And don't forget! What means "pia" in portuguese? :) ] ] That's easy, "pia" means "boy" or "child". ] ] Someone asked about PC memory management in real mode. There are ] three ways to do it: ] ] In short, memory management in the PC sucks. ] Only in real mode. But who is still using real mode these days...? Just use a 32-bit extender for DOS or use a real 32-bit OS (like linux, os2, solaris, winnt, beos, etc). Then all memorymanagement problems are gone and the PC becomes a very wonderfull machine. Theoretically capable of emulating a MSX with 4MB memory mapper in every subslot... Besides, I saw Linus yesterday on CNN. He is much cooler then Bil. So, I've decided to become a Linus fan in stead of a Bil fan ;-) Kind regards, Alex Wulms -- Alex Wulms/XelaSoft - MSX of anders NIX - Linux 4 ever See my homepage for info on the *** XSA *** format http://www.inter.nl.net/users/A.P.Wulms MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: NMS8250 Memory
On Mon, 19 Jul 1999 16:07:23 +0200, [EMAIL PROTECTED] wrote: According to a brazilian web site (i dunno exactly the name is tought it was msx home) it is possible to expand the memory simply by adding a few chips, but i can't read the text which comes with it, can somebody suply me with a english version of the memory expansion. We produce an internal memory expansion, it's not expensive... by Frengo Miri Software MSX Computer System Italy e-mail : [EMAIL PROTECTED] HomePage :http://Frengo.dragonfire.net/MSX.HTM *** greetz andre MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/) MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: NMS8250 Memory
That will do and the soldering iron isn't the problem. greets andre owner-msx [EMAIL PROTECTED] on 07/19/99 06:52:24 PM Please respond to msx [EMAIL PROTECTED] @ SMTP To: msx [EMAIL PROTECTED] @ SMTP cc: Subject:Re: NMS8250 Memory Classification: Restricted According to a brazilian web site (i dunno exactly the name is tought it was msx home) it is possible to expand the memory simply by adding a few chips, but i can't read the text which comes with it, can somebody suply me with a english version of the memory expansion. I have a dutch version, will that do? :) It is not a question of just adding chips. But it's not difficult if you can handle a soldering iron. Tristan + Omega + join #msx on undernet +[EMAIL PROTECTED]+ | | FUNET MSX maintainer | ftp://ftp.funet.fi/pub/msx | + irc: OmegaMSX +Techno composer+ http://users.bart.nl/~omegamsx + MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/) MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Memory map and interrupts at boot time
What's the actual memory map configuration and interrupt status at boot time (phase 2, after RET NC)? Can I assume it's the same on all MSX models and configurations or it depends on the firmware (either internal ROMs or from extra hardware)? Just to save a couple of instructions! 8;) Btw, what are the contents of DE, HL and A passed to the boot code? Kiss you lot. MARK 2 MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory map and interrupts at boot time
At 05:08 AM 7/20/99 +0200, you wrote: What's the actual memory map configuration and interrupt status at boot time (phase 2, after RET NC)? Interrupt status: no idea. Memory configuration: all RAM, with some routines (slot select etc) copied into page 0. Bye, Maarten MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory map and interrupts at boot time
At 05:08 AM 7/20/99 +0200, you wrote: What's the actual memory map configuration and interrupt status at boot time (phase 2, after RET NC)? Interrupt status: no idea. I issued a HALT and get frost. Memory configuration: all RAM, with some routines (slot select etc) copied into page 0. But the standard boot code seems to jump #4022 without slot select if MSXDOS.SYS is not present. MARK 2 MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
NMS8250 Memory
According to a brazilian web site (i dunno exactly the name is tought it was msx home) it is possible to expand the memory simply by adding a few chips, but i can't read the text which comes with it, can somebody suply me with a english version of the memory expansion. greetz andre MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: NMS8250 Memory
According to a brazilian web site (i dunno exactly the name is tought it was msx home) it is possible to expand the memory simply by adding a few chips, but i can't read the text which comes with it, can somebody suply me with a english version of the memory expansion. I have a dutch version, will that do? :) It is not a question of just adding chips. But it's not difficult if you can handle a soldering iron. Tristan + Omega + join #msx on undernet +[EMAIL PROTECTED]+ | | FUNET MSX maintainer | ftp://ftp.funet.fi/pub/msx | + irc: OmegaMSX +Techno composer+ http://users.bart.nl/~omegamsx + MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: VDP memory write timings
Laurens Holst wrote: Just keep in mind to have at least 7 t-states between every transfer (=OUT), then it will work on all MSX-computers (OTIR and INIR are slow enough too). MSX-turboR and 7MHz have automatic slowdowns implemented to that works too. No, this is not completely true!! If you're writting to the VRAM that contains the spritedata and sprites are enabled, then you'll need more time ! Apparently the VDP has a one byte buffer and writes this buffer to VRAM when it has time to acces that VRAM. Since sprite VRAM is used rather much the available time to write here is much less. So if you write to fast this byte-buffer is overwritten with new data before the old one is in the actual VRAM. David Heremans "One difference between SuSE and Red Hat is that the former operates in a country where people don't sue each other over coffee being too hot." Linus Torvalds MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
memory upgrade
does anyone know where in holland I can get the memory of my nms 8250 expanded? and how much this costs? thx, pepijn Get your free email from AltaVista at http://altavista.iname.com MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
RE: memory upgrade
Try Hans Oranje, HCC MSX usergroup. Hier het adres van Hans Oranje. E-mailadres(sen): [EMAIL PROTECTED] [EMAIL PROTECTED] Persoonlijke gegevens: Adres: Waddinxveen Telefoonnummer: 0182-618932 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: maandag, juli 05, 1999 12:05 uur To: [EMAIL PROTECTED] Subject: memory upgrade does anyone know where in holland I can get the memory of my nms 8250 expanded? and how much this costs? thx, pepijn Get your free email from AltaVista at http://altavista.iname.com MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/) MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: VDP memory write timings
I have to write a gfx data burst to VRAM as quickly as possible while the display, and possibly sprites are enabled. I've noticed data corruption when using quick transfer loops (via POP) that disappears when display is disabled. Is there an accurate way to determine required VDP timings and ensure proper functionality on all MSX models regardless of different clocked CPUs? Just keep in mind to have at least 7 t-states between every transfer (=OUT), then it will work on all MSX-computers (OTIR and INIR are slow enough too). MSX-turboR and 7MHz have automatic slowdowns implemented to that works too. ~Grauw email: [EMAIL PROTECTED] or ICQ: 10196372 Visit the Datax homepage at http://datax.cjb.net/ ... Live long and prosper... MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
VDP memory write timings
I have to write a gfx data burst to VRAM as quickly as possible while the display, and possibly sprites are enabled. I've noticed data corruption when using quick transfer loops (via POP) that disappears when display is disabled. Is there an accurate way to determine required VDP timings and ensure proper functionality on all MSX models regardless of different clocked CPUs? Kiss you lot. Mk2 -- Madonna Mark Two "Martin Galway means to me what Elvis meant to Sigue Sigue Sputnik" MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: MSX2 memory mappers
On Fri, 19 Mar 1999, Alwin Henseler wrote: Ooohh, it's really hard to explain those Brazilians all about memory mappers! (don't they have any?). Not all Brazilians (or am I being so repetitive?). I converted several games from Memory Mapper to Megaram, and I never had Memory Mapper! Some facts: An MSX2 doesn't need to have a memory mapper to be a true MSX-2. Example: Sony HB-G900. 64K RAM, no mapper, but true MSX-2, nothing wrong with it. That's what I said! Sony HB-F9P: 128 K, mapper Smaller: Almost every Japanese-built MSX2 or 2+: 64K mapper Philips NMS 8220 has only 64K, but this IS a mapper. Really a 128K mapper with 2nd half empty, so switching blocks, you get: Block 0, 1, 2, 3, "nothing", "nothing", "nothing", "nothing", block 0 again, 1 again, 2 again, 3 again, "nothing", "nothing", "nothing", "nothing", 0 again, 1 again, etc. Then, it can be expanded to 128kb. Not standard? Absolutely standard! Mapper=64K = 4 blocks (0-3), selecting block 0, 1, 2, 3 gets you mapper blocks 0, 1, 2, 3 - all ok. Reading the mapper ports on this machine would return other values as you might expect, but reading mapper ports SHOULD be considered unreliable, right? Not only unreliable, but a wrong procedure, since the MSX Technical Handbook prevents it. Greetings from Brazil! - Marco Antonio Simon Dal Pozhttp://www.lsi.usp.br/~mdalpoz [EMAIL PROTECTED] "Apple" (c) Copyright 1767, Sir Isaac Newton /"\ \ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL / \ MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: MSX2 memory mappers
Nestor's (Konamiman) online version of the MSX-2 technical handbook clearly reads: Well, at least someone is using my TH transcription, nice to see this! 8-) minimum, required: 64 K RAM memory mapper: OPTIONAL Well, actually... I invented this part. X-D Hey, just kidding! - the MSX-2 standard DEFINES memory mappers, but does NOT require it. Yep. In fact, Sony F500 does NOT have memory mapper and does NOT accept external mappers... 15th MSX users meeting in Barcelona: May 1th, 1999 Konami Man - AKA Nestor Soriano (^ ^)v - Itsumo MSX user http://www.geocities.com/SiliconValley/Bay/9797/msx.htm [EMAIL PROTECTED] ICQ#: 18281450 Metal Gear for MSX - (C) Konami 1987 (Nothing new under the sun...) MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: MSX2 memory mappers
"jam" [EMAIL PROTECTED] wrote: You are wrong. Every MSX2 must have Memory Mapper. Even with only 64K of RAM, it's mapped RAM. Read the MSX2 Technical Handbook (by ASCII) and check it. Nestor's (Konamiman) online version of the MSX-2 technical handbook clearly reads: minimum, required: 64 K RAM memory mapper: OPTIONAL - the MSX-2 standard DEFINES memory mappers, but does NOT require it. Alwin Henseler ([EMAIL PROTECTED]) http://huizen.dds.nl/~alwinh/msx MSX Tech Doc page MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
MSX2 memory mappers
Hi all, Ooohh, it's really hard to explain those Brazilians all about memory mappers! (don't they have any?). Some facts: An MSX2 doesn't need to have a memory mapper to be a true MSX-2. Example: Sony HB-G900. 64K RAM, no mapper, but true MSX-2, nothing wrong with it. Apparantly there exist Philips MSX-2's without a mapper (not the 8220, which has a mapper), because I made a schematic once for building 128K mapper in those (if all Philips MSX-2's had mappers, I wouldn't have). I suppose the VG 8230 could be such a machine. If you have a VG8230: check it! Does this one have a mapper, or not? Be sure it is a 8230: I've helped build a 8235 into a 8230's casing once... 128K mappers in Philips machines: Sony HB-F9P: 128 K, mapper Smaller: Almost every Japanese-built MSX2 or 2+: 64K mapper Philips NMS 8220 has only 64K, but this IS a mapper. Really a 128K mapper with 2nd half empty, so switching blocks, you get: Block 0, 1, 2, 3, "nothing", "nothing", "nothing", "nothing", block 0 again, 1 again, 2 again, 3 again, "nothing", "nothing", "nothing", "nothing", 0 again, 1 again, etc. Not standard? Absolutely standard! Mapper=64K = 4 blocks (0-3), selecting block 0, 1, 2, 3 gets you mapper blocks 0, 1, 2, 3 - all ok. Reading the mapper ports on this machine would return other values as you might expect, but reading mapper ports SHOULD be considered unreliable, right? Bigger: Turbo-R: 256K (ST) or 512K (GT), mapper Sony HB-G900AP (note the "A" in there!): 512K or 1 MB., mapper Greetings, Alwin Henseler([EMAIL PROTECTED]) http://huizen.dds.nl/~alwinh/msx MSX Tech Doc page MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: MSX2 memory mappers
Ooohh, it's really hard to explain those Brazilians all about memory mappers! (don't they have any?). Not to ALL brazilian. Just to the "fudeba" ones. :) Adriano Camargo Rodrigues da Cunha ([EMAIL PROTECTED]) Engenharia de Computacao - UNICAMP http://www.adrpage.cjb.net MSX-TR:I have one.And you? *** NEW URL! AdrianPage now is at http://www.adrpage.cjb.net *** * My next Pentium(tm) computer will be a Silicon Graphics Workstation * MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Fw: Memory Mapper
-Original Message- From: J. Lukens +ADw-j.lukens+AEA-hetnet.nl+AD4- Newsgroups: comp.sys.msx Date: Thursday, March 04, 1999 09:10 Subject: Memory Mapper +AD4-Hello all, +AD4- +AD4-Since I have stopped my quest for a Turbo R for now, I am looking for +AD4-someone who is willing to sell me an external memorymapper of about 512 KB +AD4-or one MB, preferebly in the Netherlands, so I can come and get it myself. +AD4- +AD4-I am the proud owner of an NMS8280 in complete original condition, and I do +AD4-not want to take any risks with it, but if anyone out there knows an address +AD4-or so where I can have my MSX2 internally upgraded to 1 MB or so, I would +AD4-really like to know too. +AD4- +AD4-Jan Lukens +AD4- +AD4- +AD4- MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [real coding] DOS2 and Memory...
Hi people, Thinking that you should set the interruptvector at #C000 when you set I to #C0 is a commonly made mistake in the MSX world. You should set your interruptpointer at address #C0FF instead. As some of you might know, the databus in the MSX is connected to VCC with pull-up resistors. As a consequence the Z80 will always fetch the value 0xFF when reading from the databus at a moment that no device is writing to the databus. For example, when the Z80 reads the databus in IM2 after having received an interrupt request. Well as I wrote I always filled in the whole area from #C000 to #CFFF so I never got problems with it (nowadays I program under Dos environment so I don't use it anymore). By the way, that will be C0FE and not C0FF, because interrupt-vectors can only be even numbers, bit 0 is ignored (always zero). Recently, I read the specs of of my Philips modem adapted to an RS232... The chip inside can generate an interrupt-vector... Is this put through to the MSX, will it really generate a vector when used in IM2??? If so, that would be cool. Or is the MSX standard not capable to use a IM2-vector? ~Grauw MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory mapper
At 16:48 24/02/99 +0100, you wrote: At 16:09 24/02/99 +0100, you wrote: Hi Does anyone have a schematic of a memory mapper that can use 1 MB SIMMs ? I'll ask a friend about this, I only have it for Turbo R internal Can u send this info 2 me too? 4th question: does anyone know of a MSX-site that has anything related to MSX-hardware (schematics etc.) don't know I've a friend who were preparing a MSX Hardware Book, like that Hardware Book that we can find in the web. And you can take a look at Alwin's homepage, and Novatec's homepage. There are some very interesting projects. _ __ | __ \ (_| ICQ UIN: 3635907 | | M. Sc. In Numerical Modelling - UFF | |__) | _ __ _ _ __ __| | ___ Niteroi - RJ - BR +-+ | _ / | |/ __// _` | '__/ _` |/ _ \ | Sola Scriptura | | | \ \ | | (__| (_| | | | (_| | (_) | | Sola Gratia | |_| \_\|_|\___\\__,_|_| \__,_|\___/ Jurczyk Pinheiro |Sola Fide| http://pagina.de/rjp - [EMAIL PROTECTED] - [EMAIL PROTECTED] | Solo Cristi | MSX freak, X-Phile, Trekker, Christian, Transformers, | Soli Deo Gloria | Anime (Yamato!), CuD, Linux, Rock, Comics, and hate M$! +-+ MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Memory mapper
Hi Does anyone have a schematic of a memory mapper that can use 1 MB SIMMs ? 2nd question: where do I get 50 pin header connectors or experimental MSX slot PCB's ? 3rd question: anybody happens to have the schematics of a Canon V20 MSX1 ? 4th question: does anyone know of a MSX-site that has anything related to MSX-hardware (schematics etc.) Thanx MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory mapper
At 16:09 24/02/99 +0100, you wrote: Hi Does anyone have a schematic of a memory mapper that can use 1 MB SIMMs ? I'll ask a friend about this, I only have it for Turbo R internal 2nd question: where do I get 50 pin header connectors or experimental MSX slot PCB's ? humm let's see. try your local electronic part dealer ;-) 3rd question: anybody happens to have the schematics of a Canon V20 MSX1 ? I don't have it but I'm very interesting in it, once I've started to drawn it by looking at the PCB, but it take hours of verification to make it right... 4th question: does anyone know of a MSX-site that has anything related to MSX-hardware (schematics etc.) don't know Thanx you are welcome :-) Martial. MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory mapper
Martial BENOIT wrote: At 16:09 24/02/99 +0100, you wrote: Hi Does anyone have a schematic of a memory mapper that can use 1 MB SIMMs ? I'll ask a friend about this, I only have it for Turbo R internal Can u send me the schematic? I have a Turbo R ST .. Thank's Luiz H. Lugato MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [real coding] DOS2 and Memory...
On Mon, 22 Feb 1999, Alex Wulms wrote: Thinking that you should set the interruptvector at #C000 when you set I to #C0 is a commonly made mistake in the MSX world. You should set your interruptpointer at address #C0FF instead. As some of you might know, the databus in the MSX is connected to VCC with pull-up resistors. As a consequence the Z80 will always fetch the value 0xFF when reading from the databus at a moment that no device is writing to the databus. For example, when the Z80 reads the databus in IM2 after having received an interrupt request. This is true on a standard MSX with correct devices connected to it. If on the other hand a device only checks IORQ and not M1, it might put data on the bus when it is read at interrupt-time (In this mode IORQ and M1 are both active). Conclusion: Putting the interrupt vector on [I]fe (I believe the last bit is set to 0, since a 2-byte address is fetched) should be enough on a corruct machine, but it is more secure to fill the whole table from [I]0 to [I]fe, so: jumptable: equ hc000 ld a,.high. jumptable ld i,a ld hl,interrupt_routine ld (jumptable),hl ;fill table up ld hl,jumptable ld de,jumptable+2 ld bc,Hfe ldir Bye, shevek --- Visit the internet summercamp via http://polypc47.chem.rug.nl:5002 MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [real coding] DOS2 and Memory...
] This is true on a standard MSX with correct devices connected to it. If on ] the other hand a device only checks IORQ and not M1, it might put data on ] the bus when it is read at interrupt-time (In this mode IORQ and M1 are ] both active). A device which ignores M1 does not respect the Z80 nor the MSX bus protocol, hence is not MSX compatible! Such a device will not only cause problems in IM2 but also in IM0 (the Z80 expects to get an instruction, in the MSX it will always be 0xFF which is RST 38h) and even in IM1 such a device may cause problems. In the last case because a device may generate wait-states. Especially when it is slow. This might impact the timing of games, copyprotections and other softwares that rely on accurate timing. And ofcourse it might also impact the functionality of the device itself. Some devices reset/set some internal bits after they have been read or think that they have been read. For example, the VDP resets the interrupt request bit after its status port has been read and it increases the address counter after its dataport has been read. Ofcoure, the I/O decoding for the VDP does respect the MSX bus protocol so we have never had any problems with that. Anyway, as far as I'm concerned you should ban devices from your MSX that are not MSX compatible. ] ] Conclusion: Putting the interrupt vector on [I]fe (I believe the ] last bit is set to 0, since a 2-byte address is fetched) should be enough The last bit is not set to 0 but read from the databus. Just like the other 7 bits. If you store the interrupt vector at the even address, your program will NOT work. Just try it. In a system that really supports IM2, you can have a convention that the device will only set the highest 7 bits and that the lowest bit musts always be set to 0. You can even enforce this with a specially designed circuit. But as far as the Z80 is concerned: it really reads all bits that are placed on the databus. In the case that an incompatible device would place an arbitrary number on the bus -which can be both an odd and an even number- there is only one real good solution: make sure that the high byte and the low byte of the interruptroutine are the same. For example: jumptable: equ hc000 interrupt_routine: equ h8080 ld a,.high. jumptable ld i,a ;initialize table ld hl,jumptable ld (hl),.low. interrupt_routine ;fill table up (from c000 upto and including c100) ld de,jumptable+1 ld bc,H100 ldir org interrupt_routine ; the real interruptroutine But as I already mentioned, you should ban such a device from your MSX anyway. And when using only compatible devices, my original routine is sufficient (store the pointer only at ofset 0xff in the table). Kind regards, Alex Wulms -- Alex Wulms/XelaSoft - MSX of anders NIX - Linux 4 ever See my homepage for info on the *** XSA *** format http://www.inter.nl.net/users/A.P.Wulms MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [real coding] DOS2 and Memory...
At 10:13 PM 2/22/99 +0100, you wrote: [about using IM2] You should set your interruptpointer at address #C0FF instead. As some of you might know, the databus in the MSX is connected to VCC with pull-up resistors. As a consequence the Z80 will always fetch the value 0xFF when reading from the databus at a moment that no device is writing to the databus. For example, when the Z80 reads the databus in IM2 after having received an interrupt request. Years ago, one of the NOP programmers told me that some devices do write a value to the databus during an interrupt. To make sure your program will work in any configuration, you need to fill 257 bytes with the same value. For example #81 for a routine at #8181. Bye, Maarten MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [real coding] DOS2 and Memory...
] You probably won't get problems. ] However, in Dos it is easiest to replace the bytes at adress #38, for ] example putting a JP Interrupt there. In Basic, it is -to my opinion- better ] if you swith away the ROM, however you could also set the other interrupt ] mode (mode 2?) in which the high byte of the adress of a jumptable is set in ] the I-register and the low byte of the adress is determined by the devie. ] For example, set I to #C0, and then fill adresses #C000-#C0FF with words of ] the adress the interrupt should jump to (yes, indeed, the device can only ] set odd adresses) (there are no devices delivering this lower byte of the ] adress on the MSX. So #C000 can be assumed as the set adress. However, it is ] still safe to fill the omplete 128 words with the right value, just in ] case...) Hi people, Thinking that you should set the interruptvector at #C000 when you set I to #C0 is a commonly made mistake in the MSX world. You should set your interruptpointer at address #C0FF instead. As some of you might know, the databus in the MSX is connected to VCC with pull-up resistors. As a consequence the Z80 will always fetch the value 0xFF when reading from the databus at a moment that no device is writing to the databus. For example, when the Z80 reads the databus in IM2 after having received an interrupt request. This is for example a codefragment, which I used in the 'No Waste' demo: intvector: equ #88ff ; int. vector int mode 2 scroll: di im 2 ld a,.high. intvector ld i,a ; Startoffset for int table ld hl,vertint ld (intvector),hl ; Set interruptvector ei ret vertint:in a,(#99) ; some code cut-out ei reti Kind regards, Alex Wulms -- Alex Wulms/XelaSoft - MSX of anders NIX - Linux 4 ever See my homepage for info on the *** XSA *** format http://www.inter.nl.net/users/A.P.Wulms MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: [real coding] DOS2 and Memory...
I read (nearly) all the messages from the last time... - Oh my god! I really miss mails refering to (program-) technical thingies... So - lets start a "serious" thread... ;cP **Great** DOS 2 memory -- I found out that the DOS2 page-switch routines are kinda slow. Does anybody know a simple, "legal", and compatible way to speed up those bottlenecks? Compatible, because I dunno how many different versions of DOS2 are in use. - And I want it to work with every kind of DOS2. The segment number Dos2 returns is the same as the MemMap page-number. Therefor, you can use the number you get if you allocate a page with OUT (#FC-#FF). It is illegal (ofcourse), but it works. This way you an also switch away page 3. But beware: If you set pages this way and you want to read from disk to that page the Bdos sets the old page he's got in his table. Really, these routines are made as fast as possible, so don't worry about speed. And if you do use the thing stated above, take care... Oh - another question comes in mind: In DOS1 you are not allowed to "ask" the outs (#fe...) about the page number which they may contain. You can't. Just use the pages starting with 0. So if you need 96k then use pages 0-5... - How will I know which ones are selected? - Is there a _STANDARD_ definition which memmaps are selected after the bootstrap? In dos1, the following table is valid: -3FFF: page 3 4000-7FFF: page 2 8000-BFFF: page 1 C000-: page 0 In Dos2 you should request the segment-nrs. using Get_Seg. DOS2 and Interrupts: I want to redirect the standard-interrupt (with use of IMx). Will I get troubles if there is NO(!) ROM selected in page0/1 the whole time? - I dont wanna load in this situation, only wanna switch mem... You probably won't get problems. However, in Dos it is easiest to replace the bytes at adress #38, for example putting a JP Interrupt there. In Basic, it is -to my opinion- better if you swith away the ROM, however you could also set the other interrupt mode (mode 2?) in which the high byte of the adress of a jumptable is set in the I-register and the low byte of the adress is determined by the devie. For example, set I to #C0, and then fill adresses #C000-#C0FF with words of the adress the interrupt should jump to (yes, indeed, the device can only set odd adresses) (there are no devices delivering this lower byte of the adress on the MSX. So #C000 can be assumed as the set adress. However, it is still safe to fill the omplete 128 words with the right value, just in case...) MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
Re: Memory...
-Oorspronkelijk bericht- Van: shevek [EMAIL PROTECTED] Aan: [EMAIL PROTECTED] [EMAIL PROTECTED] Datum: dinsdag 12 januari 1999 18:16 Onderwerp: Re: Memory... On Tue, 12 Jan 1999, J. Lautenbag wrote: In MSX INFO BLAD Hans van Oranje wrote how to use SIMMs as MSX-RAM... So I guess it depends on the price of SIMMs and the parts used... Willem Cazander told me this design was not optimal, but I guess the design he was talking about is a little more expensive... Are those schematics online somewhere? Or can somebody mail them to me? Second hand SIMM's aren't that expensive... Please put them online. I would like them too. In MSX-Info Blad 8 there was a complete description of how to build SIMM memory into a Philips NMS 8250/55/80 or into a Sony HB-500. In all MSX-computers with a S-3527 engine this can be done! Unfortunately this description is in Dutch only. If you can read Dutch, then you might consider to order this issue of MSX-Info Blad. You can do this by contacting Rinus Stoker on [EMAIL PROTECTED] or me on [EMAIL PROTECTED] ! The e-mail address of the author is [EMAIL PROTECTED] Without permission of MSX-Info Blad or the author this information may not be distributed freely! Greetings, Gerrit van den Berg MSX-Info Blad MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
