[FlexNet] RE: UNFLEXABLE-NET?

Wed, 9 Oct 2002 18:16:15 -0400

WOW! I think you missed the point of what I was saying.

There's no need to get so defensive.

Your absolutely right about The FLEXNET nodes and ,also, our German
foreign national friends  are absolutely wonderful in what they have
produced!

I am trying to express that there is no desent software for the END-USER
using a soundcards that that's easy to set up. This is from an END-USER
point of view not a SYSTEMS PROGRAMMING/ENGINEERING/ADMINISTRATION point
of view.

I think the problem is I'm not looking to run a node right now. I just
want a decent terminal program that will run AX.25 TCP/IP through my
sound card to my rig.

Also,Thanks for making me understand how FLEXNET is unshackably tied to
the DOS platform. I believe FLEXNET is not for me.=20

I must apologize for putting you on the defensive. Back in the late 70s
when I was troubleshooting problems for ARPANET communications, open and
honest opinions where welcome.I'm a disabled AMERICAN veteran, my neck
and back are broke. I can't just run all over the place and put a system
together and then spend hours messing with MicroBill's OS. =20

ONE LAST SHOOT, Now that my German_Irish temperment has stirred. Change
the NAME of FLEXNET, so sternly defended, to UNFLEXABLE-NET.

NOTE: If the SYSOP for this list is reading this email delete my address
from this list...73

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of John Papson
Sent: Wednesday, October 09, 2002 4:40 PM
To: '[email protected]'
Subject: RE: [FlexNet] New Flex32

Richard:

Don't beat the hell out of the FlexNet folks in Darmstadt just because
Micro$oft=20
keeps changing their Window$ operating system on a yearly basis !

The PC FlexNet DOS version is working perfectly at almost 100 node
sites,=20
running a stable network now covering 8 states in the Northeastern USA.

Don't expect FlexNet running under Window$ to operate as a node, PERIOD
!

Pull a junk computer off your pile, load Window$ 95, and get that
working for your end user station for starters...

Then move up to Win-98 which is vastly different, followed by Win-2000,
Win NT,=20
Win-Me, Win-$$$...    Do it one step at a time...

I don't have answers to your questions, as Window$ changes faster than=20
the volunteers (mostly students ?) writing FlexNet software can keep up
!

The Europeans don't give a damn about Window$, as they have jumped=20
aboard the LINUX bandwagon with both feet !

With Wal-Mart selling a $199.99 LINUX based PC, perhaps they are correct
!=20

73

John WB2CIK

=20
> -----Original Message-----
> From:	Richard Stern [SMTP:[email protected]]
> Sent:	Wednesday, October 09, 2002 3:44 PM
> To:	[email protected]
> Subject:	RE: [FlexNet] New Flex32
>=20
> KRASSI,
>=20
> I have been trying to get SV2AGW to work with my WinMe system. It says

> it can't find the TCP/IP modules. When I use it in conjunction with=20
> WinPack V6.8. It seems to operate ok with the UISS.exe for APRS. But,=20
> it's not seeing TCP/IP...
>=20
> I built a rig/soundcard interface for PTT USING EITHER RTS or DTR from

> the PC's COM port and switching between port ONE(1) and TWO(2); which=20
> also works fine with UISS.exe(freeware). I actually get the AFSK from=20
> the soundcard output after my PTT has been activated. This application

> took very little time to get up and running. The large amount of time=20
> was spent on building the PC/SOUNDCARD interface and testing it. I did

