[FlexNet] New Flex32

[John Papson]

Richard:

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

The PC FlexNet DOS version is working perfectly at almost 100 node sites, 
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, 
Win-Me, Win-$$$...    Do it one step at a time...

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

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

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

73

John WB2CIK

 
> -----Original Message-----
> From:	Richard Stern [SMTP:rstern@intercom.net]
> Sent:	Wednesday, October 09, 2002 3:44 PM
> To:	flexnet@mailman.qth.net
> Subject:	RE: [FlexNet] New Flex32
> 
> KRASSI,
> 
> 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
> WinPack V6.8. It seems to operate ok with the UISS.exe for APRS. But,
> it's not seeing TCP/IP...
> 
> 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
> also works fine with UISS.exe(freeware). I actually get the AFSK from
> 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
> was spent on building the PC/SOUNDCARD interface and testing it. I did
> not have to write a thesis about configuration problems and possible
> 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
> problem. The only draw back is it's for APRS and I don't think it deals
> with the TCP/IP stack. 
> 
> "There lies the rub". How to manipulate the TCP/IP protocol in a
> Window's environment. A PDF document called "winsm.pdf" only begins to
> describe the configuration changes to Window's O/S needed to get
> 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 translate
> it and had my translation verified by a couple hardworking guys
> connected with the FLEX-NET project. (Thanks Guys!!!)This is probably
> the first document that needs to be read if your going to start
> configuring FLEX NET for Windows. BUT, there is no exact English
> translation. I do mean EXACT.! Because, you lose a lot of important
> little tidbits if it is sloppily translated.
> 
>  I've been struggling to get FLEX-NET to operate. as an END-USER
> Soundcard TNC with Windows OS. I've been bouncing back and forth 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 and
> running.
> 
>  I can only load through Windows ME unless I formatted a FAT16 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 some sort of
> WinME PSEUDO-DOS that only runs on FAT32 format. THE DOS 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. 
> 
> There doesn't seem to be a way to format a disk using the command <
> FORMAT /s >. If you try through the DOS SHELL, a system message comes
> back that says 'WINME does not support the <FORMAT /s> command anymore'.
> Directed to the CONROL PANEL, go to "Add/Remove Programs" option to make
> a START-UP floppy. Stripping the files from the floppy and adding DOS
> commands that work with WIN-ME DOS and FLEXNET. I have a FLEX-NET boot
> file that boots with no problems through the SHELL. However, when
> booting from the floppy FLEX-NET won't accept the SOUNDCARD
> configuration from the SET BLASTER COMMAND given from AUTOEXEC.BAT
> before the FLEX-NET BAT file loads. 
> 
> I have a CREATIVE SOUND BLASTER PCI512. The card has an EMU10K1, "a new
> processor from E-mu Systems based on E-mu's highly acclaimed Emulator IV
> sound module." So says, the Hype B.S. in the installation manual. When
> loaded it shows the full blown SB version at 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 SoundBlaster with the respective
> FLEX NET Modem module in the FLEX-NET BATCH FILE to boot. I have
> documented all the different reconfigurations I've tried have failed to
> find the proper SOUNDCARD Address for FLEX-NET.BAT .
> 
> SOUNDBLASTER driver loads with no errors. FLEX-NET Kernel is activated
> and no errors occur. SMMIXER.EXE loads and outputs its setting OK.(I
> have <ECHO OFF> and <PAUSE> after each module loads . So, I can see
> which modules are giving me errors and see the configuration feedback 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 at
> the address given. I used both addresses for the soundcard with the same
> result.
> 
>  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
> one of these packages to work with my system which has no problems
> operating with ANY other software I use. I don't want to go out and buy
> another "Black Box" to clutter up my shack.
> 
> All the FLEX-Net nodes are running under DOS. All the Terminal programs
> are configured to run in a DOS environment. So all the END-USER apps are
> for DOS OS as well. I have had to do a lot of digging to get a straight
> answer to that. Because when I mention 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 that the future of Micro Bill's
> OS does not want to support DOS anymore.
> 
> If FLEX-NET wants to have a future it must start to support the WINDOWS
> END-USER. Does is great for nodes because you can use a cheap 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 Windows
> TCP/IP drivers. The Future is HERE and IT's running PSEUDO-DOS! In the
> next year or so; it's bye!...bye! DOS. This should make some vendors
> selling MS-DOS OS separately happy.
> 
> At this moment, My options have scaled down. I believe one of the
> FLEXNET sysops told me I'd be wasting my time. I didn't believe him.
> 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 find
> that FLEXNET has a great NETWORK but there is a lack of focus on
> END-USER applications for soundcards. I don't want to be a FLEXNET
> system administrator. I'm retired due to health. One of my "And Other
> Duties Assigned"-functions was to be a UNIX system admin. No, I don't
> want to do that at the moment. I just want to get on the FLEXNET
> interstate and drive! Is this possible?
> 
> 
> 
> 
> 
> Peninsula Radio Operators Society
> 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)
>