I got that, but I'm not sure I did it right. What I did was:
1) view every code on 1 single line;
2) starting from the code you posted earlier, I've changed EVERY line accordingly
3) game now crashes constantly when trying to create a map.
4) uninstalled, installed again, and started the game from the Autoplay CD, on a 1024x768 resolution. The mouse scrolling speed is still very fast, but much more playable. I'm thinking that with a higher resolution, I would not have this problem...

Anyway, i couldn't patch the game to 1.10 or any other version, cause any patches I've downloaded said that they can't find the game. And since there is no autopatcher on this site... I dunno what else I could do. it's playable now, but still frustrating.

I meant to finish that last post with the following, but I hit send prematurely. So let me try ending it properly this time.

You are diplaying the entire rom2.exe program code which is in reality one continuous stream of hex pairs from beginning to end. In your case, you have your hex editor set to display the file as 32 hex pairs on each row. So once your editor reaches the 33rd hex pair, it wraps to the 2nd row and continues...and so on until it reaches the end of the rom2.exe program.

First, you are not searching for just a single (or even two) hex string of "FF 32" and replacing it with anything. Instead, you are changing ALL of the data that is listed in the entire patch info that I posted.

As I tried to indicate in my post, each row contains three pieces of vital information: the offset location, what you will find at that offset NOW and what you must change it to be.

Perhaps a literal example will make this clearer. The first four lines of the patch info I posted for rom2.exe are:

000064F6: 8B FF
000064F7: 8D 15
000064F8: 0C A8
000064F9: FD C0
....

This means at offset 64F6 you will find 8B in your unmodified rom2.exe file. You must replace that 8B and instead make it FF

Next line: at offset 64F7 you will find 8D You must change that to 15

Next line: at offset 64F8 you will find 0C You must change that to A8

Next line: at 64F9 you will find FD You must change that to C0

And so on, keep going all the way through the WHOLE list of edits. You must make the precise edits listed EXCEPT two lines you have latitude to vary the value you enter. These are the two highlighted lines.

0000650D: FF 32 ;;; HERE IS INTERVAL

and

000067D0: 82 32 ;;; HERE IS INTERVAL

For these two offsets, you are setting the value in milliseconds that your screen scrolling will delay. 32 in hex code translates to 50 in the decimal numbering system (so that's 50 milliseconds delay in screen scrolling). If your scroll speed is still too fast with "32", you simply re-edit those two lines using an even bigger number (in hex of course). For a 100 millisecond delay you would use 64 (because 64 in hex translates to 100 in decimal).

What you are in fact doing with all this editing is literally reprogramming ROM2. You are replacing the original machine code instructions and substituting new ones. That is literally what this patch is doing.

Regarding use of your hex editor:

Looking at your screen shot, you have your hex editor set to display 32 offsets per row. I think this hex edit process will be much clearer (at least your first time around) and make more sense to you if you change your editor to display a single offset per row (ie. a one hex pair wide column). When you do that, every single offset will explicitly appear in the left-most column display because each row will be a single offset. As you currently have it dsplayed, think of it as word-wrapping in a text editor. You are diplaying one endless stream of hex pairs. In your case, you are displaying 32 pairs on each row.

Ok, so used Hex Workshop to edit each of those lines starting from line 0000650D upto 000067D0 or whatever it was, and manually changed each line to correspond to that interval. I noticed some line were left unaltered... anyway, after doing that, the executable file crashes every time I try to go into a map. I've not patched the game, it's installed in its original version, and I can't find any patches online... so... I don't get it, I can only hex edit the patched exe or what? :(

Unfortunately, the Hex code I get in rom2.exe is much different, so I have no idea where to change the milisecond scroll value, the hex strings FF 32 and 82 32 appear more than once...
Here is a screenshot (and therefore, my dilemma :D) :
http://img703.imageshack.us/img703/7771/rom2exe.jpg

So here is how you manually hex edit your game to "fix" the fast scrolling speed using that information I posted earlier (a snapshot from Vladimir's web site):

Think of each row posted as three pieces of information:

1. the offset address

2. what you will find at that offset address

3. what you change it to

If it helps you visually, change your hex editor display so that it shows the offsets one byte pair per row and then the offsets in your hex editor will exactly match what you see here. In reality, the machine code is one seamless and endless hex string. Your hex editor simply allows you to display this string word-wrap fashion with as many offsets per row as you wish. Ultimately, it's still the same end-to-end single stream. The offsets are simply the distance from the file beginning (thus the term offset).

Just got ROM2 installed again and of course, I've ran into the mouse scrolling too fast issue. What I get is that you have to HEX edit the exe file. I've downloaded a free Hex editor and looked for those particular strings, but they look nowhere near the same, they look more like boxes each with 2 number in them, and the FF 32 and the 82 32 sequences appear more than one time... So... my question is, how do you fix this file again? Or better yet, does anyone have a better Hex Editor suggestion? Really wanna play it again :)

Well, until Vladimir get's his Unix server working again, I did find a snapshot of his article concerning the scrolling speed. It lists the hex edit info you need to patch your rom2.exe or allods2.exe files in order to fix the scrolling speed. Perhaps that will help you patch your game. It's very long, so forgive me. I'll duplicate the info below as best I can. I hope the formatting does not get borked by pasting it to this forum thread.

Fix of too fast scrolling

Author: Vladimir Chebotarev aka ex-lend
Categories: RoM 2, Patches

Marked place is value of scrolling interval (32h == 50), in milliseconds. Set greater value for slower scrolling.

I looked at the other places that fix this issue and they all point to http://allods.homeunix.org.
However, everytime I try to open it to get the fix, it doesn't work. I'm thinking the site was taken down? Is there anyway to still get the scroll fix. Thanks!