User count is set to 141 when new BBS configured

[Pinacolada64]

Not sure where this is happening. Run +.alpha/ind to fix.

[Pinacolada64]

im: during new BBS setup, record 12 in e.data is set to ^ (141), then read back later as ur=141
3300- is where e.data is set up

Looked through Jack's sub.handles/sub.misc files, not as extensive as Al's im.misc.
However, Jack's i/su.config creates u.index differently. I'll try that.

4074 &"Creating {f5}u.index{f5}....":dr=6:gosub3:a$=dr$+"u.index":print#15,"s"a$
4075 a%(0)=1:a%(1)=1:&,60,3,0,a%(0),4,a$,dv%:close15:&"Done!"

His line 3 is our line 1010 (figures out which device/drive is assigned to the user disk). A struct is created with the &,60... call, and saved.

[Pinacolada64]

This has been incorporated into Dec 17th's im module. Seems to work! ur is set to 2, u.index created properly with the user count set to 1.

[x-tec2017]

Where is the Dec 17 im module?

…

On Sun, Dec 17, 2017 at 5:00 PM, Ryan Sherwood ***@***.***> wrote: This has been incorporated into Dec 17th's im module. Seems to work! ur is set to 2, u.index created properly with the user count set to 1. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aganod_-aQjmWWuOVV7ywKiKg8VL4RVdks5tBY7rgaJpZM4QzClJ> .

[Pinacolada64]

I'll upload it to the WiFi BBS. Meanwhile, commit 462ce5e

[x-tec2017]

That would be great. Thanks.

…

On Mon, Dec 18, 2017 at 3:31 AM, Ryan Sherwood ***@***.***> wrote: I'll upload it to the WiFi BBS. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AganoVD0wQ8eEonYNm702jn_P57JfgHUks5tBiLkgaJpZM4QzClJ> .

[Pinacolada64]

I'm closing this issue, I believe the Dec. 17th IM revision fixes it.

[x-tec2017]

I agree. Haven't heard from you in awhile. Lots has been done since then. New fixes, mods and a game added in the Image 2.0 Support UD's.

…

On Fri, Mar 2, 2018 at 4:47 PM, Ryan Sherwood ***@***.***> wrote: I'm closing this issue, I believe the Dec. 17th IM revision fixes it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AganoeJq065WhIJ6mxyybfCsIcGJ48aHks5tab3zgaJpZM4QzClJ> .