Re: MegaRAM
Roberto Pinna wrote: Mappers on the MSX2 are as standard as the V9938 Interesting, my MSX2 had no mapper and it ran without problems almost any japanese game. `:) I'm pretty sure it had no mapper, since it was a conversion over one old MSX1. I can't say the same for MSX2+, I think all of them had mapper. I may be mistaken, though. There was some games that didn't run in my machine, but people made some MegaRAM conv- ersions which ran fine. `:) [][]s, `:) Parn ICQ# 1693182 [EMAIL PROTECTED] --- "Music of the soul", Mitsuo Hagita 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/)
Athler Wars 2 cracked on Sony 900 with FM-PAC - continued. And ot
Hola Marco Antonio: If you prefer, I can send to you a CD with most of cracked version of Martos. MP MP And how should I pay for this CD? Hmmm. I have not decided it yet. If you are able to wait two or three weeks, I will try to put the CD on-line. Salidos, digo ... Saludos. JAMcn ([EMAIL PROTECTED]) Apdo. Correos 3294 18080 Granada ... INSERT COIN 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/)
Round 16... FAT! (help wanted!!)
Hola [EMAIL PROTECTED] !!! Nestor Soriano le soltc a jam: NS - Restore TPA segments in pages 1 and 2 NS - Load C=#62 (program terminate) and B=Error code NS - Jump to #0005 in TPA segment of page 3, via inter-segment call NS NS It works and COMMAND.COM takes control, but next execution of a NS program causes the computer to hang. Hmmm. But ... why does it hang? I think it would to work properly. NS driver (I hope!!). Also, any suggestion beta-testing offers will be NS welcome of course! I could beta-test it if you released a Novaxis version NS Thanxs in advance hasta incluso! Ta! Salidos, digo ... Saludos. JAMcn ([EMAIL PROTECTED]) Apdo. Correos 3294 18080 Granada ... 1 COIN 1 CREDIT 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 Legacy CD
Hola [EMAIL PROTECTED] !!! Nestor Soriano le soltc a jam: NS (Hi Jam! My commission!!) X-) Let's say ... a 20% for each CD selled in mailing-list? NS NS I agree! 8-) Ok. Look for clients and I'll pay your part. BTW, there is a trouble. I don't know how I have to send the CD to the potential buyers and how much must be it. And have you tested the 128K version of R-Type with FM? NS NS (!oo) No... Try it, it works very fine on any MSX-Music machine. And have you tested the 128K version of Hinotori WITHOUT slowdowning? NS NS (!!OO) No!! It's great too! MARTOS, I LOVE YOU !!! And have you tested Polar Star ROM? NS NS YES!! And it is MICROCABIN!!! 8-D I had to re-construct part of the graphics of the initial screen, since they were corrupted. I have work for more than 700 hours creating the ROMs files contained in MSX Legacy CD, using a fantabulous HEX editor (no assembler). I had even to re-allocate manuallay parts of some games. I had to work hardly with Bubbler and Blagger. And have you tested Hapy Fret ROM? NS NS What is this? It's the game that some people of this mailing-list commented some days ago. And have you tested Who Dares Wins 2 ROM? NS NS Hummm... too violence! X-) YEEAAAH!! And . Well, I think it's enough for today :D NS NS Then, hasta incluso! Then, try Hunch Back and Joe Blade. Both are joystick-only games. I have patched them in order to use keyboard/joy1/joy2. Now, I'm trying to do the same with Gauntlet, and trying to put it into a MegaROM file. So, we could play it without loading between levels :))) It is difficult, but I think I will succeed. Salidos, digo ... Saludos. JAMcn ([EMAIL PROTECTED]) Apdo. Correos 3294 18080 Granada ... GAME OVER. CONTINUE F5 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/)
Hydlide history
cool, check out the TE software Hydlide homepage: http://www.tes.co.jp/product/hydlide/index.htm They will release Hydlide for Windows April 23. Follow the link on the bottom of the page (small Hydlide logo) and see a history of hydlide: dated '83 - now. too bloody bad it is all in japanese. If anyone can do a quicky translation, I'd be very grateful. Marco -- Marco F.E.J. Frissen mailto:[EMAIL PROTECTED] Philips Digital Video Systems, CryptoWorks. Building OAN 2.39, Cederlaan 4 5616 SC Eindhoven, Netherlands -- Statistics are like bikinis: what they conceal is more important than what they reveal 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: 64K VRAM?
On Thu, 18 Mar 1999, shevek wrote: On Wed, 17 Mar 1999, Marco Antonio Simon dal Poz wrote: How can 64kb of RAM be memory mapper? Memory Mapper with only 4 memory blocks is a bit unuseful! Not at all. With a mapper every 16kB page can be switched on , 4000, 8000 or C000. This is useful for example when you want to use a lot of memory under BASIC. You can lift the bottom of your program to C000 (F676 if I remember correctly) and then use page 2 as data-area. With a 64kB mapper this still gives you 48kB to use, in stead of the 16kB you would have without a mapper. Yes, it's F676h that points to the bottom of the basic program. But the main utility of the Memory Mapper is to create a block switching system that allows the slot to contain much more than 64kb of RAM. Using Memory Mapper only to exchange memory contents isn't a big deal, because you still can do it using LDIR (or using a famous technique called swap, like this:) LD HL,source LD DE,destination LD BC,4000h LOOP: LD A,(HL) EX AF,AF' LD A,(DE) LD (HL),A EX AF,AF' LD (DE),A INC HL INC DE DEC BC LD A,B OR C JR NZ,LOOP RET Of course Memory Mapper if much faster, but it's not much flexible, because the block size to be exchanged is fixed in 16kb. If you want to change 8kb basic programs, you'll need to use the above technique. Is there a program that takes profit of the 64kb memory mapped? 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: MegaRAM
On Wed, 17 Mar 1999 [EMAIL PROTECTED] wrote: My project with MegaRAM uses a double-bank of mapped registers (16 bytes select ever 8kb block). And how do you think you'll make the registers? Will you use the even addresses to select LSB and odd addresses to select MSB? Reference for Mapped circuits are available on Elektor Electronics Magazine. Principles of mapper are publis- hed by brazilian Elektor on july'1986. The article name is "Eprom Expansions". Elektor? That magazine is made for begineers. I prefer "Circuit Cellar", by Steve Ciarcia, available in http://www.circuitcellar.com/ If you don't remember, Steve Ciarcia is the writter of the book called "Construct your own Microcomputer using Z80", McGrawHill. -EXACTLY what memory ranges do these blocks occupy? There are blocks in the area 4000h-5FFFh, 6000h-7FFFh, 8000h-9FFFh and A000-BFFFh. Graphic block diagram is: MEGARAM SLOTMEGARAM BLOCKS +-+++-+ | h-3FFFh || | 4000h-5FFFh | Block 0 +-+ --+ +-+ | 4000h-7FFFh | | 6000h-7FFFh | Block 1 +-+ +-+ | 8000h-BFFFh | | 8000h-9FFFh | Block 2 +-+ --+ +-+ | C000h-h || | A000h-BFFFh | Block 3 +-+++-+ Since that the mirror effect was known, this diagram isn't absolutely the truth. This implies that, when you select a block over page 0, it will be selected on page 2, too. The same is valid for page 3, that acts on page 1, too. The most mysteriuos MegaRAM's feature is the mirror :) MSB of address bus (A15) is ignored by MegaRAM! Yes, the creator of Megaram (Ademir Carchano) told me that he ignored A15 to make the hardware much more simple, and to fit in a standard cartridge box. So, you can use Megaram on page 0 and page 3, but when you're in "block select mode" IN A, (8Eh) No, "block select mode" is accessed by a OUT (8Eh),A and do a LD A,04h / LD (h),A the block 4 is selected for the area h-1FFFh and also for 8000h-9FFFh. If Slot (and sub-slot) Register are enable for same cartridge. If not, you can select and read/write on this 1st address, but not read/write on mirrored. Of course! Everything that I was talking about is valid only when all pages are selected over the slot where Megaram is connected. You can use 4 MegaRAM for every 16kb on same computer, 1st MegaRAM on 0-3FFFh, 2nd on 4000h-7FFFh, 3th on 8000h-BFFFh, and 4th on C000h-h. The (8Eh) port sets "block select/read mode" when OUT, or "write/read mode" when IN. Right. The same mechanic is used for "MegaRAM Disk" cartridge on (8Fh) port, for enable internal DiskROM for RAMDISK emulation. Yes, the ports affect all Megarams connected to the system. The opposite is also valid, when you do a LD A,04h / LD (8000h),A the block 4 is selected for the area 8000h-9FFFh and also for h-1FFFh. That's exactly what you said about many Megaroms (the most part of Konami ones). Mirror or "shadow" is the best name for ? For Megaram, mirror is best. But if Konami SCC Megarom works exactly like Alwin described, then shadow is best for Konami SCC Megarom. Second, if write-enable or block-switch state is undefined after a reset, No. The mode is undefined when computer startup, after reset none changes are made on this register. That's what I explained in the next related e-mail! it could ofcourse be in write-enable state at the time of reset, and behaving as normal RAM then, be detected as such (be it at 4000-BFFFh only). Yes, will be detected as normal RAM. But how much RAM is found depends of registers value. That can happen when you do a reset while Megaram is in "write enable mode". But I don't know how much memory will be detected as normal RAM. Does the BIOS verify if the mirror effect happens? But that's a good question! The computer could think that it's a normal RAM if the state is "write enable mode" while the slots are being scanned. I don't know how to answer your question, I guess that the start-up state should be "block select mode", but I'm not sure. No changes are made when startup sequence begins. MegaRAM are "RESET-insensitive". See technical informa tion and electrical diagram on CPU MSX Magazine nr 35. Don't trust in that magazine! I'll analyse the contents of those schematics to see if there aren't any bugs. Simple and good method: select (in descending order) each possible block, write its number in it in at some test address, and then (starting with block 0) check up until which block the block number matches what you find at the test address when selecting each block. (...) I think that this method has a fault Many faults for a test
Re: MegaRAM
snip Laurens Holst said: BTW, memory mapper wasn't born jointly with MSX2. Many MSX2 that I knew had only 64kb of RAM. Does your 8235 have internal Memory Mapper? Memory Mapper is part of the MSX2 standard. Ofcourse not, Laurens. Sony HB-G900P and Philips VG-8230 is really MSX2, but have no mapper. They're really, really, really 100% MSX2! So the NMS 8220 e.d. where not part of the MSX2 standard ? Same for the 8220, but maybe that 64kB of RAM _was_ mapped. I don't know. The 64kB RAM of all MSX2+ machines is mapped, I'm sure of that. Grtjs, Manuel 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: Round 16... FAT! (help wanted!!)
At 05:53 PM 3/17/99 +0100, you wrote: If so, a FAT16 driver should not in any way depend on a certain type of hardware/ROM, only change things that are the same with any disk interface. Or any DOS2-using interface, if you like. Yes, the standard way for accessing physical sectors is through routine #4010 of diskROM. But the standard input parameters specification for this routine allows only the use of 16 bit sector numbers. So, for accessing 24 bits sector numbers a controller specific routine is needed. So you are actually doing 2 upgrades at once? Upgrades being: 1. 16bit sector numbers - 24bit sector numbers (allows partitions 32MB) 2. FAT12 - FAT16 (keeps cluster size reasonable when partitions go beyond 32MB) Besides I need to set the "disk change" flag under certain circumstances, and (AFAIK) there is not standard diskROM routine for this. SET the disk change flag? Why do you need to do that? Reading the flag is perfectly possible using diskROM, but you probably already knew that. I also don't know how sector buffers works, Sector buffers are a kind of cache. They are located in the 32K of memory that DOS2 claims. If a sector is requested and it is located in a sector buffer, the content of the buffer is returned instead of reading the sector from disk. This is the mechanism that allows a turbo R to display "files" in BASIC a second time without accessing the drive. Disk buffers are invalidated whenever disk change status is "changed" or "unsure". If your MSX has hardware disk change checking (like turbo R), the hardware signal is used. Otherwise, the status will be "not changed" for a certain number of interrupts. 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/)
LOG(x) BASIC function
Hi all, I was wondering how BASIC calculates LOG(x). Does it use a look-up table (would require massive amounts of memory), some sort of algorithm (would require massive amounts of CPU time), or some mixed method? I'm trying to speed up multiplication and division (in machinecode) by using the following: log(x) + log(y) = log(x*y) log(x) - log(y) = log(x/y) I calculated I'd need about 96kB for a look-up table with reasonable accuracy. Because log(256*256)=4.8164 I'd need 48164 x 2 bytes. Although I don't mind wasting that much memory, there has to be a smarter way... Greetz, Patriek 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/)
Mitsubishi ML-G1
So, does this machine have 64KB VRAM or not? If so, I'll add it in the MSX hardwarelist... (Currently the amount of VRAM of that machine is unknown!) Maybe you can also check the other stuff that is unknown... Grtjs, Manuel 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: IDE troubles....
Hi The programm "part11" on the Fdisk. Peter from the Sunrise Team 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: MegaRAM
On Thu, 18 Mar 1999, Maarten ter Huurne wrote: Lots of people have one. I am one of them. Philips 8235, 8245, 8250, 8255 and 8280 were all sold with 128K mapper. Only Philips did it? Did other manufacturers do only 256kb of Mapper built-in? Beyond Metal Gear 2, do you know other Megarom games with 512kb of more? Hydlide 3 is 512K. ROM version of Royal Blood is 1MB. 8-megabit Megarom??? That's impressive! Is it downloadable in any site? And nobody was interested in transforming MSX1 to MSX2? I don't think any company ever offered such a conversion. Conversions from MSX2 to MSX2+ were offered though. Some included only V9958, others included new ROMs and/or internal MSX-MUSIC. Here in Brazil the only way to get MSX2 was doing conversions! Only actually Ademir Carchano produces boards of MSX2+, previously all MSX2 and MSX2+ were converted from MSX1. But ROM cartridges are very expensive. A memory expansion with exactly the same format than Megarom games was a more intelligent solution than buying several cartridges. Why didn't people from Japan create a kind of Megaram? Maybe they don't like doing illegal things? Take it easy! I was talking about one manufacturer (for example, Konami) sells Megaram cartridges and sell disks with the games separately. This would be much cheaper. Anyway, they did finally create one: the ESE-SCC. But it's main use is as a RAMdisk/DOS2 cartridge. That's a good idea, but was made very time before the Megaroms cartridges had been manufactured. The reason MegaRAM type cartridge was never developed in Europe is probably that 128K and 256K machines (SONY700) were sold. A lot of people had their MSXes memory expanded to run cracked megaROM games. Ok, that really explains everything. There was another problem here in Brazil (and perhaps in Europe too): there was no japanese softwarehouses representatives here! What were we supposed to do? In Europe, for a long time software was available in normal stores. But Was Japanese software available in normal stores? around 1990 we had to rely on imports for games like SD Snatcher and Solid Snake. I guess the European market was not profitable enough to make English versions of those games. One of the reasons was the large-scale copying. Importing games? Wasn't it too slow and too expensive? Do you know a FDC that supports 1.2Mb and 1.44Mb drives and is still being produced, and have good documentation? Note that 3.5MHz is too slow to allow reading of 1.44MB disks. The "inner loop" of the sector read routine is too slow to cope with the data flow. So if you want to create 1.44MB drives for MSX, you either have to use 7MHz Z80 or use some kind of buffer for reading sectors. Are you sure? A 720kb disk works with a FDC that handles 250kbits/s, a 1440kb disk works with a FDC that handles 500kbits/s. This means that the main routine should be able to read 12500 bytes per turn. It means that this routine should run 12500 times in 0.2 seconds. Then, the routine should spend a maximum of 16 microseconds. In a 3.57561149MHz, this means 57 clockcicles. LD HL,address LD C,D3h LOOP: IN A,(D0h) ; 12 clocks RRCA; 5 clocks JR NC,LOOP ; 9 or 12 clocks RRCA; 5 clocks RET NC ; 9 clocks INI ; 21 clocks (I guess) JP LOOP ; 10 clocks Total: 71 clockcicles. Conclusion: you're right, it's not possible to use 1.2Mb or 1.44Mb disks with Z80 at 3.57MHz. It's BAD! Then, there's still a chance only for Turbo-R. 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: MegaRAM
Philips 8235, 8245, 8250, 8255 and 8280 were all sold with 128K mapper. Only Philips did it? Did other manufacturers do only 256kb of Mapper built-in? See the hardwarelist: e.g. SOny HB-F700P: 256KB of Mapper. Hydlide 3 is 512K. ROM version of Royal Blood is 1MB. 8-megabit Megarom??? That's impressive! Is it downloadable in any site? It's on ftp.komkon.org/pub/MSX/Carts/Mega I believe. Here in Brazil the only way to get MSX2 was doing conversions! Only actually Ademir Carchano produces boards of MSX2+, previously all MSX2 and MSX2+ were converted from MSX1. Which MSX1 machines were used? Only Hotbit and Gradiente? In Europe, for a long time software was available in normal stores. But Was Japanese software available in normal stores? Konami ROMs were. And some others too. Clubs imported software, later. But in the beginning, there were even made tape-versions of Japanese software, under license. (Like Zanac, e.g., see a previous thread about Eaglesoft/Aackosoft). Importing games? Wasn't it too slow and too expensive? Appearantly not! Total: 71 clockcicles. Conclusion: you're right, it's not possible to use 1.2Mb or 1.44Mb disks with Z80 at 3.57MHz. It's BAD! Too bad! Then, there's still a chance only for Turbo-R. And 7.16 MHz MSX2! Grtjs, Manuel 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: Round 16... FAT! (help wanted!!)
So you are actually doing 2 upgrades at once? 1. 16bit sector numbers - 24bit sector numbers (allows partitions 32MB) 2. FAT12 - FAT16 (keeps cluster size reasonable when partitions go beyond 32MB) Yes. It has no sense to do one of these upgrades without doing the other, I think! ;-) SET the disk change flag? Why do you need to do that? The behavior of my driver when a function call is made is the following: - Check if the disk has been changed via CALL #4013. - If not, read an internal table which contains the type of the drive. If FAT16, process function call. Else (FAT12) do not process and let DOS to do it. - If yes, read boot sector in order to determine the type of drive. If FAT16, build new DPB and process function call. Else, let DOS to do it. Update the drive type table in both cases. Well, suppose that disk was changed and it is FAT12 type. My driver must do nothing and let DOS to execute funtion call. But what will do DOS at first? To check if the disk was changed. But my driver did it already!! So DOS will obtain a "disk not changed" status, even if the disk was changed, and will not update the drive's work area. This is very dangerous... How to solve it: if the disk was changed and it is FAT12, set again the disk change flag, so next call to #4013 (check disk change), performed by DOS, will return "disk was changed" status. I know how to do it but only on MegaSCSI. Reading the flag is perfectly possible using diskROM, but you probably already knew that. Yes but... setting?? I also don't know how sector buffers works, Sector buffers are a kind of cache. They are located in the 32K of memory that DOS2 claims. [...] Yeah, I know the general working procedures of sector buffers, but I don't know all the exact parameter: I know where they are placed, and the meaning of some bytes of the headers... but not all. And there is a flags byte whose description I don't know... And add other problem: sector buffer's header use only two bytes for sector number! So I think it is better if I use my own buffers, placed into another own RAM segment. And I can ever add an option for customize number of sector buffers, using more RAM segments if necessary. Disk buffers are invalidated whenever disk change status is "changed" or "unsure". Thanx! I had not tough in this detail!! ;-) But my "abort" routine continues crashing... someone, help!! (O! !O) 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: MegaRAM
No, with the IDE-Interface and a LS120 you can read 1,44MB disks Stichting Sunrise Team Peter 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/)
Which games work with START/GETDISK and/or FDDEMU (by Nyyrikki)?
Hi I was wondering if anyone could tell me which disk-based games can be run from harddisk with START/GETDISK and which with FDDEMU by Nyyrikki... Who posts/sends a list? Thanks! -- Grtjs, Manuel 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: MegaRAM
On Thu, 18 Mar 1999, Manuel Bilderbeek wrote: Philips 8235, 8245, 8250, 8255 and 8280 were all sold with 128K mapper. Only Philips did it? Did other manufacturers do only 256kb of Mapper built-in? See the hardwarelist: e.g. SOny HB-F700P: 256KB of Mapper. Ok, I see. But my question if if all 128kb built-in MSX are from Philips. Hydlide 3 is 512K. ROM version of Royal Blood is 1MB. 8-megabit Megarom??? That's impressive! Is it downloadable in any site? It's on ftp.komkon.org/pub/MSX/Carts/Mega I believe. Yes, that's true! Thanks!!! Here in Brazil the only way to get MSX2 was doing conversions! Only actually Ademir Carchano produces boards of MSX2+, previously all MSX2 and MSX2+ were converted from MSX1. Which MSX1 machines were used? Only Hotbit and Gradiente? Yes, HotBit was made by Sharp, and Gradiente was the manufacturer of Expert. In Europe, for a long time software was available in normal stores. But Was Japanese software available in normal stores? Konami ROMs were. And some others too. Clubs imported software, later. But in the beginning, there were even made tape-versions of Japanese software, under license. (Like Zanac, e.g., see a previous thread about Eaglesoft/Aackosoft). Tape made under license? And why didn't it happen in Japan? And how did it happen? Importing games? Wasn't it too slow and too expensive? Appearantly not! Here in Brazil it would be. The import tax is absurdly high, the transport is slow, and the inspection is lazy. Total: 71 clockcicles. Conclusion: you're right, it's not possible to use 1.2Mb or 1.44Mb disks with Z80 at 3.57MHz. It's BAD! Too bad! Then, there's still a chance only for Turbo-R. And 7.16 MHz MSX2! Yes, and why not 7.16MHz MSX1? BTW, how does a 7.16MHz works? I didn't change the main clock of my MSX2 because I know that V9938 won't work. 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: 64K VRAM?
On Thu, 18 Mar 1999, Marco Antonio Simon dal Poz wrote: Is there a program that takes profit of the 64kb memory mapped? There once was a basic-database that used the mapper. I guess it worked with 64kB as well... Most flexible memory programs do, I think. The memman filecopier BK does... I wrote some string management routines that use all memory it finds in page 2 and 1 page in page 1, so that would also be of more use when it has a mapper. I think there are many other programs. 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: MegaRAM
Manuel Bilderbeek schreef: snip snip snip So the NMS 8220 e.d. where not part of the MSX2 standard ? Same for the 8220, but maybe that 64kB of RAM _was_ mapped. I don't know. The 64kB RAM of all MSX2+ machines is mapped, I'm sure of that. the NMS8220 does have a mapper, and the mapper is 128Kb wide , but only 64Kb of ramis used. Grtjs, Manuel erik-- 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: LOG(x) BASIC function
On Thu, 18 Mar 1999, Patriek Lesparre wrote: Hi all, I was wondering how BASIC calculates LOG(x). Does it use a look-up table (would require massive amounts of memory), some sort of algorithm (would require massive amounts of CPU time), or some mixed method? I'm trying to speed up multiplication and division (in machinecode) by using the following: log(x) + log(y) = log(x*y) log(x) - log(y) = log(x/y) I calculated I'd need about 96kB for a look-up table with reasonable accuracy. Because log(256*256)=4.8164 I'd need 48164 x 2 bytes. Although I don't mind wasting that much memory, there has to be a smarter way... There is, though it's slower, of course. I believe the usual way calculators do it is with an aproximation curve. If you ask for the log, it gives you the result of a function (usually a polynome) which looks very much like a log. You could use the taylor-series, which can be calculated quite quick, but is not a very good approximation. I don't know the taylor-series by heart, but I could look it up. In case you want to start programming, it will be of the form: y=a+bx+cx^2+dx^3+ If i'm working on it anyway, I could find a more optimal way of choosing the parameters. If you tell me on what range you want to use it, I could optimize it for you. A faster way is to have a small lookup table and expect the parts in between to be lineair. It shouldn't be very slow to calculate that. Than you can make your own desicion how much memory you want to spend on it (96kB is really too much, I think...) I hope this helped, Bye, shevek 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: MSX fair in Madrid, MadriSX´99 - review for MSX magazines and diskmagazines
6- Boh Ken, this new programmers asociation came with new software, final beta versions of Puddle Land and KPI Ball were presented, another FAT16 routines and they sold Sonyc and games translations. Members: Manuel Pazos and Sutchan. Sutchan (?!) Where? I didn't see him. Bye, Manuel 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/)
[Fwd: Silence!]
[EMAIL PROTECTED] schrieb: Alex Wulms schrieb: Shadow !!!??? Where are you ?!?!!?!? We seem to need you in here !!! Because a lot of the people in this newsgroup don't seem to mail anymore when you're not arround !!! Maybe you don't know: he has no access to the newsgroup... :( What happened? Did his boss figure out that he was spending more time on the newsgroup that on his job??? Uhmm... it's possible, cause he changed the company... He has again a mail-address, but no access to the ng :( (I hope you keep him updated with your cr.. uhm, I meant with your wonderful partial off-topics...) ;cP NO - PLEASE! Don't tell me again why there are "some" off-topics! I know - MSX is fun and to talk about it (just fun) :-' greetz JJoS -- Tilburg Team: Janosch, SGI, D-AX, inDark, Maspo, SFS, Chief-Gavaman Darn!! I have sent this message to the personal account... But I'm sure all of you wanna read this... ;cP greetz JJoS -- Tilburg Team: Janosch, SGI, D-AX, inDark, Maspo, SFS, Chief-Gavaman 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: MegaRAM
] On Thu, 18 Mar 1999, Erik wrote: ] ] the NMS8220 does have a mapper, and the mapper is 128Kb wide , but only ] 64Kb of ] ramis used. ] ] What do you mean with that? It has 64kB, but reacts as 128kB? so: ] out(Hfe),0:?inp(Hfe) ] would return b1000 in stead of b1100? That would be against ] MSX-standard! I must be misunderstanding you, I think... It would not be. According to the MSX standard, it is not allowed to read the mapper registers. It is only a courtesy of some manufacturers that they produced readable mapper registers. If you want to keep track of your mapper state, you must maintain a copy of the mapper registers in your memory, just like MSXDOS2 does it. Actually, there is some history behind this whole story. The original MSX2 technical databook said that it is possible and allowed to read the mapper registers. But then people realized that you can get problems with multiple mappers and things like that.For example if one slot contains a 128K mapper and the other slot contains a 256K mapper. So, the MSX specifications got changed and from that moment on, it was not allowed anymore to read the mapper registers. 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: MegaRAM
] I have never seen a MSX2 before 1987. And this copyright doesn't mean that ] the production really started at 1985. When did you buy your 8235? ] ] I have. ] ] ] BTW, memory mapper wasn't born jointly with MSX2. Many MSX2 that I knew ] had only 64kb of RAM. Does your 8235 have internal Memory Mapper? ] ] Memory Mapper is part of the MSX2 standard. It is optional in MSX2. In MSX2+ it is mandatory. 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: MegaRAM
] That's strange. I think that it's more natural to expand memory first, and ] after expand video capabilities. ] ] Who needs more memory when all games are in ROM cartridges? ] Only people who want to play illegal versions of those ROM's... :-) Ever heard of a RAMDISK? That is something which you really need if you are working on your MSX. For example, when you are writing programs. Floppy and harddisk on MSX are too slow to be really usefull when you are constantly loading, saving, editing, assembling and the whole stuff. 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: MegaRAM
] ] My question is: why the data behavior is symmetric (pages even and pages ] odd) and the block-switching isn't, I mean, why in Konami Megaroms the ] block number can't be selected via pages 0 and 3? This mystery can be solved quite simply if you look at the specifications of the MSX slot. In a cartridge slot, you have three signals, just for the convenience of the hardware designer: CS1: This signal becomes active if the Z80 addresses memory in page 1 CS2: This signal becomes active if the Z80 addresses memory in page 2 CS12: This signal becomes active if the Z80 addresses memory in page 1 or 2 If you design a game cartridge (which is supposed to start at 0x4000) with a ROM of 16 kB, you have two options. The first option is that you ignore the CS1, CS2 and CS12 signals. In that case, your ROM will be visible in all four pages. The other option is that you use CS1 to select your rom only if the Z80 addresses page 1. In that case your rom is only visible in page 1. If you design a basic cartridge (which is supposed to start at 0x8000) with a ROM of 16 kB, you have two options. The first option is that you ignore the CS1, CS2 and CS12 signals. In that case, your ROM will be visible in all four pages. The other option is that you use CS2 to select your rom only if the Z80 addresses page 2. In that case your rom is only visible in page 2. If you design a cartridge of 32kB, you don't have much choice anymore if you want to be sure that the cartridge starts at address 0x4000. The same if you build a megarom. For both cartridge types you simply have to use the CS12 signal, to make your cartridge only visible in page 1 and page 2. Ofcourse, you might decide to ignore the CS12 signal. In that case, your cartridge will be 'mirrored' as follows: Page 1 to 3 and Page 2 to 4. Now you may wonder what is the advantage of ignoring the CSx signals. The advantage is very simple: it is cheaper as you need less logical circuits in your cartridge. You may also wonder what is the advantage of using the CSx signals: I haven't got a clue. Though, when you are designing a megarom chip anyway, you can give it a pin to connect it to the CS12 signal. Then it won't cost you any extra penny but you do have a 'cleaner' design. As you might understand, the cartridges which are 'mirrored' all over the place simply ignore the CSx signals. While the megarom cartridges, which can only be addressed in page 1 and 2, use the CS12 signal. Funny to realize that all these amazing discoveries are well documented. We should definetely get a good site up and running with all technical documentation available about the MSX. It will save a lot of people a lot of time with tracing and disassembling the MSX ROMS. 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: [Fwd: Silence!]
[EMAIL PROTECTED] schrieb: [EMAIL PROTECTED] schrieb: Alex Wulms schrieb: Shadow !!!??? Where are you ?!?!!?!? We seem to need you in here !!! Because a lot of the people in this newsgroup don't seem to mail anymore when you're not arround !!! Maybe you don't know: he has no access to the newsgroup... :( What happened? Did his boss figure out that he was spending more time on the newsgroup that on his job??? Uhmm... it's possible, cause he changed the company... He has again a mail-address, but no access to the ng :( (I hope you keep him updated with your cr.. uhm, I meant with your wonderful partial off-topics...) ;cP NO - PLEASE! Don't tell me again why there are "some" off-topics! I know - MSX is fun and to talk about it (just fun) :-' greetz JJoS -- Tilburg Team: Janosch, SGI, D-AX, inDark, Maspo, SFS, Chief-Gavaman Darn!! I have sent this message to the personal account... But I'm sure all of you wanna read this... ;cP greetz JJoS -- Tilburg Team: Janosch, SGI, D-AX, inDark, Maspo, SFS, Chief-Gavaman ARG Again wrong - should be in the newsgroup I'm really confused... -- Tilburg Team: Janosch, SGI, D-AX, inDark, Maspo, SFS, Chief-Gavaman 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/)
