| Computers Forum Index » Computer - Emulators (Apple2) » Looking for a developer to write some user interface... |
|
Page 1 of 1 |
|
| Author |
Message |
| a2retro... |
 Posted: Mon May 11, 2009 5:15 am |
|
|
|
Guest
|
To: comp.emulators.apple2
Hi all,
I integrated Spiro Trikaliotis's TFE support into Applewin a while back.
I also took the same code and integrated it into kegswin. Uthernet
emulation works fine.
I did not release the kegswin version as I never did finish the user
interface configuration code.
I doesn't look like I am going to be able to do that anytime soon given
all my other projects on the go.
Is there anyone else monitoring this list who is familiar with kegs code
and would be interested in finishing off what I started? Perhaps
releasing a patch to kegs version 0.91?
Drop me an email if your interested
Glenn |
|
|
| Back to top |
|
|
|
| Nick Westgate... |
| Posted: Mon May 11, 2009 2:18 pm |
|
|
|
Guest
|
On May 11, 10:31 pm, "a2retro" <a2re... at (no spam) a2central.com.remove-hqw-this>
wrote:
Quote: Does anyone else have updates to kegs they would like to see integrated
into a newer release?
No, but (and I haven't looked into this deeply) it would be nice to
have an option to disable the auto telnet handling for TCP serial.
Cheers,
Nick. |
|
|
| Back to top |
|
|
|
| Bill Buckels... |
| Posted: Mon May 11, 2009 4:51 pm |
|
|
|
Guest
|
"a2retro" <a2retro at (no spam) a2central.com.remove-535-this> wrote:
Quote: Perhaps releasing a patch to kegs version 0.91?
Don't patch it Glenn! Release version .92.
I didn't look at the code. What's it in? Did you just change the config
section and make the adjustments by hand? That could be handled by a readme
for now then add the UI stuff to version .93 if anyone else is interested.
Bill |
|
|
| Back to top |
|
|
|
| a2retro... |
| Posted: Mon May 11, 2009 5:31 pm |
|
|
|
Guest
|
To: Bill Buckels
Bill Buckels wrote:
Quote: "a2retro" <a2retro at (no spam) a2central.com.remove-535-this> wrote:
Perhaps releasing a patch to kegs version 0.91?
Don't patch it Glenn! Release version .92.
I didn't look at the code. What's it in? Did you just change the config
section and make the adjustments by hand? That could be handled by a readme
for now then add the UI stuff to version .93 if anyone else is interested.
Bill
Hi Bill
I would normally submit suggested changes to Kent and let him release a
new version when he was ready but it been quite some time since Kent has
released a new version. Having said that I haven't actually tried to
contact him about it (yet).
The code is standard "c". Kegs is supported under Windows, *nix and
MacOS. My changes currently would only work under Windows.
Winpcap generates a device string that needs to be fed to some of the
routines. I have my device string hard coded at the moment. The code
required to finish off the support would need to a) enable/disable the
interface and b) enumerate the interfaces via winpcap, let the user pick
the one they want and then store that in the config be be read in and
used in subsequent invocations.
Does anyone else have updates to kegs they would like to see integrated
into a newer release?
Glenn |
|
|
| Back to top |
|
|
|
| Oliver Schmidt... |
| Posted: Tue May 12, 2009 12:20 am |
|
|
|
Guest
|
Hi Glenn,
Quote: Winpcap generates a device string that needs to be fed to some of the
routines. I have my device string hard coded at the moment. The code
required to finish off the support would need to a) enable/disable the
interface and b) enumerate the interfaces via winpcap, let the user pick
the one they want and then store that in the config be be read in and
used in subsequent invocations.
An alternative might be the approach I used for Contiki - let the user
specify the IPv4 address of the interface to use:
http://contiki.cvs.sourceforge.net/viewvc/contiki/contiki-2.x/cpu/native/net/wpcap.c?view=markup
This avoids the often meaningless device strings in the UI altogether.
An IPv4 address as configuration values doesn't necessarily need an
interactive UI...
Best, Oliver |
|
|
| Back to top |
|
|
|
| a2retro... |
| Posted: Thu May 14, 2009 5:16 am |
|
|
|
Guest
|
To: ol.sc
Hi Oliver, thanks for the reply.
ol.sc wrote:
True ... I was wondering what happens for someone who uses DHCP .. the
address could be changing all the time so it could be an issue to always
have to look it up to put it on the command line?
I was thinking it might be good alternative to use some of the code you
pointed me to present some additional info to help with the interface
selection but still store the \Device\\NPF_{... in the config file
192.168.1.220 - 00-19-D1-1E-4C-FF
\Device\NPF_{26A34030-0CFE-4BD0-846C-FC6B512002F4}
(Intel(R) PRO/100 VE Network Connection (Microsoft's Packet Scheduler) )
or allow the ip address supplied to determine the \Device\NPF_ and then
store that in the config file.
Glenn |
|
|
| Back to top |
|
|
|
| Oliver Schmidt... |
| Posted: Mon May 18, 2009 11:49 pm |
|
|
|
Guest
|
Hi Glenn,
Quote: An alternative might be the approach I used for Contiki - let the user
specify the IPv4 address of the interface to use:
True ... I was wondering what happens for someone who uses DHCP .. the
address could be changing all the time so it could be an issue to always
have to look it up to put it on the command line?
Operating systems != Contiki (like i.e. Windows) don't just ask the
DHCP server for some IPv4 address. Rather they explicitly ask to
exentend the lease for the IPv4 address they already got. So in a
typical DHCP-server-on-broadband-router-SOHO-scenario the IPv4 address
of a Windows box will never change.
Best, Oliver |
|
|
| Back to top |
|
|
|
| David Wilson... |
| Posted: Tue May 19, 2009 11:01 am |
|
|
|
Guest
|
On May 19, 7:48 pm, Linards Ticmanis <ticma... at (no spam) gmx.de> wrote:
Quote: Operating systems != Contiki (like i.e. Windows) don't just ask the
DHCP server for some IPv4 address. Rather they explicitly ask to
exentend the lease for the IPv4 address they already got. So in a
typical DHCP-server-on-broadband-router-SOHO-scenario the IPv4 address
of a Windows box will never change.
...until you go on vacation and the box stays off for a while, right?
The DHCP specification states that the server should always try to
give the same address to the device each time it asks for one. The
only time this should not happen is when you have more devices than
addresses. Once all the addresses in the pool have been issued (and
possibly returned) a new device is issued the oldest unused address.
This requires that the server store the leases in permanent storage (I
had an ADSL2+ modem router that did not, so whenever it was power
cycled my computers would end up with different addresses). So yes,
turning everything off for a (long) while may well change your IP
address. |
|
|
| Back to top |
|
|
|
| Linards Ticmanis... |
| Posted: Tue May 19, 2009 1:48 pm |
|
|
|
Guest
|
Oliver Schmidt wrote:
Quote: Hi Glenn,
An alternative might be the approach I used for Contiki - let the user
specify the IPv4 address of the interface to use:
True ... I was wondering what happens for someone who uses DHCP .. the
address could be changing all the time so it could be an issue to always
have to look it up to put it on the command line?
Operating systems != Contiki (like i.e. Windows) don't just ask the
DHCP server for some IPv4 address. Rather they explicitly ask to
exentend the lease for the IPv4 address they already got. So in a
typical DHCP-server-on-broadband-router-SOHO-scenario the IPv4 address
of a Windows box will never change.
....until you go on vacation and the box stays off for a while, right?
--
Linards Ticmanis |
|
|
| Back to top |
|
|
|
| a2retro... |
| Posted: Thu May 21, 2009 2:40 am |
|
|
|
Guest
|
To: ol.sc
ol.sc wrote:
Hi Oliver, I followed your suggestion and it is now getting the adapter
to work with from the command line specified ip address.
I consider this alpha quality .. if anyone wants to try it out drop me a
line and I send you a copy of the binary.
Glenn |
|
|
| Back to top |
|
|
|
|
