I am now struggling with DreamWeaver 4.0. I want to remove the first Nag; the Dialog which tells u if it's expired or not and that we should buy DreamWeaver for 'only' $299,-. When u remove this nag correctly, everything will be fine. I know this because I did it. Now, what is my problem? When I patch the .EXE file at location 004072DF (This jump should always jump). My harddisk starts to make lots of noize but I see nothing on my monitor. But, when I just reverse the jump in SoftICE, no nag will be shown and DreamWeaver starts without any problems. Could this be some kind of checksum? I find this very hard to believe, because when I set a BPX with SoftICE, one byte of the file is changed into CC and DreamWeaver will run normally.

Does anyone know anything about this?

Thanks in advance and Grtz,

Argoth

I don't know if there is a checksum in Dreamweaver, but anyway you are wrong when you say that "when I set a BPX with SoftICE, one byte of the file is changed into CC". In fact, when of the byte of the program loaded IN MEMORY is changed, but the file stays the same. Of course, when you make a patch, the file is modified.

Wizard

Thanx for replying, but I'd like to disagree with you there. Maybe its my sICE version (v3.0), but when I set a specific breakpoint in an EXE and I compare it to a backed up EXE with HexWorkShop, the files are different; there's a CC on the places where I just set my breakpoints.

Grtz

Argoth

(This doesn't really solve my problem, but what the hell )

hi,

I think you're both kinda right :-) That is, Wizard is rigth in theory... debuggers only change the code of the program in memory. What Argoth is seeing is some very weird softice-specific thing, which mostly seems to happen when debugging programs made with MSVC (not sure if it was VC or VB though)... There was a discussion on this a long time ago on the board, and as far as I can remember, nobody could give an explanation for this behaviour. I think it was Kayaker or Jimmy Cliff who started that thread (not quite sure though -- it's a long time ago).

Anyway, concerning your original question: have you looked at memory patching tools or process loaders and the like? That's all I can think of, just trying to help until one of the local gurus arrives

i have a question or two. is this the old rsagnt32.dll? if so i have already done tutorials on that but will help you nevertheless. it matters not, i have reversed all of the newer versions and would be glad to lend assist. please email me.
jomamameister

the CC is an int3 opcode instruction for the debugger to break on. So DONT set a bpx. Try setting a bpm 4072df rw or bpr 4072df 4072df+4 rw and see if you get to the crc code that way.

I remember the old rsagent - simple to 'pop' those real exe's but this DW4 is a with later version but you can still make it self register with the correct string in the registry. no hacking required.

+Spl/\j }>
...topped up with Guinness again :-)

Hello Coderz

Today I am in shitty mode due to trouble at work ......

So I am going to take my vengence out on RSAGNT ANY VERSION............ as the LAMEST commercial 'protection' scheme in the history of .... commercial protection.

So I read this thread and posted a teaser as a reply. Nobody took me up on the offer of explaining (probably cos the MB was down !) what I meant about 'pop'ing the exe !!!
I also checked out some other tuts that take you deep into the codewoods........ well forget em.....here is my *tutorial* for ANY RSAGNT 1,2,3 protected app...esp. Macromedia Dreamweaver, UltraDEV, AuthorWare, Flash 5 etc etc etc

1) Install the app.
2) look in the program folder for a ???pop.exe or ???pop.tty and always make it a ???pop.exe.
3) Set a BPX MessageBox in SI
4) run the 'pop' exe
5) proggy says 'preparing blah blah'
6) SI pops cos your not supposed to be doing this !
7) Press F12 and see a couple of lines down CMP ESI,1.
8) make ESI register 1
9) BC*
10) Press F5

Finished. The program self registers and unprotects itself like a good little boy.

Lame or what......... Norton / Symantec used to use RSAGNT. I once saw a fantastic tut on bypassing the protector thread in WinFax Pro 9 trial.... well pop me they moved to 'superior' VBOX soon after !!!!!!! duh.

+Sp/\j

evil

Hiya,
Lucky for Macromedia etc you were'nt in a *really* bad mood
Its that orrible black stuff you've been drinking that puts
you in the evil mood .
greetz

Ok here is a little info on Macromedia Appz:

All Macromedia Appz can be cracked easily....What to do is simple..Just install Flash4 Trial and unlock it with your softice..And register it with a serial...Now the trick is coming

Go Start-->Run-->Regedit

Open Hkey_Classes_Root\ultxfile key and export it as a reg file.....

Ok...After this install another Macromedia Appz like Dreamweaver 4 and just check Hkey_Classes_Root\ultxfile.You must see another sub-key with a new number just write down the number and open your imported reg file and change the number to the new number you just got.Save the file and double click it.

And now open Dreamweaver What You See!

"Your software is being prepared" Heheheheh You got it!

This works for all Macromedia Appz including Flash 3-4-5 ;Fireworks 3-4 ;Dreamweaver 3-4 and Authorware

Just newbie's gift to all newbies outta there!

and the easiest trick :
go to astalavista.box.sk and download the crack he he.

I'm using dreamweaver 4 on the main site and did it that way, this time

Sorry but somebody had to make the stupid post of the thread, I felt comfortable with this