Text 66, 86 rader
Skriven 2005-05-15 14:08:08 av Peter Knapper (3:772/1.10)
     Kommentar till text 64 av Mike Luther (1:117/3001.0)
Ärende: Resetting computer name?
================================
Hi Mike,

 ML> OK, now we are getting toward what I recall.  I don't 
 ML> recall that it was two places though.  And Johan hit at 
 ML> what I recall here.

 JZ> Huh? I clone OS/2 systems all the time and simply edit
 JZ> the 'Computername = ' line in IBMLAN.INI to reflect the
 JZ> new network name for the system. Works just fine.

 ML> Bingo.  Took a look at my own boxes and that's what I 
 ML> remember now here too.

Thats the main one and can be easily done, but there may be something in the
"current" NETACC file that also has a finger in there, but as Johan says you
can always blow that away and re-create it from x:\IBMLAN\INSTALL\NET.ACC

 JZ> They don't have to be the same length.

I think that may have come from a time when I tried HEX editing
NET.ACC........;-)

 ML> You know I think I recall that is one of the reasons 
 ML> you are supposed to keep a private 'Back' file for 
 ML> IBMLAN.INI in that sometimes the PEER LAN blows up when 
 ML> you do this stunt.  Looking at systems here and there, 
 ML> I see that it looks like I did keep these private 
 ML> archive files.

The one in the above INSTALL directory is from the original CD, it is NEVER
touched, so you should be right. You just need to build the shares, connections
and users.

 ML> Peter .. you've opened up more of this in that you note 
 ML> TWO such places are 'required'.  Is there any chance 
 ML> you can coax out any more hidden gems from you diamond 
 ML> mine mind that can teach us more here?

It may not be in 2 places, its just that 2 different things are affect by a
"simple" name change. Perhaps its something like a share password is "encoded"
using the hostname or something related like that...

 JZ> If you want to share a drive on the new system, you may have
 JZ> to reset NET.ACC first to get it to work. The system has to be
 JZ> rebooted afterwards to get it all to work.

 ML> Is this the deal where you copy the NET.ACC from the 
 ML> install source position in #\IBMLAN\INSTALL over the 
 ML> current one in #\IBMLAN\ACCCOUNTS and start all over 
 ML> for re-assigning stuff?  That including having to 
 ML> recreate new over-rides for ADMIN/PASSWORD and the 
 ML> original 'free-loading' GUEST?

Thats the one........;-)

 ML> You both have got me wondering!  Looking at my boxes here, I notice that 
 ML> in every case, the \ACCOUNTS\NET.ACC file shows dates 
 ML> MUCH more recent than any change I ever made in access 
 ML> rights manually, even for boxes that have no SHARE 
 ML> enablement at all.  

Yes, that file seems to get touched if you do something with the shares. If
your shares are "permanent" and you use the WPS to re-open them on System boot,
then the NET.ACC date does not change, but if you use the commandline NET USE
xxxx, then it seems to be "touched", but not in all cases...

 ML> And this is part of why NET.ACC is involved in this as 
 ML> the NET.ACC file has to be clean for such names that 
 ML> are 'identified' as boxes 'seen' on the PEER LAN, but 
 ML> isn't updated until ..

 ML>    When?   When is NET.ACC updated with no share/connection changes?

On one box here I have a set of shares that start at system boot and have not
changed in years, NET.ACC there still wears the 2003 date of last change. This
machine has changes every few weeks, and it reads as 10th May 2005, the last
time I connected to a 3rd machines share...

I think you should be right as long as you re-build NET.ACC.

Cheers.............pk.



--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)