PC-DC server on Vista/Win7/XP etc. (Sort of)

[segafreak2]

I've edited the registry entries to get it try and work it with the pc-dc server, but tried it with another modem (un-edited) and it still didn't work. And no, I don't have anything else running on the modem, or any software that came with it that's running (as far as I know).

I did find this link though:
http://communities.vmware.com/thread/31995

Most PCI modems are Winmodems, and are not supported in a virtual machine. If it's an external modem and plugs into the serial port, it can usually be accessed as a generic serial device from within a virtual machine.

What now?
Ha, this isn't looking possible.

[Favrenation]

I know what green uses is an internal winmodem.

[segafreak2]

Ha, I managed to work it! Use the manturion.de registry settings and it works!
The only problem is that it won't install gnome-pp, it says

E: Cannot fine gnome-ppp

or something like that.

Gonna try win98se.

BTW I have a Smart Link 56k voice modem, if anyone else has similar problems.

[brourke228]

Ha, I managed to work it! Use the manturion.de registry settings and it works!
The only problem is that it won't install gnome-pp, it says

Quote:
E: Cannot fine gnome-ppp


or something like that.

Gonna try win98se.

BTW I have a Smart Link 56k voice modem, if anyone else has similar problems.

You probably just need to update synaptic. But try searching for gnome-ppp in the GUI software manager.

[segafreak2]

OK, so I've got a few problems.

I"m doing everything as is said, a combination of the video you put up (which i'm very grateful for) and the linux guide but i'm having problems with mgetty.

When I try to establish a connection I type this in

sudo killall -USR1 mgetty

In response however I get an error message:

mgetty: no process killed

This is the log:

hugh@ubuntu:/etc/mgetty$ tail -f /var/log/mgetty/mg_ttyS1.log
10/03 19:09:36 ##### failed A_FAIL dev=ttyS1, pid=16486, caller='none', conn='', name=''

--
10/03 19:09:36 yS1 mgetty: interim release 1.1.36-Jun15
10/03 19:09:36 yS1 WARNING: parent process not init(pid=1), but pid=15944 (bash)
10/03 19:09:36 yS1 check for lockfiles
10/03 19:09:36 yS1 locking the line
10/03 19:09:36 yS1 lowering DTR to reset Modem
10/03 19:09:37 yS1 send: AT[0d]
10/03 19:09:37 yS1 waiting...^C
hugh@ubuntu:/etc/mgetty$

I'm running Ubuntu 8.10, with Dream Key 3.0 (ATX0 entered into the AT settings to make it blind dial). The only things I changed were the IPs so they were the ones on the router and my PC.

Thanks for any help.

SF2

[brourke228]

OK, so I've got a few problems.

I"m doing everything as is said, a combination of the video you put up (which i'm very grateful for) and the linux guide but i'm having problems with mgetty.

When I try to establish a connection I type this in

sudo killall -USR1 mgetty

In response however I get an error message:

mgetty: no process killed

This is the log:

hugh@ubuntu:/etc/mgetty$ tail -f /var/log/mgetty/mg_ttyS1.log
10/03 19:09:36 ##### failed A_FAIL dev=ttyS1, pid=16486, caller='none', conn='', name=''

--
10/03 19:09:36 yS1 mgetty: interim release 1.1.36-Jun15
10/03 19:09:36 yS1 WARNING: parent process not init(pid=1), but pid=15944 (bash)
10/03 19:09:36 yS1 check for lockfiles
10/03 19:09:36 yS1 locking the line
10/03 19:09:36 yS1 lowering DTR to reset Modem
10/03 19:09:37 yS1 send: AT[0d]
10/03 19:09:37 yS1 waiting...^C
hugh@ubuntu:/etc/mgetty$

I'm running Ubuntu 8.10, with Dream Key 3.0 (ATX0 entered into the AT settings to make it blind dial). The only things I changed were the IPs so they were the ones on the router and my PC.

Thanks for any help.

SF2

Before you type in the command

Code: Select all

sudo killall -USR1 mgetty

, you first need to type in the command

Code: Select all

sudo mgetty -D /dev/ttyS1 -m '"" AT'

to start mgetty in the first place. The "/dev/ttyS1" can be replaced by whichever device name your modem uses, though it is probably the same. After you start mgetty you can leave it running. But don't do the killall command until after 2.5-3 seconds after the dreamcast has started to dial. You then issue the killall command in a separate terminal window or tab and your dreamcast will negotiate the call with your PC. If you've done all this exactly as I've explained let me know, because if that's the case then most likely you've configured something wrong.

[segafreak2]

No, I did that and I still get the same 'no process killed' melachy. The DC dials for a bloody long time though, compared to normal, I don't know if that's anything to do with it.

