************************************************
************************************************

Unfortunately, this site has restricted functionality as this browser does not support the HTML button formaction attribute.

Unfortunately, this site has restricted functionality as this browser has HTML web storage turned off.

326 of 857 files independent

1999 May

This HackStop Unpacker is able to unpack all .COM & .EXE files protected with HackStop 1.17, 1.18, 1.19 and .EXE files with and without encrypted relocations or image encryption.
  • Zip - DOS / Computer tool
  • CHRiSTOPH, program credits

Emulating UNHS.EXE in DOSee.

Use these tabs to make adjustments to the emulation

If the emulation is taking too long to load, you can turn it off.


Reload DOSee to launch the DOS prompt

Applying changes will reload the page and reboot the emulator





Changes are not applied until the browser tab is reloaded





DOS programs need a keyboard for user input
Some common keys used in DOS programs

ENTER to select or continue
ESC to navigate back or exit
are often used to navigate menus


Emulation too fast?
Set the emulator to use the 386 CPU configuration

Experiencing graphic or animation glitches?
Set the emulator to use VGA only graphics configuration

Need to turn off the audio?
Disable sound card support

Have no audio?
  1. Try Gravis Ultrasound hardware
  2. The song or audio file maybe missing from the program

DOSee pronounced dos/see, is our emulator used to run MS-DOS based software in your web browser.

MS-DOS (Microsoft DOS) was the primary operating system used by PCs during the 1980s to the early 1990s and is the precursor to Microsoft Windows.


DOSee is a slimmed down, modified port of The Emularity.

The Emularity is a multi-platform JavaScript emulator that supports the running of software for legacy computer platforms in a web browser. It is the same platform that's running emulation on the Internet Archive.

EM-DOSBox is a discontinued, high-performance JavaScript port of DOSBox that is applied by The Emularity for its emulation of the MS-DOS platform.

DOSee uses BrowserFS ZipFS and ZipFS Extras to simulate zip file archives as hard disks within EM-DOSBox.

DOSBox is the most popular MS-DOS emulator in use today and is frequently used by commercial game publishers to run games from their back-catalogues on modern computers.


DOSee, built on The Emularity, EM-DOSBox and DOSBox. Capture screenshot and save function built on canvas-toBlob.js.

3 items in the archive
  • UNHS.DOC
  • UNHS.EXE
  • UNPACK2
