I'm looking for either source code for daynbr.exe, or (even better)
a winodws 32/64 bit version. I know of daynbrw.exe, but it doesn't
have a full commandline set of instructions, so doesn't work for
what I want. Appreciate any help in this direction!

i have never seen sources for the dos daynbr tool... however, it isn't really needed if you have something (ie: 4DOS/4OS2/4NT) that can generate the dayofyear number... some folks mistakenly call this the julian day number...


in any case, the best thing i like about daynbr is that it is easy to denote the number @### and doesn't require something like %_DOY% which really isn't all that bad... another positive is that it can do some rudimentary math on the
doy number, too... i have, somewhere around here, replicated most all of this in 4DOS bat/btm files but i haven't seen it in a very long time... might be easier to just write a replacement from scratch :?

speaking of writing from scratch, if you do pascal, then you might want to look
at FPC (FreePasCal) which is cross-platform and multi-bits... i'm pretty sure they have some library code that can (easily?) handle this and even the maths stuffs :)

)\/(ark


* Origin: (1:3634/12)

Hi mark -- on Aug 27 2012 at 15:50, you wrote:

i have never seen sources for the dos daynbr tool... however, it
isn't really needed if you have something (ie: 4DOS/4OS2/4NT) that
can generate the dayofyear number... some folks mistakenly call this
the julian day number...

Thanks, Mark -- no, it has to be Windows 32/64 bit.

in any case, the best thing i like about daynbr is that it is easy
to denote the number @### and doesn't require something like %_DOY%
which really isn't all that bad... another positive is that it can
do some rudimentary math on the doy number, too... i have, somewhere
around here, replicated most all of this in 4DOS bat/btm files but i haven't seen it in a very long time... might be easier to just write
a replacement from scratch :?

It may be - my programmer friend was hoping for a starting point. :-)

speaking of writing from scratch, if you do pascal, then you might
want to look at FPC (FreePasCal) which is cross-platform and
multi-bits... i'm pretty sure they have some library code that can (easily?) handle this and even the maths stuffs :)

Thanks kindly!


Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

i have never seen sources for the dos daynbr tool... however, it
isn't really needed if you have something (ie: 4DOS/4OS2/4NT) that
can generate the dayofyear number... some folks mistakenly call this
the julian day number...

Thanks, Mark -- no, it has to be Windows 32/64 bit.

hummm... may i ask why? a limitation of the OS' console operations? i don't know how far 4DOS/4OS2/4NT has gone but there may be a 32bit build of them...

in any case, the best thing i like about daynbr is that it is easy
to denote the number @### and doesn't require something like %_DOY%
which really isn't all that bad... another positive is that it can
do some rudimentary math on the doy number, too... i have, somewhere
around here, replicated most all of this in 4DOS bat/btm files but i haven't seen it in a very long time... might be easier to just write
a replacement from scratch :?

It may be - my programmer friend was hoping for a starting point.
:-)

ahhh... other than a simple DOY tool? ;)

speaking of writing from scratch, if you do pascal, then you might
want to look at FPC (FreePasCal) which is cross-platform and
multi-bits... i'm pretty sure they have some library code that can (easily?) handle this and even the maths stuffs :)

Thanks kindly!

TBH, this is one of the things that i've been looking at, myself... i've been working on a tool to merge satellite TLEs and some of this date stuff has come into play... especially on the "outside" when the daily archive is archived... but with the routines i'm using, i can easily see where feeding a full date can/will result in a DOY number being returned... at that point, it is just a matter of relatively duplicating daynbr... the biggest thing i see as a drawback is that daynbr is a shell program... by that i'm meaning that it does the doy calcs and formatting on the @### items found on the command line and then it shells out to another console to do the actual work and feeds that math
@### calculation to the shelled task in the same manner that i was thinking of just setting an environment variable to the needed doy variable...

i hope that makes sense and may also offer some assistance to the task you are looking at...