> not have to write a thesis about configuration problems and possible=20
> fixes to get UISS.EXE to operate with Windows O/S. (ANY WINDOW'S O/S).

> It seems to me that the programmer for UISS.EXE has whipped that=20
> problem. The only draw back is it's for APRS and I don't think it=20
> deals with the TCP/IP stack.
>=20
> "There lies the rub". How to manipulate the TCP/IP protocol in a=20
> Window's environment. A PDF document called "winsm.pdf" only begins to

> describe the configuration changes to Window's O/S needed to get=20
> FLEX-NET to operate in the Window's environment. I stumbled on to this

> document after going through all the English documentation, "Winsm.pdf

> is only released in the German language. I was able to roughly=20
> translate it and had my translation verified by a couple hardworking=20
> guys connected with the FLEX-NET project. (Thanks Guys!!!)This is=20
> probably the first document that needs to be read if your going to=20
> start configuring FLEX NET for Windows. BUT, there is no exact English

> translation. I do mean EXACT.! Because, you lose a lot of important=20
> little tidbits if it is sloppily translated.
>=20
>  I've been struggling to get FLEX-NET to operate. as an END-USER=20
> Soundcard TNC with Windows OS. I've been bouncing back and forth=20
> between the two applications FLEX NET and AGW packet with WINPACK.exe.

> But, no one has given me any concrete ways to get any of the apps up=20
> and running.
>=20
>  I can only load through Windows ME unless I formatted a FAT16=20
> partition to run MSDOS6.22 because Winme does NOT have a real DOS O/S.

> This will enable the PC to run the DOS version of FLEX-NET. It has=20
> some sort of WinME PSEUDO-DOS that only runs on FAT32 format. THE DOS=20
> SHELL is now what WinME only uses for DOS. So, I've tried to boot from

> a formatted disk by the START-UP DISK routine.
>=20
> There doesn't seem to be a way to format a disk using the command <=20
> FORMAT /s >. If you try through the DOS SHELL, a system message comes=20
> back that says 'WINME does not support the <FORMAT /s> command=20
> anymore'. Directed to the CONROL PANEL, go to "Add/Remove Programs"=20
> option to make a START-UP floppy. Stripping the files from the floppy=20
> and adding DOS commands that work with WIN-ME DOS and FLEXNET. I have=20
> a FLEX-NET boot file that boots with no problems through the SHELL.=20
> However, when booting from the floppy FLEX-NET won't accept the=20
> SOUNDCARD configuration from the SET BLASTER COMMAND given from=20
> AUTOEXEC.BAT before the FLEX-NET BAT file loads.
>=20
> I have a CREATIVE SOUND BLASTER PCI512. The card has an EMU10K1, "a=20
> new processor from E-mu Systems based on E-mu's highly acclaimed=20
> Emulator IV sound module." So says, the Hype B.S. in the installation=20
> manual. When loaded it shows the full blown SB version at=20
> IRQ-5/ADDRESS [B000]and a SB16 EMULATOR loaded at ADDRESS 220/IRQ-7 in

> the system settings. I have tried to boot using either IRQ7 or IRQ5=20
> SoundBlaster with the respective FLEX NET Modem module in the FLEX-NET

> BATCH FILE to boot. I have documented all the different=20
> reconfigurations I've tried have failed to find the proper SOUNDCARD=20
> Address for FLEX-NET.BAT .
>=20
> SOUNDBLASTER driver loads with no errors. FLEX-NET Kernel is activated

> and no errors occur. SMMIXER.EXE loads and outputs its setting OK.(I=20
> have <ECHO OFF> and <PAUSE> after each module loads . So, I can see=20
> which modules are giving me errors and see the configuration feedback=20
> to the Display(stdio).) When it gets to "THE FIRMWARE EMULATOR" Module

> TFEMU.EXE an error halts the process. THE CREATIVE SB cannot be found=20
> at the address given. I used both addresses for the soundcard with the

> same result.
>=20
>  It does get a little complicated but I kept track of my configuration

> procedures by noting them down with each step. I am determined to get=20
> one of these packages to work with my system which has no problems=20
> operating with ANY other software I use. I don't want to go out and=20
> buy another "Black Box" to clutter up my shack.
>=20
> All the FLEX-Net nodes are running under DOS. All the Terminal=20
> programs are configured to run in a DOS environment. So all the=20
> END-USER apps are for DOS OS as well. I have had to do a lot of=20
> digging to get a straight answer to that. Because when I mention=20
> Window's, It seems like the sysops start talking about OLD versions of

> Windows and with a full DOS OS. I can't seem to make them understand=20
> that the future of Micro Bill's OS does not want to support DOS=20
> anymore.
>=20
> If FLEX-NET wants to have a future it must start to support the=20
> WINDOWS END-USER. Does is great for nodes because you can use a cheap=20
> PC to support it but the END-USERS who don't want to be a Node and use

> the FLEX-NET WAN(Wide Area Net) need a windows end-user's application,

> using the soundcard, that's easy to configure and attaches to the=20
> Windows TCP/IP drivers. The Future is HERE and IT's running=20
> PSEUDO-DOS! In the next year or so; it's bye!...bye! DOS. This should=20
> make some vendors selling MS-DOS OS separately happy.
>=20
> At this moment, My options have scaled down. I believe one of the=20
> FLEXNET sysops told me I'd be wasting my time. I didn't believe him.=20
> Because, I thought if the application was using the sound card it must

> be able to use Windows. My efforts did get me the "BIG PICTURE". I=20
> find that FLEXNET has a great NETWORK but there is a lack of focus on=20
> END-USER applications for soundcards. I don't want to be a FLEXNET=20
> system administrator. I'm retired due to health. One of my "And Other=20
> Duties Assigned"-functions was to be a UNIX system admin. No, I don't=20
> want to do that at the moment. I just want to get on the FLEXNET=20
> interstate and drive! Is this possible?
>=20
>=20
>=20
>=20
>=20
> Peninsula Radio Operators Society=20
> http://www.intercom.net/npo/pros/index.html
> http://mailman.qth.net/mailman/listinfo/PROS
> No Fat in our HAM-LINKS!
> Webmaster: NW3N (FISTS ARLHS MARS ARRL)
>=20
_______________________________________________
FlexNet mailing list
[email protected] http://mailman.qth.net/mailman/listinfo/flexnet