[+] Configuration Copy text
┌┐ ┐ ┌┬─┐ ┐ ┌┬──┐ ┌┬──┐ ┌┬──┐ ┌┐ ┌─ ┌┬──┐ ┌┬──┐ ┌┬──┐ ┌┬──┐ ┌┬──┐ ├┤ │ ├┤ │ │ ├┼──┘ ├┼──┤ ├┤ ├┼─┴┐ ├┼─ ├┼─┬┘ ├┼─ ├┤ │ ├┼─┬┘ └┴──┘ └┘ └─┘ └┘ └┘ ┘ └┴──┘ └┘ └ └┴──┘ └┘ └ └┘ └┴──┘ └┘ └ ┌┐ ┐ ┌┬──┐ ┌┬──┐ ┌┐ ┌─ ┌┬──┐ ┌─┬┬─┐ ┌┬──┐ ┌┬──┐ ├┼──┤ ├┼──┤ ├┤ ├┼─┴┐ └┴─┬┐ ├┤ ├┤ │ ├┼──┘ └┘ ┘ └┘ ┘ └┴──┘ └┘ └ └──┴┘ └┘ └┴──┘ └┘ 1.0 HackStop Unpacker 1.0 - Unpacks HS 1.17-1.19 [8086 Version] UNPACK, TR Script File - Unpacks HS 1.19 [386 Version] .EXE UNPACK2, TR Script File - Unpacks HS 1.19 [386 Version] .COM ──[1]──[ABOUT THIS UNPACKER]──────────────────────────────────────────────── This HackStop Unpacker is able to unpack all .COM & .EXE files protected with HackStop 1.17, 1.18, 1.19 and .EXE files with and without encrypted relocations or image encryption. There is a small chance of successfully unpacking lower versions than 1.17 because I tried to write this unpacker as generic as possible. Files protected with HS386 are not yet supported - support might come in later, use the Automatic Manual Unpacking Script file for TR 2.xx to unpack files protected with HS386. If the unpacking proccess fails for any reason, I suggest you to use : IceUnp 0.3.1, GTR, EDump, CrkCom or a manual unpack with TR or whatever... ──[2]──[ABOUT HACKSTOP]───────────────────────────────────────────────────── Wellknown and often unpacked trash for you favourite trash-can. Now, Stonehead has joined the HS project to improve it a little bit and in order to tell us how great this stupid little encryptor is, to make a few poor fools out there use it, who only read the docs. ;) I must admit, the reloc and image encryption is nice but the antidebugging code... After reading the huge HS.DOC everyone gets the impression that HackStop is the most powerful protector known to man... and after tracing HS, everyone feels sorry for the authors of this infamous encryptor. Just imagine : HS 1.00 - 1.18 could all be unpacked with CUP386 3.4 /3 which is out since 1997, but the last HS versions were even released in 1998! The only thing I'm expecting in further versions is a switch "/UNP" to automatically remove HS from encrypted files so that we needn't waste our time writing further unpackers for it. Maybe there's somebody who can tell me if they are talking seriously about HS in the arrogant way they are currently doing... ──[3]──[USAGE]────────────────────────────────────────────────────────────── In order to unpack HackStop 1.17 - 1.19 (86+ version) both .EXE .COM files do the following : UNHS.EXE [PROTECTED_FILE] In order to unpack HackStop 1.19 .EXE (386+ version) do the following : (Requires TR 2.xx) TR.EXE [PROTECTED_FILE] DO UNPACK (in TR itself) Q (in TR itself) MKEXE -> MEM.EXE is the unpacked file. In order to unpack HackStop 1.19 .COM (386+ version) do the following : (Requires TR 2.xx) TR.EXE [PROTECTED_FILE] DO UNPACK2 (in TR itself) Q (in TR itself) -> UNPACKED.COM is the unpacked file. ──[4]──[RECIPE OF HOW TO OBTAIN DRUG-LIKE EFFECTS WITH HACKSTOP]──────────── If you really need a quick laugh, take my advice and do the following : Take a look at that interesting HSFAQENG.DOC, Rose and Stonehead offer us : : ID> There is only one other concern. My program makes use of Int1 and : ID> Int3 interrupts and I am worried that the HACKSTOP program will : ID> interfere with my own. Is this the case or do you release these : ID> interrupts when the protected program is allowed to run? : :Sure, everything will be restored _after_ HackStop has done its job! Isn't this nice? HS will restore INT1 so that hardware breakpoints are able to break after HS has decrypted the original file, so we don't need to use a different IDT. Thank you guys. :) : ND> I'd like to register HackStop (the 30DM method). How much would it be : :That's fine :) ND, please mail me, I would like to hear this sentence again and this time from yourself so that I'm able find out if there are really 1 or just 0 persons caring about HS. :)) : CG> Trap is better than HackStop. :Delete TRAP.DOC and INSIDER.FAQ and reform your opinion while tracing :TRAP happily with TD386 and a bit of experience. After that, enjoy :the view of the unpacked bat2exe-compiled comfile. Don't forget :to empty your recycle bin. First of all: I did *never* say that. Second: I *would* have sayd it if anyone asks. :) These guys are still talking about TRAP 1.21 - because they are afraid of further versions... anyway, the bullshit with TD386 is another lame joke - can't everything be unpacked with experience?! : VT> Is HackStop still not unpackable? :HackStop 1.19 is probably unpackable by GTR. Furthermore we have not :developed a good method to detect EliCZ' EDump yet. But for some time we :can say that these tools aren't easy enough to use for mortal people :) Hahaha, typing "EDUMP FILE.EXE" is really *pretty* difficult!! GTR 1.C1 also includes a text file on how to unpack HS manually... :The nasty thing is that an unpacker just claims to work on one specific :platform, and that a protector is supposed to work everywhere - and :still kicking those unpackers. Yeah, that's really nasty, I suspect you guys to delete your sources and get yourself pklite instead. HS 1.19 is pretty unstable now! Sometimes the keyb behaves locked after starting a HS protected file. -> this was *really* the *only* advantage of HackStop, it's compatibility, which is gone now too. :[to be continued] Oh, yes, please continue it, we want to keep laughing. Ok, enough for this one, but, let's take a closer look at the "secret area" inside of one of the main HS .EXE files : :As a reward for finding the secret area, we allow you to read the least :boring notes out of our betatesters guide.. :) wow, are you happy! :) *Yeah*, we are really happy to read the secret area, because it will now allow us the laugh about the "hidden" messages following in it. :HS has always had a reputation :in this and we're planning to continue it ;) : :"The higher the better" (c) by ROSE ;) Guys, protectors are *normaly* getting better, the higher the version (or build) number is. :Concurrent protections rating table according to ROSE SWE & Stonehead (05/10/99) : :name ver type l date new security compat origin ROSE STN tot author :─────────────────────────────────────────────────────────────────────────────── So, the real jokes have begun now, I think the idea of writing a rating table if you are coding encryption systems your own is a little bit senseless. :C-Crypt 1.02 ce a 0898 0898 * **** ** * * 24 De'Feind C-Crypt did never work on my machine - 4 stars in compatibilty?! (...) :DS-Crypt 1.31 c a 1196 1297 *** *** *** ** ** 31 D Stalker This is the most incompatible protector I have discovered - 3 stars in comp?? :HS/386 1.19 ce a 0794 1198 **** ***** *** *** *** 43 ROSE SWE Nice joke guys, I cannot believe this is your true opinion... :PCrypt 3.51 e a 0795 1297 **** ** **** ** *** 35 Merlin 35 total points?! - PCrypt 3.51 is unfortunately completely worthless because of it's incompatibilty. :REC 0.39 e a 95 1198 ** **** ** ** * 27 ROSE :Trap 1.21 ce b 0198 1198 * *** * * * 16 Gabler Oh boy, REC, Rose's shitty image encryption trash-rip more secure than TRAP 1.21 - And the origin with ** stars... a rip... oh my god. Of course some people have to up-rate their own shit, because otherwise there would be nobody who says something positive about it. ;) :Secure 0.29 e p 0896 1097 **** **** *** **? *** 39 Warezak Total insanity or just a joke? Let's hope that they only made a joke... :Current Hacks_Top Six tot Rose STN Rose&STN :──────────────────────────────────────────────────────────────────────── :1. HackStop 1.19/386 ....... 43 **** ** 3 I don't want to tell you my rating for HS, because I want everyone to see for themselves.. but I want to say that writing an unpacker & script file for EnCom was much more difficult than for HackStop. ──[5]──[COMING NEXT]──────────────────────────────────────────────────────── ■ There is of course no more challenge in writing further UNHS for HS86, but an UNHS supporting HS386 would really be a challenge. ■ -> Send me unpacker requests ──[6]──[CONTACTING CHRiSTOPH]─────────────────────────────────────────────── Email : [email protected] Url : www.thepentagon.com/trap IRC : Nick: CHRiSTOPH ──[6]──[GREETINGS]────────────────────────────────────────────────────────── Rose & Stonehead, I feel sorry if I am too cruel, but - I would have never started UNHS.DOC the way I am ending it now, if you guys wouldn't have written so much bullshit in your own docs. I would just have kept my opinion in my mind and not have written it down. :)) Btw, Dimmu Borgir rules too, ICED EARTH either.. :) Chief, Here comes the promised UNHS.. finished within a few hours.. only the reloc rebuilder was hard work. But IceUnp does the work better. ;) The Cleric, How do you like the routines I sent you? Sorry for slow replies! How are you coming along with your protector? D.W., I'll get the pic ready soon. MantiC0re, There's still a big bug in SDW386 1.76 I have discovered. Dr. No & DarkGrey, So, where is the promised phone talk? Did you loose my phone number? LiuTaoTao & Lado, Thanx again for your debuggers. Exelist, Everyone who still cares about DOS. [19.05.1999]
UNHS.DOC 83x224 Font
83