FWIW: everything, other than the new coding of an app for this, is all 16bit stuff... everything in BATPOWER that might help you seems to be but it is possible that i've overlooked something...

)\/(ark


* Origin: (1:3634/12)

Hi! mark,

In a message to Dallas Hinton you wrote:

FWIW: everything, other than the new coding of an app for this, is
all 16bit stuff... everything in BATPOWER that might help you seems
to be but it is possible that i've overlooked something...

Just a guess... I think the poor fellow is having trouble with the so-called 'advanced' version of Windows, on the loose these days. Any old DOS tools that
might have set/changed a DOS %envar% no longer works. There is a way around it...

Cheers,
Paul.

---
* Origin: You're twisted and sick, I like that in a person. (3:640/384)

Hi mark -- on Aug 27 2012 at 23:16, you wrote:

Thanks, Mark -- no, it has to be Windows 32/64 bit.

hummm... may i ask why? a limitation of the OS' console operations?
i don't know how far 4DOS/4OS2/4NT has gone but there may be a 32bit
build of them...

It's what I run on my desktop. Simple!

ahhh... other than a simple DOY tool? ;)

If we change to something other than daynbr, then several batch files will have
to be rewritten -- rather a pain!

drawback is that daynbr is a shell program... by that i'm meaning
that it does the doy calcs and formatting on the @### items found on
the command line and then it shells out to another console to do the
actual work and feeds that math @### calculation to the shelled task
in the same manner that i was thinking of just setting an
environment variable to the needed doy variable...

There's several routines for getting that number, but as I say, a complete rewrite of the existing batch files.

i hope that makes sense and may also offer some assistance to the
task you are looking at...

FWIW: everything, other than the new coding of an app for this, is
all 16bit stuff... everything in BATPOWER that might help you seems
to be but it is possible that i've overlooked something...

That's the other possibility - batch files work, and maybe I can write a daynbr.bat to take the equivalent parameters.


Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

Hi Paul -- on Aug 28 2012 at 14:43, you wrote:

Just a guess... I think the poor fellow is having trouble with the so-called 'advanced' version of Windows, on the loose these days.
Any old DOS tools that might have set/changed a DOS %envar% no
longer works. There is a way around it...

Nice idea, but no. The problem is that I'm running 64 bit, so 16 bit stuff no longer works at all (at least, not without running a virtual machine, which I'm
trying to avoid).

Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

Hi! Dallas,

On Tue, 28 Aug 12, you wrote to me:

Any old DOS tools that might have set/changed a DOS %envar% no longer
works. There is a way around it...

Nice idea, but no. The problem is that I'm running 64 bit, so 16 bit
stuff no longer works at all (at least, not without running a virtual machine, which I'm trying to avoid).

Oh, okay. In that case I say 'suck it up', whoosie. :) VMs are the way; there are many benefits with minimal risks.

Cheers,
Paul.

---
* Origin: A system event? Wow! Can I get tickets? (3:640/384)

FWIW: everything, other than the new coding of an app for this, is
all 16bit stuff... everything in BATPOWER that might help you seems
to be but it is possible that i've overlooked something...

Just a guess... I think the poor fellow is having trouble with the so-called 'advanced' version of Windows, on the loose these days.
Any old DOS tools that might have set/changed a DOS %envar% no
longer works. There is a way around it...

yep... even if the tool does nothing but to emit the DoY number...

eg:

@echo off
echo checking the DoY...
echo set doy=>doy.bat
whatdoy>>doy.bat
echo setting the DoY...
call doy.bat
echo the current DoY is %doy
:end

that should still work... the key factor being that the output from the ficticious whatdoy tool is written to stdout so that it can be redirected to the .bat file which is called later...

of course, one might also look at what might be done with the winwhatever scripting stuff... i've always had a large central main controlling .BAT file... in my environment, it could be converted to REXX which is another scripting language available on my system... i would imagine that winwhatever's
scripting stuff should be able to do the same? what's it called? VBS?

)\/(ark


* Origin: (1:3634/12)

Thanks, Mark -- no, it has to be Windows 32/64 bit.

hummm... may i ask why? a limitation of the OS' console operations?
i don't know how far 4DOS/4OS2/4NT has gone but there may be a 32bit
build of them...

It's what I run on my desktop. Simple!

:)

ahhh... other than a simple DOY tool? ;)

If we change to something other than daynbr, then several batch
files will have to be rewritten -- rather a pain!

i know what you mean about "fixing" a working system...

drawback is that daynbr is a shell program... by that i'm meaning
that it does the doy calcs and formatting on the @### items found on
the command line and then it shells out to another console to do the
actual work and feeds that math @### calculation to the shelled task
in the same manner that i was thinking of just setting an
environment variable to the needed doy variable...

There's several routines for getting that number, but as I say, a
complete rewrite of the existing batch files.

