home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
HATCH
/
WWIVNEWS.ZIP
/
9407_9.NWS
< prev
next >
Wrap
Text File
|
1994-07-24
|
26KB
|
501 lines
In other words, if you wanted to use that "now-antiquated" Word for Windows
or MacExcel on a PowerPC, you had to pay a penalty and use an inefficient
emulator package. As we're finding out - at least, as far as the SoftWindows
emulation is concerned - that such a method just might not cut it when it
comes to performance needs.
"JUST THE FACTS, MA'AM..."
──────────────────────────
The tests show that on the average, a Windows-equipped Power Mac 7100/66
with a $4200 price tag, delivered an amazingly s-l-o-w 10.21 MIPS, 4.36 MFLOPS,
and 0.723 MPixels. For those not up on MIPS, MFLOPS and MPixels, this level
of performance is typical of 386SX CPU's in the 10-12MHz range, and 286 CPUs
in the overdriven 20MHz range. Adding more insult to injury is the fact that
the Windows emulator supplied by Insignia not support any accellerated or
enhanced video for Windows, has no support for sound or multimedia, and lacks
the ability to utilize any other drivers not included with the emulator. Oh,
and the whole mess runs in Standard mode. No Enhanced mode, nor any Real
mode, either. 16-bit compatibility is all you get, which throws Windows
for Workgroups right in the toilet, and gives you performance that's closer
to Windows/386 than Windows 3.1.
Of course, Insignia Solutions claims that a new version of Windows for
Power Mac is in the works that will overcome these difficulties, but insiders
at Insignia say not to expect this to ship before the end of this Fall. The
revision, those insiders also warn, will only address complaints about the
existing version's lack of speed, and to offer 486 performance. Absolutely
no plans are in the works at the present to address compatibility with 32-bit
Windows apps, although the Multimedia issue "is being looked into, but will
probably require the use of the Power Mac's own sound capabilities.
Now, in all fairness, it should be noted that the Power Macs run Mac wares
at anywhere from 90% to 400% faster than on your normal 68040. Your performance
varies depending on the app in question. However, at the same time it needs
to be pointed out that quite a number of FPU-intensive Mac apps have shown
poorer performance thanks to an incompatibility between the 040-native apps
and the PowerPC's 040 FPU emulation. These apps - most specifically, Excel
for the Mac - fail to recognize the emulated FPU, and start their own
software emulation process. The end result is that these apps run anywhere
from 10% to as much as 60% *slower* than when run on a 33MHz 68040!
"AND NOW, THE RESULTS OF THAT TRIAL..."
───────────────────────────────────────
So, when you get down to brass tacks, what you're looking at is, at best,
386SX-16 performance which carries a Pentium price tag. Take your basic Power
Mac, throw in 24MB of RAM - 16MB for the SoftWindows appetite, 8MB for the
Mac OS requirements, a typically overpriced Apple multisynch monitor, the
equally overpriced Mac keyboard, and SoftWindows, your complete PowerMac
7100/66 system will run $4,200. Those wishing to sacrifice maximum performance
for savings can look at the so-called entry-level Windows-capable Power Mac
6100/60, which comes only with 16MB of RAM and a price tag of around $2,600.
With that kind of pricing and performance, it should be rather obvious whether
or not a Windows-capable Power Mac is worth buying or not. In the opinion of
this writer, the Power Mac isn't worth the cost. Granted, there will be those
die-hard Mac geeks who happen to think that these Power Macs are a really good
deal. Those people will be those who primarily use Mac apps - and eventually
PowerPC-native Mac apps, and only use one or two Windows apps for those
"rare" compatibility matters that MacinDos or an Appletalk connection used
to solve.
For the rest of us, whether we be IBM geeks or Mac geeks, the issue is whether
or not the combination is efficient enough to justify the added cost. Those
of us in the IBM world would be best suited in plunking down their cash for
a 486DX-100 or a Pentium-66, and taking what's left over and finding a used
Mac if a Mac app or two needs to be run. Apple dogmatists should purchase
a Power Mac, but avoid the added costs of Windows compatibility and spend
what's left over on a down payment on a used 486SX-25 machine for those few
DOS apps they need to run.
Bottom line is this: If Apple expects these Macs to start setting the world
on fire, then they'd better start dropping the prices and improving the
performance issues. The former insures that the normally-frugal IBM crowd
will give it more than just a curious glance, while the latter will keep
everybody happy.
───────────────┬─────────────────────────────────────────────┬───────────────
│ Type 0 Forum │
│ Edited by Omega Man (1@5282) │
└─────────────────────────────────────────────┘
[Editor's nOTE: As Wayne has mentioned in his column, lately there's been
quite a bit of debate on the various sysop subs as to the merits of adding
a QWK packet manager to stock WWIV code. During the debate, opinions for
inclusion in WWIVNews were solicited, and the following responses were
received prior to press time. Also, a net-wide poll was being taken with
regards to this question, and the results will be reprinted in the next
issue of WWIVNews, along with any other commentaries received.]
─────────────────────────────────────────────────────────────────────────────
What ever happened to the old spirit of WWIV sysops?
You know, the ones who used to fight about who had the silliest mod?
Who spent hours tweaking their boards to have something different?
Who went out of their way to find externals to install on their machines?
Now we want *everything* built into WWIV?
Somehow I don't think so If you want everything built in, and if you want to
be a lazy shit (pardon my french), go spend $200 on wildcat! This is the IDEA
of WWIV: You have an excellent basic BBS program with which to do whatever
your personal tastes dictate.
Me (1@5439)
I do believe an internal QWK mailer would be beneficial to WWIV. I have had
problems with WWIVMail/QWK, even set up correctly, odd problems that cannot be
nailed down to any specific event or happening. There is also too much fluff
in the other external QWK mailers, gee, my users download, and upload posts,
they don't need the other four screens of options that they have no idea as to
what they are for, a simple menu and a simpler setup is what is needed. It
should pack messages and send them to the user, and recieve from the user
and unpack, and use the user's default protocols and qscan setups.
Wildfire (1@5891)
[..] I'm gonna keep using WOMR and WOMR-QWK, unless Wayne comes out with an
absolute *killer* QWK. So, for that reason, I'd obviously like to see one
added to stock WWIV, but it needs to be "#define-able". It's not really
that big a deal, tho, 'cuz I can rip the offending code out, easily enough!
Wiz (1@3325)
Considering that there are problems with running some external programs with
WWIV under OS/2, it only makes sense to have an important feature such as
a QWK packet manager built into WWIV itself. The majority of system lockups
under OS/2 that occur on our company's BBS have been attributable to the
external QWK manager that we use -- specifically, WWIVMail/QWK. Since WWIV
itself has no real problems under OS/2, and in light of the upcoming WWIV for
OS/2, adding an *internal* QWK mailer to your basic WWIV source makes a whole
lot of sense, IMHO.
MicroSource Sysop (1@15136)
─────────────────────────────────────────────────────────────────────────────
Dear Editor:
With the release of NET33, WWIV network software gained the ability to gate
e-mail and posts between the different networks without much (if any) effort.
While this ability has made it much easier to interconnect the other networks
with WWIVNet, I think a side effect of this gating ability has probably
resulted in reduced registrations for the WWIV bbs software and has without
question slowed the growth of WWIVNet.
The proliferation of mini-networks has in some areas made communication between
local boards easier by allowing local connections to pass e-mail etc.. between
boards which connect to different long distance servers. These types of
connections are beneficial in that they remove some of the burden of
unnecessary traffic from the network servers.
Now for the down side of all of this: The operators of these new mini-nets
often accept any and all applicants in an effort to grow. While that growth
is good for the mini-net, it tends to be detrimental to WWIVNet in the long
run. Since new SysOps tend to join local networks before joining the national
ones, they are usually under no pressure from the NCs of the mini-nets to
register their boards or network software. In fact many of them tend to shy
away from the main networks when it becomes known that they will be required
to register in order to retain a node number.
Another catch: Due to the ease with which gating subs can be accomplished,
the new "1@1s" can and often do subscribe to the major networks then gate
anything they please into the mini-net. This makes it easier still for a
nonregistered board to receive "main network" traffic and at the same time
further reduces their incentive to register or join the larger networks.
Where is all this leading? I not sure what can be done, but based on these
observations I think all of the new "1@1s" should abide by and attempt to
uphold Wayne Bell's policy of the trial period for WWIV and WWIVNet usage.
Maintech (1@5211)
Editor's Reply:
The local "mini-nets" do in fact provide a "proving ground" for new sysops
to get their feet wet with regards to running a BBS with network access, and
managing its users as well. Once they've become confident with how everything
works, and have their users understanding how to properly use the resources
of a network, -then- the sysop should start looking into a larger, more
nationally-based network, such as WWIVNet or IceNET.
However, your last comment does need to be made clear to -everyone-, and not
just the 1@1's for these "mini-nets". If a sysop intends to stay in a WWIV
network past the trial period, Wayne requires that the program be registered.
Based on what has been brought up over some of the sysop subs of late, there
are quite a few "mini-nets" whose 1@1's are reportedly not enforcing Wayne's
requirement. While some 1@1's elect to "extend" the deadline for certain
systems depending on individual circumstances, wantonly exempting systems
from being required to register WWIV with Wayne is not an acceptable practice,
and should be refrained from in the future.
─────────────────────────────────────────────────────────────────────────────
"Nyah! My modem is faster than yours!"
We all do it, we all get a little lift by telling people how great we think
our new stuff is. This very human characteristic spilled into the networks
probably within hours of the first BBS systems and has never ended. My
particular concern is the usefulness of this practice when it spills into the
very data files that are used by the network to determine connection rates,
the BBSLIST.x files.
Let me just pull an example (this is a random selection, so don't get mad at
me for picking on particular systems)
@3250 *312-334-9092 #2400 [40841] "The Talamasca"
@3350 *313-655-8030 #14400 >!$ [30765] "Dragon's Lair"
@3351 *313-234-9242 #2400 [40732] "The Space bbs"
@3352 *313-736-5730 #9600 >!$ [40413] "Black Celebration"
@3354 *313-733-6057 #38400 >!$ [30168] "The Dojo"
@3355 ^ *313-694-9957 #57600 < !$ [11017] "The Cat's Meow"
In the above section from one of the WWIVnet BBSLIST files we see systems
listing modem speeds from 2400 to 57600. Last I checked the VFAST modems are
only recently available (though not yet standard) and have a rate of 28800.
What are these listings of 38400 and 57600 showing up for? Even 19200 is
suspicious.
Now before someone sends me email to explain that compression provides
throughput at these higher speeds, my question is this: What makes these
systems different from the systems listing 14400 or 9600? Those people
probably have very similar or even the same modem. Looking at the lists to
see who might be a potential connect or a good place to call looking for
files, etc. it gets rather confusing. The identifiers are some help, but
not a complete solution Furthermore, with the new 28800 modems on the way it
becomes more complicated and no end is in sight.
Perhaps the network software is using these inflated values in some useful way,
or perhaps some sysops feel better about themselves if they list a higher
modem rate. But the fact is, some type of standards are needed to clear things
up. If we agree that 57600 is the value we should use for a 14400 with all
it's compression, etc. great, lets get them all listed that way. If we are
going to use real rates lets do that.
As things are now, there is no rhyme or reason to any of it and as the nets
continue to grow and WWIVnet begins to interface with FIDO and perhaps other
"outside" networks these standards may become even more relevant. It seems a
simple matter to fix, we have the people in place to do it: AC's, and GC's
already handle updates of the BBSLIST files now. Simple search and replace
commands would make short work of standardizing the lists, and really who are
we trying to impress anyway? These are data files used by sysops. If people
want to advertise these high modem rates use the A)dd command on the BBS list
file on every system you log onto...that's the one users are going to look at!
Mr. Jones (1@3359)
Editor's Reply:
Personally, I've been prodding Wayne for years to add standard Warp Speed
codes to the BBSLIST files, with Impulse Power being anything below 9600,
and a -true- 115k connection being that unattainable infinite speed of Warp
10 :-)
─────────────────────────────────────────────────────────────────────────────
Dear Editor:
I have read numerous posts from sysops complaining about the order of their
subs and directories. They try to insert a new sub or directory into a
position they want them in, only to have them pop up at the end of the
conference.
It is my understanding this is being changed in 4.24, but for now, here is an
FAQ I typed up everyone using 4.23:
─────────────────────────────────────────────────────────────────────────────
The "legal" way currently (as of 4.23) is to (C)lear the entire conference
(not really a lot of fun if you have a lot of conferences, or subs or
directories in a conference).
Or, there is another way (and the way I prefer to do it). Use an editor and
edit the appropriate file (SUBS.CNF or DIRS.CNF) They are located in your
DATA directory.
When you do this, you have GOT to be careful though. I strongly urge you to
make a backup copy of them before you do it in case you mess up. It is
IMPERATIVE you use an editor that does not 'word-wrap', or put those little
smiley faces in the file for you. I use the one that comes with Borland C++.
It works very nicely.
When you open the file, you'll see a note to not edit this file, rather to use
//CONFEDIT. Ignore that part, since that is exactly what we are getting to
do. (Did I mention to back up these files before you do this?)
Next you will see something that looks like this. Of course the sub names will
be different, as will the numbers:
~A Politically-Oriented
!0 0 255 0 255 0 255 0 2 - -
@0 12 13 14 16
~B Of Interest to Sysops
!0 0 255 0 255 0 255 0 2 - -
@1 2 65 66 67 68 69 70 71 72 73 75 76 77 78 0 3 79 80 81 4 74 64
~C General
!0 0 255 0 255 0 255 0 2 - -
@0 5 6 7 8 9 10 11 14 16 17 18 26 63 82 78 19
Now, say I want to add a new sub in the General (~C) area, and I want it to be
listed second. Assume it is sub number 333. When you use //CONFEDIT to add it
in, this section will now look like this:
~C General
!0 0 255 0 255 0 255 0 2 - -
@0 5 6 7 8 9 10 11 14 16 17 18 26 63 82 78 19 333
^^^
(Did I mention to back up these files before you mess with them?)
All you need to do with your editor is take it and put it second, like this:
~C General
!0 0 255 0 255 0 255 0 2 - -
@0 5 333 6 7 8 9 10 11 14 16 17 18 26 63 82 78 19
^^^
Save the file, and wala, it is in the correct place!
─────────────────────────────────────────────────────────────────────────────
Make sure it came out like you wanted it,, then delete your backup copies of
the file(s) so that when you back them up the next time, you will not get
confused. In case I forgot to tell you, make sure you back these files up
before you go to edit them, and do NOT use an editor that will automatically
word-wrap the line when it goes beyond 80 columns, or you will not be happy!
Sam (1@2077)
Editor's Reply:
This has been tested on Klingon Empire (1@15117), and despite the fact that
it came from Sam, it worked :-) While it's not that "Official Wayne Bell
Fix" that everyone's been waiting for since //JE was added to WWIV, it'll
do just fine for now.
───────────────┬─────────────────────────────────────────────┬───────────────
│ A Net Sub Host's Best Friend - AutoSend │
│ by JAFO (1@8861) │
└─────────────────────────────────────────────┘
Have you ever subscribed to a sub and two weeks later you still have not
seen any posts on the sub? Wouldn't you rather see posts right away so you
can join in the conversation?
I've written a program called AutoSend which solves this problem. When an
auto-request comes in for one of your subs, AutoSend sends old posts to the
new subscriber so they can immediately receive posts.
AutoSend was originally meant to only send old posts, but it has grown into
a full-featured sub host utility. Here are some of its features:
- Graphical packet scanner, which allows you to view packets as they
arrive on your system. The display rate for the viewer is configurable
and you can turn it off if you want.
- Sends old posts to new subscribers. This is the main and original
purpose of AutoSend.
- Keeps log of amount of posts sent. This lets you see who is requesting
your subs and shows you the number/size of posts sent out.
- Posts sub rules on new subscriber's system.
- Posts subscription lists. The colors for the subscription lists are
completely configurable. AutoSend lets you set up a date to post
subscription lists, so you never have to worry about doing it.
- Posts new subscriber lists. AutoSend will track new subscribers for subs
you host. You can track new subscribers for each sub by month or by the
week. AutoSend will automatically post these new subscriber listings on
the first day of each week or month. This feature is in v1.14, which
will be released when WWIV v4.24 comes out.
- Posts sub ads, rules, etc. on any sub. This feature lets you post >any<
text file on >any< sub you have. Do you have sub ads? Post them on all
of the Yellow Pages subs you carry! You can also post your sub rules
too! AutoSend lets you assign certain dates to post certain text files,
and posts them on those days automatically. You can even set up AutoSend
to post a message every day if you would like.
- Removes unknown systems from N*.NET files and keeps a log. This keeps
your host data files clean. This feature also sorts your N*.NET files.
- Returns dead network e-mail to sender. If e-mail to unknown systems are
found in your DEAD.NET, AutoSend will return the e-mail to the sender so
they know that they're mail was undeliverable.
- Sends e-mail to sub host if dead posts are found. If dead posts are
found in your DEAD.NET, the sub host for the various subs are notified
that they have unknown systems in their host data files. Of course, if
you're using AutoSend you will rarely get these messages, since it
removes unknown systems from your data files automatically.
- Keeps detailed error log if any errors occur. The error log tells you
specifically what the error was and where it occured.
- Configuration program for ease of use. This program is completely
graphical and lets you edit most of AutoSend's features. One of the
best features is the ability to configure the subscription list colors
on screen.
- WWIV v4.23+ multi-instance compatible. As of this writing, AutoSend has
also been updated to work with WWIV v4.24 and its new messaging stuff.
This new version is v1.14 and will be released when WWIV v4.24 comes out.
Of course, everything in AutoSend is completely configurable. If you don't
want to use certain features, you don't have to.
Most people who are using AutoSend agree that it is one of the most useful
network utilities around. I have only heard positive things about AutoSend
from day one.
Here are some things AutoSend users have said:
─────────────────────────────────────────────────────────────────────────────
"I think AUTOSEND is the best WWIV utility program that was ever written!
It saves me COUNTLESS hours of work, and it's TOTALLY automated! It scans my
packets, sends out messages, gives me subscriber lists of all of the subs that
I host once a month, and now even automatically posts ads for subs that I host
in the WWIVnet Yellow Pages!"
"It is only something like $15 to register the program, and it's worth ten
times that amount! If you host a sub (or LOTS of subs) and haven't checked
out this program, give it a shot! If you don't like it `I'll eat a bug'!"
Robert Griffith #1 @7729
"I agree! AutoSend would be perfect to include with WWIV and/or NETxx
releases. It's the perfect sub-host utility. It could also be used to post
FAQ's in some of the subs, eliminating some of the useless repeat-questions
that pop up once in a while. :)"
Chris #1 @2914
"And thanks for replying to my posts and trying to explain it to me. Also
thanks for working on it for us. I am still telling others how great AutoSend
works. I think anyone hosting a sub should be using it."
Chat Cat #2 @5211
─────────────────────────────────────────────────────────────────────────────
AutoSend is currently being used by over 300 sysops. If you haven't seen it
being used to post sub ads and subscription lists, you probably will soon.
Perhaps you should pick up a copy and try it yourself!
AutoSend is shareware and costs $15 to register. Registration does not really
give you any extra features because AutoSend is not crippleware, but you do
get a lot for your money.
If you want more information about AutoSend, feel free to e-mail me. The
current version is v1.13. There is a sub set up for support of AutoSend and
my other programs. The sub type is JAFOSUP on every network that my BBS (Blue
Thunder) is on. You can find AutoSend on most WWIV Support BBSs and on my BBS
as well. You can reach my BBS by calling (818) 848-4101 or my second line at
(818) 848-4350.
───────────────┬─────────────────────────────────────────────┬───────────────
│ POSSE COMITATUS ACTIVITY ON WWIVNET? │
│ Mr. Natural (1@8262) │
└─────────────────────────────────────────────┘
[Editor's nOTE: This guest editorial by Mr. Natural asks more than just
the question of whether or not racist, seditionist, or anarchial activity
should be allowed over the WWIV networks, but whether or not they should
be used for any sort of questionable sales practices. As this is a very
sticky topic, considering the recent "Green Card Lottery" fiasco on the
Internet, and the White Supremacy debates on Prodigy, your responses to
the questions raised by this editorial are hereby solicited.]
─────────────────────────────────────────────────────────────────────────────
There has been some activity being promoted on a WWIVnet subboard that strikes
me as illegal, and I thought I ought to call someone's attention to it.
There has been a fair amount of activity on a political netted subboard by
white supremacists. One of these white supremacists is a member of a tax-
protest and survivalist group that has historically been associated with
crimes including the unlicensed practice of law - the specific violation I
think I observed - and far worse, including homicide.
This group calls itself "Posse Comitatus." It takes its inspiration from the
old Sheriff's posses familiar from Wild West movies, and from a Federal law
forbidding military intervention in civilian law enforcement.
They espouse a belief system that, however unlikely it seems, can only be