Hello, Scott.

Here's what I've come up with:

=== Cut ===
Program SetHidden;

Uses
DOS, CRT;

{$I TELEGARD.INC}

Var
URec : UserRec;
UF : Userflags; { Total of 8 flags }
UserFile : File of UserRec;

Begin
Assign (UserFile, 'users.dat');
{$I+}Reset(UserFile);{$I-}
Seek(UserFile, 0);
Read(UserFile, URec);
UF := UF + [Hiddenlog, Hiddenlist];
Seek(UserFile, 0);
Write(UserFile, URec);
Close(UserFile);
End.
=== Cut ===

Does that look right? I'll test it later on after I back up my user data file.

Later,
Sean

//sean@nsbbs.info | http://nsbbs.info | ICQ: 19965647

... When women go wrong men go right after them.
--- GoldED/2 3.0.1
* Origin: Nocturnal State BBS - Johnson City, TN - bbs.nsbbs.info (1:18/200)

Here's what I've come up with:

=== Cut ===
Program SetHidden;

Uses
DOS, CRT;

any particular reason you need the CRT unit? i don't see any specific calls for
routines out of it...

[trim]

Does that look right? I'll test it later on after I back up my
user data file.

that's always a prudent thing to do :)

that and also use list.com and even a binary comparison tool to compare the two
files so that you can verify that only those two bits got changed and that they
are the proper two bits :)

)\/(ark


* Origin: (1:3634/12)

[ On 2009-10-13 at 20:56:30, Sean Dennis wrote to Scott Little ]

Var
URec : UserRec;
UF : Userflags; { Total of 8 flags }

UserRec would have its own Userflags field, so you don't need to define one here. Rather than:

UF := UF + [Hiddenlog, Hiddenlist];

you'd have something like:

URec.UF := URec.UF + [Hiddenlog, Hiddenlist];

Change .UF to whatever it's actually called in the UserRec definition.


-- Scott Little [fidonet#3:712/848 / sysgod@sysgod.org]

--- There is no spoon.
* Origin: [sysgod.org] You know you want it. (3:712/848)

Hello, mark.

Wednesday October 14 2009 at 22:56, you wrote to me:

that and also use list.com and even a binary comparison tool to
compare the two files so that you can verify that only those two bits
got changed and that they are the proper two bits :)

That's an excellent idea. You have any comparison tools to recommend (DOS or OS/2, doesn't matter)?

Later,
Sean

//sean@nsbbs.info | http://nsbbs.info | ICQ: 19965647

... Where there's a will, there's an inheritance tax.
--- GoldED/2 3.0.1
* Origin: Nocturnal State BBS - Johnson City, TN - bbs.nsbbs.info (1:18/200)

that and also use list.com and even a binary comparison tool to
compare the two files so that you can verify that only those two bits
got changed and that they are the proper two bits :)

That's an excellent idea. You have any comparison tools to
recommend (DOS or OS/2, doesn't matter)?

i generally used "comp /b" (/b for binary compare instead of textual) but i don't know what version of comp that is/was... i don't see it as a built-in in 4DOS or 4OS2... i'm lookin'...

[time passes]

i can't find it, now... the comp that i do find is comp.com and is both OS/2 and DOS flavored (one .com file for both)... maybe it was "fc"?? i just know that i had to use the "/b" option to denote a binary comparison instead of a textual one...

damn, that's got my goat and i'm rather frustrated that i can't locate that tool or remember exactly which one it was :( maybe it was... hummm... :!:

[time passes]

found it!! believe it or not, on one of the win98se boxes hiding out in \windows\command and also in \options\tools\oldmsdos... this last one is a copy of the tools\oldmsdos folder from the win98 install cd... it is FC.EXE...

[/me quickly copies it over to this OS2 box and gives it a try]

aww... says incorrect DOS version :? now, how to setver on warp3 with 4DOS?? :( maybe that's why i still tend to do most development on that machine?? no... can't be because i've been running this one for far too long... there's gotta be another util that i used to use that i probably lost yers back when i had to reinstall this system :? dagnabit! it was a very very very handy tool, too...

guess i need to figure out how to hack it and blow the dos version check out :?
:(

well, in any case, here's the /? output just so's you have an idea what it is/was capable of and decide to go looking for a similar tool on the net somewhere...

FC [/A] [/C] [/L] [/LBn] [/N] [/T] [/W] [/nnnn] [drive1:][path1]filename1
[drive2:][path2]filename2
FC /B [drive1:][path1]filename1 [drive2:][path2]filename2

/A Displays only first and last lines for each set of differences.
/B Performs a binary comparison.
/C Disregards the case of letters.
/L Compares files as ASCII text.
/LBn Sets the maximum consecutive mismatches to the specified number of
lines.
/N Displays the line numbers on an ASCII comparison.
/T Does not expand tabs to spaces.
/W Compresses white space (tabs and spaces) for comparison.
/nnnn Specifies the number of consecutive lines that must match after a
mismatch.

i'll keep looking, too because a good file comparison tool is a must for many programming situations... especially if you have large (greater than 64K) files
to compare :)

)\/(ark


* Origin: (1:3634/12)