hummm... bear with me... this is kinda a "stream of consciousness" flow...

[current DoY]

daynbr echo @###

DAYNBR -- Version 1.0
Copyrignt (c) 1985 by Ben Baker
Released for noncommercial distribution

Executing 'echo 241'

241

echo %_doy

241

[DoY seven days ago]

daynbr /-7 echo @###

DAYNBR -- Version 1.0
Copyrignt (c) 1985 by Ben Baker
Released for noncommercial distribution

Executing 'echo 234'

234

echo %@EVAL[%_DOY-7]

234

so those are relatively easy general DoY things... however, figuring the DoY for a specific weekday like a sunday or a friday may slightly more complicated depending on what you want or need to do... hummm... check this created on the fly monstrousity... it looks complicated but it isn't as bad as it looks... the
following is all one long line but i'll break it apart here for easier reading...

for %i in (-7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7) do echo
%@IF[
'%@DOW[%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]]]' EQ 'Fri',
%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]] is a
%@DOW[%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]]] YaaY!!! DoY =
%@DOY[%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]]],
%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]] is a
%@DOW[%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]]] Booo...
]

i'm using the %@IF[condition,true,false] function and the true and false stuff is the same so as to print the calculated date and day... their deviation comes
at "YaaY!!!" or "Booo..." plus the true result (YaaY!!!) prints the DoY for that date... this all wrapped in a simple FOR loop feeding the numbers into the
%i variable to subtract or add X to today's date... to do that we have to work with the number of days since the epoch date of 01-01-80 so that's why there's all that messy MAKEDATE stuff in there... it gets easier further below ;)

the output is...
08-21-12 is a Tue. Booo...
08-22-12 is a Wed. Booo...
08-23-12 is a Thu. Booo...
08-24-12 is a Fri. YaaY!!! DoY = 237
08-25-12 is a Sat. Booo...
08-26-12 is a Sun. Booo...
08-27-12 is a Mon. Booo...
08-28-12 is a Tue. Booo...
08-29-12 is a Wed. Booo...
08-30-12 is a Thu. Booo...
08-31-12 is a Fri. YaaY!!! DoY = 244
09-01-12 is a Sat. Booo...
09-02-12 is a Sun. Booo...
09-03-12 is a Mon. Booo...
09-04-12 is a Tue. Booo...

so we can mimic daynbr's /Dx where x is 0 thru 6... with a similar "formula" (wow... never would have thought of it as a formula but i guess that is what it
is) using the DoWI function and/or variable... so the condition in the above would use the DoWI function and go from this

'%@DOW[%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]]]' EQ 'Fri'

to this

'%@DOWI[%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]]]' EQ '6'

but that's one (1) based... if we want it zero (0) based like daynbr, then we need an @EVAL[] wrapped around that to subtract one (1) from the result and then drop the 6 back to 5 for the comparison...

'%@EVAL[%@DOWI[%@MAKEDATE[%@EVAL[%@DATE[%_date]+%i]]]-1]' EQ '5'

so... in this example, i've done a MAKEDATE of a date (today +- 0 thru 7) so we
can see what they were seven (7) days ago, today and seven (7) from today... we
calculate the DoWI (Day of Week Integer) on that date... then we subtract one (1) from DoW Integer to zero (0) base it...

now here's a much shorter version without all the MAKEDATE date calculation stuff needed to add or subtract a random X from a date... this one checks today's DoWI _only_... it is zero (0) based like daynbr's is... again, broken apart for readability but it is all one long line...

echo %@IF[
'%@EVAL[%_DOWI-1]' EQ '5',
%_date is a %@DOW[%_date]. YaaY!!! DoY = %@DOY[%_date],
%_date is a %@DOW[%_date]. Booo...
]

08-28-12 is a Tue. Booo...


now that we can see the basics and how it may be used, we can do something simple like this to work with today's info only ;)

