Only if your porting Rom 2.4b6 to Windows. Linux is fine. Of course most
of my experience has been with the Windows ported version. If you are
concerned about Linux compatibility issues. Read the rom faq I think they do
have something on there about Linux issues. Hope that helps you.
Dantin
----- Original Message -----
From: "Alex Thaler" <[EMAIL PROTECTED]>
To: "Dantin" <[EMAIL PROTECTED]>
Sent: Saturday, July 06, 2002 11:59 AM
Subject: Re: OLC 2.0/customization bug
> When you say there are "a number of things you need to do...to fix the
> original bugs", do you mean in general, or if you want to run on Windows?
> I'm just wondering, because I just installed Rom2.4b6 (on Linux) and if
> there's something I need to do, I'd like to know what it is...
>
> On 7/6/02 11:59, "Dantin" <[EMAIL PROTECTED]> wrote:
>
> > There are a number of things you need to do to the stock Rom 2.4b6 in
> > order to fix the original bugs. When porting to Windows there is a
problem
> > with the time, gen data, and Encryption. Its not neccessarily a bug but
a
> > customization to the stock Rom in order for things to run smoothly. Get
> > those fixed first in a virgin stock Rom 2.4b6 then run your patch. You
will
> > get some additional files when the patch program doesn't find the exact
> > lines your looking for then you can go right to those spots and enter
the
> > data by hand.
> >
> > When I installed my english version of OLC I think I included the
> > fixes in the patch but I'm not sure. I also installed Lopes Colour Code
2.0
> > right after which required a lot of data input. Hope that helps you.
> >
> > Dantin
> >
> > ----- Original Message -----
> > From: "Matt Foltz" <[EMAIL PROTECTED]>
> > To: <[email protected]>
> > Sent: Saturday, July 06, 2002 10:16 AM
> > Subject: Re: OLC 2.0/customization bug
> >
> >
> >> --- Tom Whiting <[EMAIL PROTECTED]> wrote:
> >>>> Show us your whole customize code.
> >>> Please, don't.. That'd just spam the list with
> >>> unnecessary code. Showing
> >>> code is good, but then again, sometimes, you need to
> >>> solve problems
> >>> yourself too.
> >>>> We cant help you with something like that if you
> >>> dont show us the code.
> >>> Who's this we you're talking about? got a mouse in
> >>> your pocket or
> >>> something? Generally, there's someone that can help
> >>> with something, even
> >>> without asking for code. As a general rule, you're
> >>> best bet is to speak
> >>> for yourself and only yourself.
> >>>> and what bug are you talking about?
> >>> Read email fully before asking.
> >>>> the way. And what codebase Rom Rot etc..?
> >>> Once again, read email before asking.
> >>> Porting OLC2 to Rot, while possible, is most likely
> >>> NOT going to be
> >>> happening.. As it was, porting 1.8 was bad enough
> >>>> I dont think we wanna dig threw the archives
> >>> trying to find a nice little
> >>>> customize bug. Theres prolly 100 or more.
> >>> Again, read the emails before asking, and run your
> >>> mail through a spell
> >>> checker.
> >>> If you don't have a solution for the problem, it's
> >>> best to just keep to
> >>> yourself, allowing others that DO have one to help
> >>> solve it.
> >>>
> >>>
> >>>>> I've been reading up on this bug in the
> >>> archives, but
> >>>>> all of the bug fixes seem to just lead to more
> >>>>> problems. Has anyone encountered this problem?
> >>> No (and I AM running olc2, have been for almost 2
> >>> years, had almost
> >>> little problems with it that couldn't be solved with
> >>> a little common
> >>> sense:P).
> >>>
> >>> Here's a couple of solutions for you:
> >>> A> Go through your customization code, make sure
> >>> that you have done
> >>> everything CORRECTLY.
> >>> B> Take out customization completely (unless you're
> >>> running a full pk
> >>> mud, or plan on encouraging it heavily, it's not the
> >>> best.). This will
> >>> only temporarily solve the problem however.
> >>> C> Go through ALL of your spellgroups and make sure
> >>> they're set
> >>> correctly. If you've added classes or groups, that's
> >>> probably your
> >>> problem.
> >>>
> >>> More than likely, the problem is NOT with
> >>> customization, but with a
> >>> separate function INSIDE of customization. Did you
> >>> patch this into a
> >>> STOCK mud, or did you wait and add things, THEN
> >>> adding OLC?
> >>>
> >>> --
> >>> TJW :Head tech, designer, bum:P
> >>> Mud :http://dreamless.wolfstream.net
> >>> telnet :telnet://dreamless.wolfstream.net 9275
> >>> OLC Pages:http://olc.wolfstream.net
> >>>
> >>>
> >>>
> >>> --
> >>> ROM mailing list
> >>> [email protected]
> >>> http://www.rom.org/cgi-bin/mailman/listinfo/rom
> >>
> >> Well it's in the new_gen_data function. Like I said
> >> when you selected yes to customize it crashed, and I
> >> found this fix in the archives:
> >>
> >> GEN_DATA *new_gen_data(void)
> >> {
> >> GEN_DATA *gen;
> >>
> >> if (gen_data_free == NULL)
> >> gen = alloc_perm(sizeof(*gen));
> >> else
> >> {
> >> gen = gen_data_free;
> >> gen_data_free = gen_data_free->next;
> >> }
> >> +#if defined( FIRST_BOOT )
> >> VALIDATE( gen );
> >> +#else
> >> + gen->group_chosen = ( bool * ) malloc( sizeof(
> >> bool ) * MAX_GROUP );
> >> + gen->group_chosen[MAX_GROUP-1] = 0;
> >> + gen->skill_chosen = ( bool * ) malloc( sizeof(
> >> bool ) * MAX_SKILL );
> >> + gen->skill_chosen[MAX_SKILL-1] = 0;
> >> + VALIDATE(gen);
> >> +#endif
> >> return gen;
> >> }
> >>
> >> Except when I customize I have no choices, and it ends
> >> up giving me beguiling, attack, and then tons of
> >> spells that aren't in either group, along with most of
> >> the skills. It's a ROM 2.4b6, that I did add stuff
> >> to, and then I patched OLC 2.0 into it. However, I
> >> didn't change anything to do with customization.
> >>
> >> __________________________________________________
> >> Do You Yahoo!?
> >> Sign up for SBC Yahoo! Dial - First Month Free
> >> http://sbc.yahoo.com
> >>
> >> --
> >> ROM mailing list
> >> [email protected]
> >> http://www.rom.org/cgi-bin/mailman/listinfo/rom
> >>
> >
>
