Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About HolmesSherlock

  • Birthday 05/29/1988

Profile Information

  • OS
    XP Pro x86
  1. PassPass - Bypass the Password

    Meet PassPass (Bypass the Password), a nifty Grub4DOS batch script to disable/re-enable Windows logon password validation. Credit (as well as dis-credit) is to be equally shared between jaclaz and Holmes.Sherlock for the idea and coding respectively. We appreciate any success/failure report mentioning the following: Windows version (e.g. XP, Vista, 7)Architecture (e.g. 32-bit/64-bit)msv1_0.dll version (e.g. 6.1.7600.16525) along with MD5 checksum, if possible Technical details: The script tries to locate all existing Windows installations and corresponding Windows editions as well. Thereafter, it replaces the CMP instruction responsible for password verification with a 'benign' sequence of bytes. For reverting back the changes, the process is just the opposite. The whole idea is derived from WindowsGate and Astr0baby's tutorial. Usage: Install Grub4DOS. You may prefer using RMPrepUSB. Script tested with Grub4DOS v0.4.5c-2013-03-03.Download grubutils and copy WENV binary on the root of the boot media. Script tested with grubutils-2011-06-27.Copy PassPass.g4b and menu.lst on the root of the boot volume.Boot.Ideally 'Autodetect' mode should be able to list out all existing Windows installation. For buggy BIOS-es, try appropriate <Disk#> and <Partition#> to 'Forcedetect' Windows installations.Choose either 'Patch' or 'Unpatch' respectively for disabling/re-enabling password verification.Reboot and boot into target Windows. Credits: jaclaz - For ideas, code snippets, information. The script embeds his DLL version detection script.Ectomorph a.k.a. Damian Bakowski - For his 'unannounced' patch for 32-bit version of msv1_0.dll.Astr0baby - For his reversing tutorial Download: http://www.sherlock....s-the-password/ Development: https://code.google....pts/source/list
  2. Probably it can be achieved this way. It's so surprising Windows doesn't provide any standard way to apply certain policies like this to limited accounts. Actually, I've started this thread to solve my friend's problem. To my knowledge, Internet access can be prevented by one of the following methods: 1) If your organisation is using a proxy server(e.g. SQUID) for its internal network, then you can make that proxy ask for authentication, failing which one won't be able to access Internet. 2) You can install a web filter software which installs a filter driver on ur machine. That driver starts at Windows startup & rejects all network access requests dynamically. One such free, yet good tool is "K9 Web Protection". But I'm not sure whether it's configurable on a per-account basis. 3) You can force users to use specific browsers & then set those browsers' proxy settings to an invalid one. IE's proxy settings page can be made disappear from the view with some tweaks. Now, I'm not sure whether my friend's office uses a proxy or not. So, option (1) is ruled out for the time being. They don't wan't to use any third party tool apart from what is provided with Windows. It makes me reject option (2) also. The problem with (3) is, it only prevents IE users from accessing Internet. But, they have other browsers installed. Here, I'm stuck now.
  3. Can it be done only for limited user accounts & left as it it for Administrators?
  4. Can Windows firewall be configured on a per-user basis?
  5. Is there any way to block Internet access for LIMITED users on a Windows XP machine WITHOUT using any third party software ? By googling, I've found certain guides which instructs some mechanism either using any third party tool or talks about policies which will only prevent an user from surfing if Internet Explorer is used but not other browsers. Please note that either of the solutions will not work for me.
  6. I own a LENOVO IDEAPAD V460 (59 - 044185) laptop. It has an integrated fingerprint driver & a web-cam. Both are internally connected by USB bus, I guess. I've installed Windows XP several times & every time I installed all the drivers listed here. I need to install EgisTec FingerPrint driver & BioExcess front end to power up the fingerprint reader (FPR). Never I faced any problem. But only this time, what problem I'm facing is - every time I try log in to the system, the Windows XP logon screen apperas, but the BioExcess FingerPrint recognition remains disabled. When I enter password (instead of fingerprint) & log in to the system, then also it remains de-activated. When I swipe finger at BioExcess console, it shows "Unable to detect fingerprint device". Every time I need to install the EgisTec driver to activate the FPR device & get it recognized by BioExcess. I haven't stopped any services associated with EgisTec driver. Any ideas to share?
  7. Install XP from a RAM loaded ISO image

    @cdob Even if I uncomment fixboot.usb, then also my problem remains the same. Instead of using the menu.lst that I posted earlier, if I use yours, then after the completion of GUI mode setup, the machine restarts & again starts the setup from the very beginning. The loop goes on. I don't even get a chance to choose to boot from HD as the "Press any key to boot from CD.." prompt is not there. My boot order in BIOS is: USB drive first & then internal SATA HD. CD drive comes later. Any suggestions so that I can use your menu.last conatining a single entry instead of mine which contains three?
  8. Install XP from a RAM loaded ISO image

    Can u plz explain this a bit? Is there any specific known reason for happening this? If the file is not found, then?
  9. Install XP from a RAM loaded ISO image

    To answer my query, only this much was enough. I've already checked the link. Just wanted to make myself clear. Anyway, thanks a lot.
  10. Can anybody upload the attachment in the first pot? As many has told, the link (http://zonalteck.com/Winpe3.0ver0.1.rar) is dead.
  11. Install XP from a RAM loaded ISO image

    The menu.lst works fine for me. But, my apology, I can't follow what u r trying to mean.If I boot from hard disk at first restart, the GUI setup starts, then stops asking me to choose the location of files which resides on CD, better to say CD image. Then how can I locate them if I don't RAM-load them beforehand? If I ram-load the image, then installation goes without error. Can u post the COMPLETE menu.lst ? What is a broken BIOS? Then r u OVERWRITING the original setup.exe that gets copied from <CD Image>\I386\setup.ex_ ? Beg ur pardon again for making u "talk" so much on the same issue. I just want to make things clear to myself.
  12. Install XP from a RAM loaded ISO image

    The way I've solved the problem is by appending two more entries in menu.lst. The second entry was used after the restart that takes place as soon as text mode setup finishes while the third one was used after the restart that takes place after GUI mode setup. Now my menu.lst lookes like: title Loading XP RAM install - Part 1 ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) #(fd1) optional, required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_RAM.ISO (0xFF) map (hd0) (hd1) map (hd1) (hd0) map --hook chainloader (0xFF)/I386/SETUPLDR.BIN title Loading XP RAM install - Part 2 ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) #(fd1) optional, required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_RAM.ISO (0xFF) map (hd0) (hd1) map (hd1) (hd0) map --hook chainloader (hd0, 0)/ ntldr title Loading XP RAM install - Part 3 map (hd0) (hd1) map (hd1) (hd0) map --hook chainloader (hd0, 0)/ ntldr I pardon, but my question is still unanswered. The only statement I found in txtsetup.oem is: dll = setup32, setup.exe which according to Microsoft documentation(http://msdn.microsof...919(VS.85).aspx), copies the specified file under %systemroot%\system32. But how the fake setup is being EXECUTED?
  13. Install XP from a RAM loaded ISO image

    What I tried to mean is - after the text mode setup, Windows setup is expected to proceed to GUI phase. When my machine restarts after text mode setup, I usually take out the CD from the CD drive. Because, I'm using a tweaked version of XP install CD which does not provide me with usual "Please enter a key to boot from CD/DVD" option.(If I can remember correctly, I've seen a BartPE plugin like this). Anyway, after Windows setup continues with GUI phase, I reinsert the CD in the drive again. But, with Grub4DOS memory mapping, that I can't do. That's what my problem is. Can u suggest some workaround? Reference threads: http://www.nu2.nu/pebuilder/pluginhelp/bootfix.htm http://www.boot-land.net/forums/index.php?showtopic=9540 How Windows is being "made to read & execute" fake setup.exe from virtual floppy instead of usual I386 of CD image, means where it is expected to be?
  14. Install XP from a RAM loaded ISO image

    What can I do to install by cdob's method? NO, surely it's not the actual question. Thanks for the link Sorry for asking a hazy question. What I'm asking is - 1) "Should I copy the contents of <virtual floppy>/setup/I386 to <CD>/I386 & rebuild the ISO ?" 2) If NOT, then how Windows is going to find fake setup.exe?
  15. Install XP from a RAM loaded ISO image

    Can anybody explain me how the setup.cmd is being invoked during setup? Following the procedure stated by cdob , the installation of Windows begins from scratch after the restart (which takes place after initial text mode setup) ? What can I do?