rem see if today is friday via _DOWI. equal to daynbr /d5 some.bat @###
rem but here, we just set dodiff to the DoY or no vs calling some.bat
set dodiff=%@IF['%@EVAL[%_DOWI-1]' EQ '5',%@DOY[%_date],no]
if '%dodiff' eq '' goto errror
if '%dodiff' eq 'no' goto skipdiff
echo *** do nodediff stuffs here ***
:skipdiff
goto whereever
:error
echo oops! dodiff variable is not set :(
:whereever

FWIW: everything, other than the new coding of an app for this, is
all 16bit stuff... everything in BATPOWER that might help you seems
to be but it is possible that i've overlooked something...

That's the other possibility - batch files work, and maybe I can
write a daynbr.bat to take the equivalent parameters.

does daynbr not run for you any more or is it the shelling to the called apps that is failing??

BTW: what version of daybnr do you have?

)\/(ark


* Origin: (1:3634/12)

Hi! mark,

On Tue, 28 Aug 12, you wrote to me:

Any old DOS tools that might have set/changed a DOS %envar% no longer
works. There is a way around it...

yep... even if the tool does nothing but to emit the DoY number...

Nah. I was thinking of a two-liner, still involving daynbr (which I don't use here) and a tool I use called NSET. NSET could pick up the output from daynbr and spew it into a %temp%\temptemp.bat file. That's one line. The second simply runs the %temp%\temptemp.bat to SET the %envar%. It's a technical solution found long ago in BATPOWER. I use it here.

However, the environmental constraints that Dallas is hinting at has me confused.

Cheers,
Paul.

---
* Origin: Access denied -- nyah nyah!! (3:640/384)

yep... even if the tool does nothing but to emit the DoY number...

Nah. I was thinking of a two-liner, still involving daynbr (which
I don't use here) and a tool I use called NSET. NSET could pick up
the output from daynbr and spew it into a %temp%\temptemp.bat file.
That's one line. The second simply runs the %temp%\temptemp.bat to
SET the %envar%. It's a technical solution found long ago in
BATPOWER. I use it here.

yeah, that's similar to the one i posted where the ficticious whatdoy tool emits the doy number which is redirected to stdout and then saved to a bat to be called next...

However, the environmental constraints that Dallas is hinting at
has me confused.

seems that he doesn't or can't run a VM and the old 16bit apps are [censored] in this supposedly better world of 64bit schtuff :?

)\/(ark


* Origin: (1:3634/12)

Hi! mark,

On Tue, 28 Aug 12, you wrote to me:

It's a technical solution found long ago in BATPOWER. I use it here.

yeah, that's similar to the one i posted where the ficticious whatdoy
tool emits the doy number which is redirected to stdout and then
saved to a bat to be called next...

Pretty much, yeah. I like to use the real thing rather firing blanks. :)

However, the environmental constraints that Dallas is hinting at
has me confused.

seems that he doesn't or can't run a VM and the old 16bit apps are [censored] in this supposedly better world of 64bit schtuff :?

Yeah, I'd forgotten about the latest advances in my original reply. They've gone out of their way to forget their roots. (Psst. I'm writing this from my wife's Ubuntu host, upstairs, in a RDP session to my Win98Se VM on my Ubuntu host downstairs. :)

Cheers,
Paul.

---
* Origin: District 9: SAVE the PRAWNS !! (3:640/384)

i know what you mean about "fixing" a working system...

Yup! :-)

[current DoY]

Where are you getting DoY from? It's not built into W7.

that's one of the main things that daynbr does.. actually, the main thing... but i also thought you said that you were able to use 4DOS/4NT/4OS2 (one of them) on your setup...

FWIW: everything, other than the new coding of an app for this, is
all 16bit stuff... everything in BATPOWER that might help you seems
to be but it is possible that i've overlooked something...

I'd have to recompile it for 64 bit, and that's beyond me.

hunh? maybe... but it seems to me that while 16bit is out, 32bit is in??

does daynbr not run for you any more or is it the shelling to the
called apps that is failing??

No, it just doesn't run.

ok... and i've also seen that you are running a 64bit OS...

BTW: what version of daybnr do you have?

2.1

wow! i've only ever had v1.0... and it has a misspelling in the copyright if you hadn't noticed :P

where can i get a/the daynbr v2.1 original archive from Ben Baker??

I'll have to study this stuff -- it's pretty messy, but could be
turned into an EXE once it's done. Thanks!

if you are talking about my "stream of consiousness" stuff, i dunno... and i can't fathom why it would need to be an executable... but then again, i don't run a 64bit OS... and likely won't until a true and real need is depicted that i cannot refuse...

on that note: the major things seen with going with 64bit stuff is nothing more
than memory usage... 16bit stuff quadruples and 32bit stuff doubles... other than that, there is no *real* enhancement or capabilities... the main thing that happens is that memory storage of data doubles when it is converted to 64bit... it has also been shown that 64bit processing takes a hit in speed when
compared with the same functions in 32bit... but, the world wants to advance further and the driving forces are storage sizes and memory usage...

if you have a 64bit machine at your disposal and you want/need to carry on with
your 16bit operations, the only answer these days is to set up a VM... others have already pointed out the available recovery options... moving past that is dancing on the razor's edge but someone has to do it ;) -=B-)

i can only hope that my previous postings have offered some assistance and an answer to your plight... especially since most everything in BATPOWER is 16bit ;)

)\/(ark


* Origin: (1:3634/12)

seems that he doesn't or can't run a VM and the old 16bit apps are [censored] in this supposedly better world of 64bit schtuff :?

The latter <sigh>

i feel the pain, brother! i feel it...

)\/(ark


* Origin: (1:3634/12)

Hi mark -- on Aug 28 2012 at 11:54, you wrote:

i know what you mean about "fixing" a working system...

Yup! :-)