I have noticed a few things.

For gnome-ppp, do you have to do anything other than check the modem, since there are other options (such as username/password, specifying IP and DNS addresses etc.) Also several modems are listed (ttyS0 through to ttyS3, as well as /dev/modem?

It's conceivable that it's because I'm using Dreamkey. Has anyone else got this to work with dreamkey? I tried downloading planet web but my DC couldn't read the disc, it was probably a dodgy rip.

Is there anyway we can get an installer working on this? Ha, it's not just because I'm lazy (:P) but this kind of proves that i'm quite technically inept.

Here's another log:

hugh@ubuntu:~$ tail -f /var/log/mgetty/mg_ttyS1.log
10/04 15:13:24 yS1 lock not made: lock file exists (pid=6782)
--
10/04 15:15:39 yS1 mgetty: interim release 1.1.36-Jun15
10/04 15:15:39 yS1 WARNING: parent process not init(pid=1), but pid=6837 (bash)
10/04 15:15:39 yS1 check for lockfiles
10/04 15:15:39 yS1 locking the line
10/04 15:15:40 yS1 lowering DTR to reset Modem
10/04 15:15:40 yS1 send: AT[0d]
10/04 15:15:41 yS1 waiting...
10/04 15:18:50 yS1 lock not made: lock file exists (pid=7082)

Also is it true that all you need to do every time to get it up and running is enter this:

sudo mgetty -D /dev/ttyS1 -m '"" ATM0'

...on the terminal (obviously doing things on the DC side too)?


Thank you so very much for all your help. Maybe I'll be able to play quake and PSO after all

[brourke228]

No, I did that and I still get the same 'no process killed' melachy. The DC dials for a bloody long time though, compared to normal, I don't know if that's anything to do with it.

I have noticed a few things.

For gnome-ppp, do you have to do anything other than check the modem, since there are other options (such as username/password, specifying IP and DNS addresses etc.) Also several modems are listed (ttyS0 through to ttyS3, as well as /dev/modem?

It's conceivable that it's because I'm using Dreamkey. Has anyone else got this to work with dreamkey? I tried downloading planet web but my DC couldn't read the disc, it was probably a dodgy rip.

Is there anyway we can get an installer working on this? Ha, it's not just because I'm lazy (:P) but this kind of proves that i'm quite technically inept.

Here's another log:

hugh@ubuntu:~$ tail -f /var/log/mgetty/mg_ttyS1.log
10/04 15:13:24 yS1 lock not made: lock file exists (pid=6782)
--
10/04 15:15:39 yS1 mgetty: interim release 1.1.36-Jun15
10/04 15:15:39 yS1 WARNING: parent process not init(pid=1), but pid=6837 (bash)
10/04 15:15:39 yS1 check for lockfiles
10/04 15:15:39 yS1 locking the line
10/04 15:15:40 yS1 lowering DTR to reset Modem
10/04 15:15:40 yS1 send: AT[0d]
10/04 15:15:41 yS1 waiting...
10/04 15:18:50 yS1 lock not made: lock file exists (pid=7082)

Also is it true that all you need to do every time to get it up and running is enter this:

sudo mgetty -D /dev/ttyS1 -m '"" ATM0'

...on the terminal (obviously doing things on the DC side too)?


Thank you so very much for all your help. Maybe I'll be able to play quake and PSO after all

You don't need to set anything up with gnome-ppp, just leave all the fields blank. The purpose of using that is simply to verify that a modem device appears on your computer, and also to determine what the device name is.

Yes, to start mgetty all you need to do is type the command you listed. Just be sure that the device name is the same as what's listed in gnome-ppp.

The fact that it is saying no process killed after you do the killall command, having started mgetty already leads me to believe you've configured something wrong on your computer. It has nothing to do with DC. I'm sure you've verified that you didnt make a mistake typing these commands in already. But having said that, post your 6 config files and their respective file names so I can see if you did anything incorrectly. Also before you even do that make sure you've named your options.(device) file correctly. A lot of people accidentally copy the device name used in ryochans guide. However, it is specific to your device name. Therefore if your device is called /dev/ttyS1, then that options file should be named options.ttyS1.

[Bob Dobbs]

Thanx to Green Man, I'm online. Just connected with it today using XDP. What I had to do is loose my external USR 56k Fax Modem and I put in a much newer internal voice modem made by Agere. Green Man pointed out it must be my modem, so all I did was swap the modem and then...internet. Green Man got me through it.

A Voice modem makes a difference.
Microsoft, Linux just kicked your butt!

Now, I want to do the dual modem thing so we can have another DC online.

[Favrenation]

time to play some maximum pool