Re: MSX PC local network
The PC part is probably easier than the MSX part, because you can use a language like Pascal or C to write the software and it will still be fast enough. Na, on MSX C or pascal or modula-2 will be fast enough I guess. The communication is rather straight-forward.. But transfer rate doesn't depend just on the speed of the software... Both ICs and wires introduce delays. Does anyone know how fast an average MSX joystick port is? Donno, but with a sync-signal it doesn't really matter. Don't expect very high bandwith, but we're not asking for that really (do we? As long as it works it would be nice :-) The joystick-port is implemented using the.. PSG! I don't think this chip is a wonder of speed, although it's possible to use it for digital audio at a desent quality. And take in mind that we have 2 joystick-ports, so we can have 5 data bits + 1 sync-signal. That'll be fast enough. Is the MSX parallel port bidirectional? If so, it would be ideal for data communication. No, it's not. It has only one input: printer on-line. We can use it's output capabilities 8-bit + strobe but that's it. Timing will become too hard. An other possiblity is, as I've mentioned before, the MIDI ports of PC and MSX, but this requires extra hardware. Also, MIDI will give you a low transfer rate. Enough for multiplayer games, too low for file transfers. And for multiplayer games the joystick connection is good enough. MIDI not fast enough you think? MIDI is 31.5kb/s, so faster than a 28k8 modem! There is a tetris-clone which you can play with 32 players at once, using the MusicModule as "lan". Does somebody know's how this is achived? I guess using the MIDI-IN and MIDI-OUT and a piece of software that relays the data for other computers. Using the interrupt-capabilities of the MusMod I guess it is possible to make a reliable network, in which you can hook up a PC quite easily. So, if somebody would think about transferring files using the joystickport and LPT port (perhaps even a toke-bus network using both joystickports? wha!) If you connect your joystick port 1 to one MSX and port 2 to another, you don't get a token bus network. The reason it's called token bus is that there is one bus for all nodes (computers) and the one who has the token is allowed to send. Oeps, token RING I mean.. Ok, this is what we have: -Connecting one PC to one MSX using RS232. That's possible and easy, but I guess I'm ot the only one without a RS232 interface for MSX (which are too expensive for me and for what I want to do with it) -Connecting one or more PC'es to one or more MSX'es in a real token RING (hehe) LAN using MIDI-IN and OUT. On MSX, a lot of people have a MIDI-port. MusMod, tR-GT and a bunch of others. Special drivers could be written for every module. On PC, this requires a soundcard and a (rather expensive) cable, however it's not THAT hard to make this cable yourself. Problem here is that there isn't a real standard for the MIDI-port used in all cards. I, for example, have a GUS PnP which is quite different from a SoundBlaster (fortunatly; SB stinks IMHO) although there are emulators. AND on PC we have Windows, which does provide a standard for using MIDI. I've looked at it, but it seems rather complicated to achieve raw data transfer in VC++5... Perhaps it's easier with Delphi. Using MIDI, it's possible to make a REAL LAN. Not too fast, but doesn't require rare or expensive hardware. -Connecting PC's and MSX'es using the PCs LPT port and MSXs joystickport. There is some kind of standard (could somebody give me the URL to the scheme?) for connecting 2 MSX'es and I guess it's not too hard to use a compatible standard using the LPT port. So, with standard hardware we can hook up MSX'es and PC'es together in a LAN. We only need some wires, plugs and a soldering-iron and ofcourse the software. Drawback is that on MSX this can't be interrupt-driven so you need polling which is not very suited in a token ring LAN IMHO. Looking at this, I prefer MIDI for data-transfer... Randy 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 PC local network
Alex Wulms wrote: I have an even better idea. In stead of using port1 and port2 for communication, we can also use port1 for the joystick and port2, with a device like the Ninja Tap, for communication with the neighbouring computers. Like in the following picture: +--+ +-+ +-+ +-+ | comp1p2+ mux p2ap2b mux +-p2 comp2 | | p1-+ |p2b--+ +---p2a| +-p1 | +--+ | +-+ | |+-+ | +-+ joy-stick | | joy-stick +-+ +-+ | | p p +-2-2-+ | a b | | mux | +--+--+ |+-+ +---p2 comp3 | +--p1 | | +-+ joy-stick To keep the communication driver as simple as possible, we can define one port on the multiplexer (mux) as in-only (for example p2a) and the other as out-only (for example p2b). In this case, we have to implement a token-ring network. A bus simply can't do because in a bus we need bi-directional communication for the two systems on the end. This schema can be implemented in very cheap hardware. Ofcourse, it will be a little bit more complicated then only making a cable, but I think it still is not too complicated. Or is it? Kind regards, Alex Hi all, This is what I've been waiting for. This seems (at least to me) the smartest solution. In this way the token bus could be expanded 'without end' and you wouldn't need expensive hardware. If I'm not mistaken, then the only thing you need are wires and connectors. As I have understood this discussion, the MSX has (per joystick port) 3 outputs and (for simplicity) 3 inputs (does it already ring a bell :-) ). This means that you could make a connection as follows (keep in mind that I'm only a simple programmer and don't understand data communications): +data-+ |+---clock---+| || || || +---data+ +---data+ +---data+ || || |+--clock--+| |+--clock--+| |+--clock--+| || || || || || || || || || || || || || || || || || +-ii-oo-+ +-ii-oo-+ +-ii-oo-+ +-ii-oo-+ | MSX A | | MSX B | | MSX C | | MSX X | +-o---i-+ +-o---i-+ +-o---i-+ +-o---i-+ | | | | | | | | | | | | | | | | | +--ready--+ +--ready--+ +--ready--+ | | | +ready+ In simple language this would mean that MSX N signals MSX N-1 it is ready to receive data. MSX N-1 'sees' this and sends it's data (in a sort of I2C way with a data and a clock signal) to MSX N. MSX N removes the message from the ring if it has the token, else it relays the message to MSX N+1. If MSX N has the token, it sends the next message (if any) or transfers the token to MSX N+1. Let me clarify the 'I2C way' of communicating: If MSX N signals it is ready to receive data (ready line), MSX N-1 sets the first bit on the data line and after that alters the clock line. MSX N reacts on the alternating of the clock by IMMEDIATELY reading the signal on the data line. After Xms (depends on the implementation), MSX N-1 sets the next bit on the data line and alters the clock line. MSX N reacts on the alternating of .. After reading the above again, I realize that the wait of Xms could be replaced by toggling the ready line, but this sort of detail could be worked out if the idea seems feasible. I don't know if all of this is feasible, but it seems to me that this is THE most low budget token ring bus possible for MSX. This would also mean that any MSX could be replaced by a PC (which could do the same thing via the parallel port). This would also mean an easy to use and implement driver. It would however mean that every MSX in the ring becomes slower if the bus activity increases. Hope this adds something to the discussion, Jeroen Smael FutureDisk Homepage: http://www.futuredisk.msxnet.org 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 PC local network
Hi there! From: "Randy Simons" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: MSX PC local network Date: Thu, 16 Jul 1998 17:51:13 +0200 --- cut --- MIDI not fast enough you think? MIDI is 31.5kb/s, so faster than a 28k8 modem! There is a tetris-clone which you can play with 32 players at once, using the MusicModule as "lan". Does somebody know's how this is achived? I guess using the MIDI-IN and MIDI-OUT and a piece of software that relays the data for other computers. Using the interrupt-capabilities of the MusMod I guess it is possible to make a reliable network, in which you can hook up a PC quite easily. This Tetris-clone is called 'Triplex'. I've written this game a couple of years ago. You can read more about Triplex on my homepage: www.stack.nl/~sanderk/triplem Triplex allows up to 16 players to play at once. The computers were linked up as a ring. The MIDI-OUT of computer 1 is connected to the MIDI-IN of computer 2. The MIDI-OUT of computer 2 is connected to the MIDI-IN of computer 3... Finally, the MIDI-OUT of computer n is connected to the MIDI-IN of computer 1, where n is the number of computers participating. The network structure indeed is a token ring. A token (1 byte), contained a sender and a message. The receiving, queing and forwarding of the message was taken care of by a routine which was called on interrupt-base. When the sender finally receives the token it has sent itself, the token is removed from the network. The principle is quiet simple. Our game works fine, and has resulted in many hours of fun! (You don't need fancy graphics and a fast computer to have fun. Ofcourse all of you know that... :-) Greetings, |\/\/\| |-O-O-| +-----+ | Sander Kooijmans | | | /\ | | student Technische Informatica -+- | | | | | | | |---| | | email: [EMAIL PROTECTED]|_ |__| | | http://www.stack.nl/~sanderk\/ | | | +-+ 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 PC local network
] On Thu, 16 Jul 1998 22:40:12 +0300, Alex Wulms wrote: ] ] Stupid question perhaps, but where do you plug-in the joystick ] to play the multi-user game if both joystick ports are used to ] communicate with the two neighbouring computers in the ring? ] Ha! Smart observation! ] ] Some years ago, there was at Japan an artifact called Ninja ] Tap that allowed to play up to four players with a single joystick ] port. I dunno if it would have been useful for this purpose. ] However, it is out of stocks. I gues that with a smart design (both hardware and software) we can make something like that. I have an even better idea. In stead of using port1 and port2 for communication, we can also use port1 for the joystick and port2, with a device like the Ninja Tap, for communication with the neighbouring computers. Like in the following picture: +--+ +-+ +-+ +-+ | comp1p2+ mux p2ap2b mux +-p2 comp2 | | p1-+ |p2b--+ +---p2a| +-p1 | +--+ | +-+ | |+-+ | +-+ joy-stick | | joy-stick +-+ +-+ | | p p +-2-2-+ | a b | | mux | +--+--+ |+-+ +---p2 comp3 | +--p1 | | +-+ joy-stick To keep the communication driver as simple as possible, we can define one port on the multiplexer (mux) as in-only (for example p2a) and the other as out-only (for example p2b). In this case, we have to implement a token-ring network. A bus simply can't do because in a bus we need bi-directional communication for the two systems on the end. This schema can be implemented in very cheap hardware. Ofcourse, it will be a little bit more complicated then only making a cable, but I think it still is not too complicated. Or is it? Kind regards, Alex -- 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: MSX PC local network
Hi! o When a computer wants to send, it starts it's CLOCK and waits for the receiving side to set the READY signal o Sending starts with 1 start bit (high signal) o Followed by data and odd parity o Sender waits for a drop of the READY signal for 1 clock cycle as an ACK o If it doesn't drop withing X cycles after sending the last bit a resend is in order (step 2) o If there is more data to send, return to step 2 o All data sent, stop CLOCK signal o Receiver drops READY signal Why do you want a CLOCK signal? I'm a big fan of asynchronous communication, because it's easy and robust. One way of doing asynchronous communication is a handshake. I think a 2-phase handshake is appropriate for the joystick port communication protocol. In a 2-phase handshake you have 2 control signals: - request (REQ), written by the sender - acknowledge (ACK), written by the receiver Apart from the control signals you also have a number of data signals. We have only 1 bit left, so we'll use 1 data signal. This could be a handshake cycle between computer S (sender) and R (receiver): S: write DATA S: signal REQ R: read DATA R: signal ACK A signal in a 2-phase handshake is the flipping of a bit, so the transition from '0' to '1' is a signal and the transition from '1' to '0' is another signal. To make the system more safe, we can combine DATA and REQ. It still takes 2 bits, now called DR0 and DR1 (data request). Sending a signal over DR0 means "REQ DATA=0". Sending a signal over DR1 means "REQ DATA=1". In technical terms, this is a "one-hot" code. Here is the reason that the DR0/DR1 encoding is safer than the REQ/DATA encoding: It takes some time for a signal to go through a wire. This delay depends on many factors, for example: length of the wire, temperature, material of the wire, strength of the signal. The result is that you never know how much the delay is exactly. There are two ways to combat this: - calculate a maximum for the delay - make the encoding delay-insensitive The first way is more difficult, and in this case the second way is as efficient as the first one. So I say we should go for the delay-insensitive way. Using the REQ/DATA encoding, you first send the DATA and then the REQ. But because of the delays in the wires, it's quite possible that sometimes the REQ will arrive first. If that happens, the old (invalid) data will be read and you have a transmission error. Using the DR0/DR1 encoding, you send a signal on either DR0 or DR1. Because you send only 1 signal, the wire delay doesn't matter. So this encoding is delay insensitive. Note that the protocol I described can use the same hardware that Patrick Lina proposed. The protocol only tells you how to send bits over the network. The next step would be to describe the format of a transmission. 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: MSX PC local network
] There is a game called Trip¨lex which uses the midiports of ] the music module to creat a LAN. I think you can get much ] info out of these sources ] ] so we are going back to midi again... ] What would it cost to make a midi or LAN cartridge? Too much I gues. MIDI basically has the same hardware as RS232. And most people have been complaining that they find RS232 too expensive. So, MIDI will be too expensive as well for the ones not having it yet. Kind regards, Alex -- 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: MSX PC local network
] ] -Oorspronkelijk bericht- ] Van: Alex Wulms [EMAIL PROTECTED] ] Aan: [EMAIL PROTECTED] [EMAIL PROTECTED] ] Datum: donderdag 16 juli 1998 22:42 ] Onderwerp: Re: MSX PC local network ] ] ] :Stupid question perhaps, but where do you plug-in the joystick to play the ] :multi-user game if both joystick ports are used to communicate with the two ] :neighbouring computers in the ring? ] ] It isn't nessacary to use both joystick-ports... just one will do too and ] then the other one can be used to, well err, 'play' with... ;-) Not if you want to connect more then 2 computers to each other. For example, when building a token-bus network with 15 computers, then you need both ports on the 13 machines in the middle. And if you are going to make a token-ring, all machines will use both ports for communication... Kind regards, Alex -- 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: MSX PC local network
On Mon, 20 Jul 1998, Tambet Matiisen wrote: This network adapter was not a regular cartridge. It was connected (with screws) to a special slot of Yamaha YIS-???. Module had two 5-pin They were Yamaha YIS503III, as i remember. connectors (like cassette connector). All computers were connected Connectors were more like standard pc keyboard connector. The module had its own ROM and CALL-commands (CALL NETINIT, CALL NETEND, CALL SEND, CALL RECEIVE, etc.). Teacher could send BASIC programs, Those commands were also aviable to program using special bios. binary files and even VRAM contents to other computers, while these were in BASIC. Student computers could not send files, until teacher enabled them to do so (CALL ENACOM, CALL DISCOM). CALL NETEND disconnected from Thanks Tambet for remaining me that i have more specific document about those netbios calls (written in cyrrillic): ftp://ftp.physic.ut.ee/pub/people/sagi/docs/msx/network.lzh seemed to me, that the network operated like bus - every computer could see the information sent by other computers. Even more - the student/teacher setting was only for ROM, actually all computers in the network were equal. I remember that it was not so simple. Only student computers were equal. They have the same bios, but teacher's computer (id:0) can set all properties for other computers (id: 1-15). For starting any network session, teacher's computer send a special command for computer (or group of computer) to start listen. Then teacher's machine start sending data. Another way, when student want to send his data to host computer (id:0) he simply waits for his time (host must start listen from network, but this could be set only from main console) to start sending data. Tambet (from Estonia, former Soviet Union republic) Kristian (from Estonia too) P.S. Sorry about my bad english. 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 PC local network
The Music Module midi section is based on 68B50 - chip, which is cheap. (You need ofcourse I/O-decoding, an optoisolator + clock circuit for the sync chip, but they also are cheap :-) Sincerely Kari Lammassaari Btw. The transfer rate is 31,25 Kbaud ! Joystick connection is much easier and faster ! At 07.29 17.7.1998 +0200, you wrote: There is a game called Trip¨lex which uses the midiports of the music module to creat a LAN. I think you can get much info out of these sources so we are going back to midi again... What would it cost to make a midi or LAN cartridge? greetings Maico Arts At 20:13 16/07/98 +0100, you wrote: Looking at this, I prefer MIDI for data-transfer... I'm still in favour of the joystick solution :-) 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 PC local network
Hello, Philips has made a serial-interface called NMS 1212, with one RS232-port and one RS422-port (LAN!). I had one myself (a long time ago) but had also a NMS 1210 (single RS232-port) so I sold that one... I've never seen software for that RS422-port, maybe someone else? Philips made also a NMS 1211 with two RS232-ports... --[ MARI ]-- -- Visit XSW-Magazine's HomePage at: http://www.tip.nl/users/m.broek -- M.H.M. van den Broek Molenweg 17 5342 TA Oss 0412-630653 / 0654-642288 (till 31/08/98) -- 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 PC local network
According to my information, there is a new RS232-interface in development... by Sunrise Hardware or Sunrise Swiss or so... I'm not sure... Only heard from it... It's a cartridge, just like the Philips RS232. It's allready finished and even sold on Tilburg! It's not developed by Sunrise nor Sunrise Swiss. Sunrise only manufactored it and sold it! More information about this RS232c-interface can be found at Erik Maas' Homepage: http://www.tip.nl/users/erik.maas --[ MARI ]-- 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 PC local network
According to my information, there is a new RS232-interface in development... by Sunrise Hardware or Sunrise Swiss or so... I'm not sure... Only heard from it... It's a cartridge, just like the Philips RS232. ~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: MSX PC local network
According to my information, there is a new RS232-interface in development... by Sunrise Hardware or Sunrise Swiss or so... I'm not sure... Only heard from it... It's a cartridge, just like the Philips RS232. It is already available since the MSX Fair in Tilburg last April! It is from Stichting Sunrise! Greetings Maico Arts MSX-NBNO 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 PC local network
Stupid question perhaps, but where do you plug-in the joystick to play the multi-user game if both joystick ports are used to communicate with the two neighbouring computers in the ring? 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: MSX PC local network
At 16:28 16/07/98 +0200, you wrote: Is the MSX parallel port bidirectional? If so, it would be ideal for data communication. As I've heard, the MSX parallel port has only one input pin. Ugh! =( Ricardo Jurczyk Pinheiro (\__/) Star Trek, X-Files, M. Sc in Numerical Modelling (..) _) Comics, MSX, Anime, Universidade Federal Fluminense/\/\ (Gospel Christian __ .___ _ _(m__m)_)_ _ \__ \| |\_ ___ \ / _ \ \__ \ \__ \ \_ \ | _/| |/\ \/ / /_\ \ | _/ || \ / | \ || \| |\ \/|\|| \ |` \/|\ ||_ /|___| \/\|/||_ //___ /\___ / \/ [EMAIL PROTECTED] \/ \/ \/ [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] http://www.geocities.com/SiliconValley/9822/ - ICQ UIN: 3635907 "Freedom is the right of all sentient beings." - Optimus Prime Say NO to Internet censorship! Say NO to monopolies! Say NO to Microsoft! And, why not... Say YES to Jesus Christ?! 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 PC local network
At 12:45 PM 7/16/98 +0200, you wrote: According to my information, there is a new RS232-interface in development... by Sunrise Hardware or Sunrise Swiss or so... I'm not sure... Only heard from it... It's a cartridge, just like the Philips RS232. It's already finished, it was sold at the Tilburg fair! 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: MSX PC local network
Kari Lammassaari was also makeing some kind of utility to transfer files between MSX and PC by using MSX's joystick port and PC's paraller port. (...) Has a software/cable called 'acrobat' that transform the joystick port in a RS232. You can found more information about in the web page of Genuine Network (search in Baboo or MRC, please). Using it you can connect without problems in other serial port (PC, Amiga, Mac, Atari ST, other MSX, etc...) I think, that every one of us knows that Acrobat, but I don't know anybody from Europe, that has managet to get this software. When we asked about buying this software about year ago, they said, that it is for internal markets only, maybe later... Do you know anybody ? ,_. _=_=_=_=!_MSX_!=_=_=_=_=_=_=_=_, ! A1ST ~--- - I ( o o o o o o )i /`, / .::;::; ., / :::.:.:.::::!. -=- `, ~== NYYRIKKI : [EMAIL PROTECTED] 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 PC local network
-Original Message- From: Stefano Fronteddu [EMAIL PROTECTED] I've thought about this also, and I guess it could be done without extra hardware by using the Music Module and the MIDI-port of your soundcard. I've hooked op 2 MSX's using the MIDI port of the MusicModule and managed to transfer data from one to the other computer. However, some data got lost... I have to say it was a fast experiment, using KUN-basic. So, I guess it could be made more reliable. Also, I've heard of making a RS232 interface from the joystick-port with just a few extra hardware. Unfortunatly, I've no more info on this... Perhaps it's possible to use the joystickport as MIDI interface (I've read something more about this, it could be done. But guess: no more info on this one too..) Anyone more ideas? Randy 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 PC local network
:Hello MSX world, : I have a question for You. I want to know if is it possible to make a :local network (also simply connect each other) a MSX2 with a PC with WIN95. :If it is possible, how can I do it ? What HW SW do I need ? :Thanks to all, goodbye That is not possible yet. Well, you could try using a null-modem link, but then you'll have to write all the software yourself. However, when the Z380-project is finished, the designers of it (o.a. HPN) have planned to build a network-cartridge. ~Grauw "what's o.a. in English???" 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 PC local network
] ] ] I've thought about this also, and I guess it could be done without extra ] hardware by using the Music Module and the MIDI-port of your soundcard. I've ] hooked op 2 MSX's using the MIDI port of the MusicModule and managed to ] transfer data from one to the other computer. However, some data got lost... ] ] Anyone more ideas? ] Another solution would be to buy an RS232 interface for the MSX and use some standard serial communication/modem software to transfer the data. For example using the x-modem protocol. In this case, you do not need to write anything special for the MSX or the PC. You can use all kind of already available products. 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: MSX PC local network
At 18:17 13/07/98 +0200, you wrote: I've thought about this also, and I guess it could be done without extra hardware by using the Music Module and the MIDI-port of your soundcard. I've hooked op 2 MSX's using the MIDI port of the MusicModule and managed to transfer data from one to the other computer. However, some data got lost... I have to say it was a fast experiment, using KUN-basic. So, I guess it could be made more reliable. Well, it sounds very nice! But you should have developed a quick-and-dirty 'protocol'... =) Here in Brazil we have connected 2 MSXs by the joystick port, only to play F-16 (ASCII) and F-1 Spirit 3D Special (Konami). And it worked! Also, I've heard of making a RS232 interface from the joystick-port with just a few extra hardware. Unfortunatly, I've no more info on this... Perhaps it's possible to use the joystickport as MIDI interface (I've read something more about this, it could be done. But guess: no more info on this one too..) The Japanese from G-Net have done a RS-232 interface using the joystick port. It's called Acrobat. More info at http://www.g-net.org. ByE! Ricardo Jurczyk Pinheiro (\__/) Star Trek, X-Files, M. Sc in Numerical Modelling (..) _) Comics, MSX, Anime, Universidade Federal Fluminense/\/\ (Gospel Christian __ .___ _ _(m__m)_)_ _ \__ \| |\_ ___ \ / _ \ \__ \ \__ \ \_ \ | _/| |/\ \/ / /_\ \ | _/ || \ / | \ || \| |\ \/|\|| \ |` \/|\ ||_ /|___| \/\|/||_ //___ /\___ / \/ [EMAIL PROTECTED] \/ \/ \/ [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] http://www.geocities.com/SiliconValley/9822/ - ICQ UIN: 3635907 "Freedom is the right of all sentient beings." - Optimus Prime Say NO to Internet censorship! Say NO to monopolies! Say NO to Microsoft! And, why not... Say YES to Jesus Christ?! 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 PC local network
-Oorspronkelijk bericht-
Van: Randy Simons [EMAIL PROTECTED]
Aan: [EMAIL PROTECTED] [EMAIL PROTECTED]
Datum: woensdag 15 juli 1998 22:04
Onderwerp: Re: MSX PC local network
:Really interesting, that 1212 cardridge with LAN, I never knew it existed.
:But this hardware is very rare, and even harder to get and even harder to
:get more than one. True, it would be *excellent* for what we want: a
:connection between MSX'es and PC('s).
:
:So, what we need is something that hardly requires extra hardware. Luckily,
:MSX has really nice joystickports, which can do much more than that. They
:have 2 (or 3, I don't remeber exactly) outputs, and 5 inputs.
Left/Right/Up/Down = input
Trig1/Trig2=input/output (if output selected input is not possible)
pin 8 output=output
:It shouldn't
:be too hard to wire this to the PC'es parallel port, since all you need
:is... wire! (and 2 connectors) So, we only need some software. The main
:problem here is the actual data-transfer, but since we have at least 2
:inputs on our MSX it's possible to make a synchronate-signal and one
:databit-signal. I think it's even possible to make this in pure BASIC on
the
:MSX. The PC-part is perhaps not as easy, but someone who has used the
:hardware directly won't have any trouble making this to. When things are
:made in assembly on MSX, perhaps we can get a reasonable transfer-rate.
I think that when you want to transfer data between an MSX and a PC you
should just use the normal MSX-RS232. There are alot of them, both Sony and
Philips have produced them. Also there is a new one in development.
~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/)