[current DoY]

Where are you getting DoY from? It's not built into W7.

FWIW: everything, other than the new coding of an app for this, is
all 16bit stuff... everything in BATPOWER that might help you seems
to be but it is possible that i've overlooked something...

I'd have to recompile it for 64 bit, and that's beyond me.

does daynbr not run for you any more or is it the shelling to the
called apps that is failing??

No, it just doesn't run.

BTW: what version of daybnr do you have?

2.1

I'll have to study this stuff -- it's pretty messy, but could be turned into an
EXE once it's done. Thanks!



Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

Hi mark -- on Aug 28 2012 at 22:55, you wrote:

seems that he doesn't or can't run a VM and the old 16bit apps are [censored] in this supposedly better world of 64bit schtuff :?

The latter <sigh>



Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

i know what you mean about "fixing" a working system...

Yup! :-)

[current DoY]

sorry... i didn't answer this directly... the first is from daynbr... the second is from 4DOS/4NT/4OS2...

this is why i spoke of possibly needing a whatdoy app type thing in my previous
postings... everything after that was based on your "that's what i run on my desktop" comment which i understood to mean that it is what you are running on the problematic machine...

i don't know if 4DOS/4NT/4OS2 is 16bit or 32bit or maybe even 64bit these days... AFAIK i still run the 16bit stuff but i may be being fooles by my OS2 OS :P ;)

as long as it works for me, i'm "all in!" as the poker players are known to say
:)

)\/(ark


* Origin: (1:3634/12)

[current DoY]

Where are you getting DoY from? It's not built into W7.

that's one of the main things that daynbr does.. actually, the main thing...

dang it! i thought i also answered this with the main secondary thing that daynbr does... that being to give the daynbr of the DOW (Day of Week) based around the current date...

in other words, if today is DOW 3 as daynbr counts (zero based), then

daynbr /d5 echo @###

will execute the echo of the DOY number for DOW 5 as it calcs it... this means that if today is DOW 4, then the calculated DOW 5 is this weeks DOW 5... if today is DOW 6 then the calculated DOW 5 is last weeks DOW 5...

i do hope that these posts help in your endeavors... especially since i'm of the opinion that the original daynbr is written in ASM which probably won't translate to today's stuff even if you could get hold of the original author, ben baker, and get that original source code ;)

but, all things considered, that is still a possibility if anyone has any current contact information on him -=B-)

)\/(ark


* Origin: (1:3634/12)

Hi mark -- on Aug 29 2012 at 02:30, you wrote:

that's one of the main things that daynbr does.. actually, the main thing... but i also thought you said that you were able to use 4DOS/4NT/4OS2 (one of them) on your setup...

No, someone suggested it, but I'm not willing to overlay yet another OS/shell!

hunh? maybe... but it seems to me that while 16bit is out, 32bit is
in??

Yes, true. However, if I have to rewrite for 32, why not for 64?

wow! i've only ever had v1.0... and it has a misspelling in the
copyright if you hadn't noticed :P

where can i get a/the daynbr v2.1 original archive from Ben Baker??

I should have it here.... Yes, I do. I can send it to you....

if you are talking about my "stream of consiousness" stuff, i
dunno... and i can't fathom why it would need to be an executable...
but then again, i don't run a 64bit OS... and likely won't until a
true and real need is depicted that i cannot refuse...

if you have a 64bit machine at your disposal and you want/need to
carry on with your 16bit operations, the only answer these days is
to set up a VM... others have already pointed out the available
recovery options... moving past that is dancing on the razor's edge
but someone has to do it ;) -=B-)

Yup -- I've got a VM running, but there are a few disadvantages, and the challenge of moving ahead is, um, interesting. :-)

i can only hope that my previous postings have offered some
assistance and an answer to your plight... especially since most
everything in BATPOWER is 16bit ;)

I do appreciate your help - honest!


Cheers... Dallas

--- timEd/386 1.10.y2k+
* Origin: The BandMaster, CANADA [telnet: bandmaster.tzo.com] (1:153/715)

that's one of the main things that daynbr does.. actually, the main thing... but i also thought you said that you were able to use 4DOS/4NT/4OS2 (one of them) on your setup...

No, someone suggested it, but I'm not willing to overlay yet
another OS/shell!

oh... i must have misread this following quote, then...

[quote]

Thanks, Mark -- no, it has to be Windows 32/64 bit.

hummm... may i ask why? a limitation of the OS' console operations?
i don't know how far 4DOS/4OS2/4NT has gone but there may be a 32bit
build of them...

It's what I run on my desktop. Simple!

[/quote]

i thought the desktop comment was about 4DOS/4OS2/4NT but i can see now that it
may have been answering my question(s) as to why it has to be a winwhatever thing...

hunh? maybe... but it seems to me that while 16bit is out, 32bit is
in??

Yes, true. However, if I have to rewrite for 32, why not for 64?

on the one hand, sure... but on the other, weeellllll...

wow! i've only ever had v1.0... and it has a misspelling in the
copyright if you hadn't noticed :P

where can i get a/the daynbr v2.1 original archive from Ben Baker??

I should have it here.... Yes, I do. I can send it to you....

thanks! got it... i wonder how it is different from the v1.0 i have?

if you are talking about my "stream of consiousness" stuff, i
dunno... and i can't fathom why it would need to be an executable...
but then again, i don't run a 64bit OS... and likely won't until a
true and real need is depicted that i cannot refuse...

if you have a 64bit machine at your disposal and you want/need to
carry on with your 16bit operations, the only answer these days is
to set up a VM... others have already pointed out the available
recovery options... moving past that is dancing on the razor's edge
but someone has to do it ;) -=B-)

Yup -- I've got a VM running, but there are a few disadvantages,
and the challenge of moving ahead is, um, interesting. :-)

disadvantages?

i can only hope that my previous postings have offered some
assistance and an answer to your plight... especially since most
everything in BATPOWER is 16bit ;)

I do appreciate your help - honest!

de nada, mon... de nada -=B-)

)\/(ark


* Origin: (1:3634/12)

Hi Mark,

BTW: what version of daybnr do you have?

2.1

wow! i've only ever had v1.0... and it has a misspelling in the copyright if you hadn't noticed :P

where can i get a/the daynbr v2.1 original archive from Ben Baker??

I've got daynbr21.zip here:

http://www.filegate.net/bfds/daynbr21.zip

040105 16k 1 DAYNBR Version 2.10 is a simple program. It calculates the correct
day number, edits a DOS command's parameters to contain the day number, then executes the command. It was originally created to assist in automating the processing of FidoNet's weekly nodelist. NOTE that v2.1 is DAYNBR.EXE (vice .COM) so be sure and rename DAYNBR.COM to something like DAYNBR10.COM when upgrading ..

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)

where can i get a/the daynbr v2.1 original archive from Ben Baker??

I've got daynbr21.zip here:

thanks, janis! i've got a copy now ;)

)\/(ark


* Origin: (1:3634/12)

where can i get a/the daynbr v2.1 original archive from Ben Baker??

I've got daynbr21.zip here:

thanks, janis! i've got a copy now ;)

Ok :) One of these days I have to install DOSEMU Lol..

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-1
* Origin: Prism bbs (1:261/38)

where can i get a/the daynbr v2.1 original archive from Ben Baker??

I've got daynbr21.zip here:

thanks, janis! i've got a copy now ;)

Ok :) One of these days I have to install DOSEMU Lol..

hehehe... you might be better off with DOSBOX or one of the newer machine emulators ;)

)\/(ark


* Origin: (1:3634/12)