Jump to content

MOONLIGHT SONATA

Member
  • Posts

    203
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    India

Posts posted by MOONLIGHT SONATA

  1. Let me ask some further clarification before i can send you pack software:

    1. will all files running from cmdlines.txt are going to be archived? including runonceex.cmd? i ask because both CMDLINES.txt and runonceex.cmd sits inside $OEM$ folder.

    2. are you going to unzip archive.zip to some TEMP directory? if that then unzip command should include mention of temporary extraction directory.

    3. i run a lot of batch files from RUNONCEEX.cmd but those files are located in some other folder inside my software installer "BOX" folder. do i include that directory inside the archive?

    Guide me.....as you and me -these 2 paranoids about security probably can't sleep this night before settling such issues.

    **MOON

  2. Great idea Martin, encrypted archive is the solution. but, how do you pass the authentication success/failure to the rest of the script in cmdlines.txt? are you thinking to encrypt runoncex.cmd? it remains within $OEM$ folder? is there be any problem when xp copies files & folders inside $OEM$ in 16-bit copy mode?

    -It's MOON

  3. @Martin

    wmic baseboard list full command returns following detail:

    *-*-*-*-*-*-*-*-*-*

    ConfigOptions=

    Depth=

    Description=Base Board

    Height=

    HostingBoard=TRUE

    HotSwappable=

    InstallDate=

    Manufacturer=MICRO-STAR INTERNATIONAL CO., LTD

    Model=

    Name=Base Board

    OtherIdentifyingInfo=

    PartNumber=

    PoweredOn=TRUE

    Product=MS-6734

    Removable=

    Replaceable=

    RequirementsDescription=

    RequiresDaughterBoard=

    SerialNumber=

    SKU=

    SlotLayout=

    SpecialRequirements=

    Status=

    Tag=Base Board

    Version=

    Weight=

    Width=

    *-*-*-*-*-*-*-*-*-*

    and,

    wmic bios list full returns as below:

    *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

    BiosCharacteristics={4,7,9,10,11,12,14,15,16,17,19,22,23,24,25,26,27,28,29,30,32

    ,33,34,36,37}

    BuildNumber=

    CodeSet=

    CurrentLanguage=n|US|iso8859-1

    Description=Phoenix - AwardBIOS v6.00PG

    IdentificationCode=

    InstallableLanguages=3

    InstallDate=

    LanguageEdition=

    ListOfLanguages={"n|US|iso8859-1","n|US|iso8859-1","r|CA|iso8859-1"}

    Manufacturer=Phoenix Technologies, LTD

    Name=Phoenix - AwardBIOS v6.00PG

    OtherTargetOS=

    PrimaryBIOS=TRUE

    ReleaseDate=20030710000000.000000+000

    SerialNumber=

    SMBIOSBIOSVersion=6.00 PG

    SMBIOSMajorVersion=2

    SMBIOSMinorVersion=3

    SMBIOSPresent=TRUE

    SoftwareElementID=Phoenix - AwardBIOS v6.00PG

    SoftwareElementState=3

    Status=OK

    TargetOperatingSystem=0

    Version=KM400 - 42302e31

    *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

    please ask what more can i do....

  4. @Dumpy

    yeah, it does the same thing as Martin's script does. but it doesn't solve the insecurity lied therein. Martin, during writting the script, selected a fictitious BIOS date and astonishingly that imaginary BIOS date is younger by just 6 days to the genuine BIOS release date of my machine. It is the Caveat. If we cannot include the BIOS release time (in my machine it is 8:58:02) , then ultimate protection based on BIOS method remains incomplete and unfulfilled.

    Thanks. Think again for the sake of Whole UACD builder community.

    P.S. BTW, MartinsVBS.txt doesn't have any BIOS release date in it . array AllowedHosts= array("Please")

  5. @MARTIN ZUGEC

    In the 1st code, you use,

    arrayAllowedHosts = array("20030716000000.000000+000")

    here what are the meaning of 000000.000000+000 ?

    now your bios build date and that of mine just missed by 6 days only. so near yet so far! that's why i wish if you could include BIOS build time inside the code. this can make the protection rock-solid. is it impossible to implement?

    waiting your kind response.

  6. 2Martin Zugec

    I implemented your script, it works flawlessly as i expected, and even before i applied i firmly believed that whatever you post here will work for sure. That's why i badly expected you to come forward with the code. I don't wear hat so i can't say "hat's off to you" and since i alredy commissioned my heart in favour of your brain(seeing your MAC magic work), the only thing that i can give you now is my head. Behead me Martin!

    For some serious input, i come with another post very shortly.Not Now! It is the Day of Deliverence, sir, Pardon me.

    2MSFN

    Thanks, for providing me a platform from where i got the chance to Net-Meeting someone like Martin who inspite of Work Pressure came with a Code in office time for Whole UACD builder community.English adjectives become useless and speechless in times when silence is the only way to say something!

    2ALL UACD Builders

    Watch Martin's Code here. It , with some further modifications, if possible, can provide the ultimate solution towards protecting UACD from any sharing nightmare. If the logic behind using such method is realized properly, any forum member can only extract benefit from Martin's Code. My position is very clear. I have no objection to give my UACD to ALL PC USERS ALL OVER THE WORLD, but i want to make One PC users' copy his personal one. I am not jealous , rather generous to play the perfect Host to any guest asking attention about my UACD. I want to be santaclaus, but it's only me. Regarding my UACD project, I am the MONARCH of ALL i SURVEY! Period.

  7. @Nois3

    why are you absorbed in limiting security to setting some expiry date and why CDKey is under scanner so much? your cdkey inn Winnt.sif can always be encrypted and if during cd preparation you, using UltraISO , hide $OEM$, your Install folder and particularly, winnt.sif in i386 folder , then how an intruder will ever get his eye into it?

    it is better to think about implementing BIOS version+date+time for killing unauthorised use of CD in conjunction with what i said about UltraISO method.

    -Thanks.

  8. @Nois3 and @ evilvoice

    Thanks, for your contribution. Great.

    What i had when i started this topic was the unavoidable situation where any of our forum member has to conceed his uACd to someone close enough to ask for it and someone generous enough to give it to some other without even thinking about how much effort from the side of original builder has been put into it. such scenario is neither unthinkable nor unavoidable. just imagine if such unfortunate things happen what is the solution ? we, all forum members, are men and do men cry?

    I forgot to mention martin's post. here's the link to first page:

    http://www.msfn.org/board/index.php?showtopic=47383&st=0

  9. Here's My stream of thought about protecting unattended Windows XP CD.

    Unfortunately, very little could be done about protecting unattended cd, just because no unique marker could be attached to UACD that can distinguish between

    two different installation CDs as well as two different installation environments. Martin Zugec posted an original but self-limited method of protecting UACD by using MAC address checking of installed LAN card. Brilliant implementation of idea, but to be appreciated with its limitation of mandatory availability of a LAN card for genuine success which, in, reality, may not be the case in many cases.

    I have one suggestion about some modifications to be implemented in Martin's method. Here is it :

    1. instead of LAN card and MAC address , we may think about system BIOS version as the unique identifier of installation environment and the machine. Windows xp stores in registry, in different places, a lot of information about system BIOS including version, date etc.

    while date can be a marker, for sure, but it is not going to be the ultimate solution, because it can be same in two machines.

    2. what xp , in my limited idea, spares from storing in the registry, is the system BIOS build time which is displayed in either entering BIOS setup or in mere wakeup logo screen of system bios display during boot-up.

    in my opinion, this build time is crucial if any seperate hardware independent protection is to be imagined.

    3. what we basically need is a program which , if run from CMDLINE.txt before runoncex.cmd, automatically detects System BIOS version+date+time, then cross-checks with a file in the cd for acuuracy of information. for next part i owe it to Martin for his unique mind - if cross-check is successfull then silently proceed with installation, but if it fails then silently delete NTLDR and restart the machine. although, here's a suggestion from me - as NTLDR can be restored from at least REcovery console, better is to delete NTLDR and boot.ini both.

    if there is any ignorance on my part , please let me know. give your piece of mind, please, - anybody.

    EDIT by Martin Zugec (with Moonlight Sonata permission)

    AnalyzeUA.vbs:

    Option Explicit
    'On Error Resume Next

    Dim objWMIService : Set objWMIService = GetObject("winmgmts:\\.\root\CIMV2")
    Dim colItemsBios : Set colItemsBios = objWMIService.ExecQuery("SELECT * FROM Win32_BIOS", "WQL", wbemFlagReturnImmediately + wbemFlagForwardOnly)
    Dim colItemsBaseBoard : Set colItemsBaseBoard = objWMIService.ExecQuery("SELECT * FROM Win32_BaseBoard", "WQL", wbemFlagReturnImmediately + wbemFlagForwardOnly)
    Dim strItemBios, strItemBaseBoard, strAllowedValue
    Dim objItemBios, objItemBaseboard

    Const wbemFlagReturnImmediately = &h10
    Const wbemFlagForwardOnly = &h20

     
    For Each objItemBios In colItemsBios
      For Each objItemBaseboard In colItemsBaseboard
         strItemBios = Trim(LCase(objItemBios.ReleaseDate))
         strItemBaseboard = Trim(LCase(objItemBaseBoard.Product))
       strAllowedValue = InputBox ("BIOS Release identificator","BIOS Release",strItemBios & strItemBaseboard)
      Next  
    Next
     
    Set objWMIService = Nothing
    Set colItemsBios = Nothing
    Set colItemsBaseboard = Nothing
    Set objItemBios = Nothing
    Set objItemBaseboard = Nothing

    ProtectUA.vbs:

    Option Explicit

    Dim objWMIService, arrayBIOS, objBIOS, strAllowedHost, strYouAreWelcome
    Dim strOperatingSystem, colOperatingSystems
    Dim objFSO, objShell, strSystemDrive
    Dim objBaseboard, arrayBaseboard, strComputerHost, strPassword

    Const wbemFlagReturnImmediately = &h10
    Const wbemFlagForwardOnly = &h20
    Const wmiRestartForce = 4

    strPassword = "Passw0rd"
    Dim arrayAllowedHosts(1)
    arrayAllowedHosts(0) = "20030716000000.000000+0000x1078"
    arrayAllowedHosts(1) = "20030814******.******+***virtual machine"

    Set objShell = CreateObject("Wscript.Shell")

    Set objWMIService = GetObject("winmgmts:\\.\root\CIMV2")
    Set arrayBIOS = objWMIService.ExecQuery("SELECT * FROM Win32_BIOS", "WQL", wbemFlagReturnImmediately + wbemFlagForwardOnly)
    Set arrayBaseBoard = objWMIService.ExecQuery("SELECT * FROM Win32_BaseBoard", "WQL", wbemFlagReturnImmediately + wbemFlagForwardOnly)

    For Each objBIOS In arrayBIOS
    For Each objBaseboard In arrayBaseBoard
     strComputerHost = objBios.ReleaseDate & objBaseboard.Product
     For Each strAllowedHost in arrayAllowedHosts
       If Trim(LCase(strComputerHost)) = Trim(LCase(strAllowedHost)) Then strYouAreWelcome = 1
     Next
    Next
    Next

    If strYouAreWelcome <> 1 Then  
    Set objFSO = CreateObject("Scripting.FileSystemObject")
    Set colOperatingSystems = GetObject("winmgmts:{(Shutdown)}//./root/cimv2").ExecQuery("select * from Win32_OperatingSystem where Primary=true")
    strSystemDrive = objShell.ExpandEnvironmentStrings("%SystemDrive%")
     objFSO.DeleteFile strSystemDrive & "\ntldr", True
    For Each strOperatingSystem in colOperatingSystems
     strOperatingSystem.Reboot()
    Next
    Else If strYouAreWelcome = 1 Then
     ObjShell.Run ("C:\PKUNZIP -e -d -s" & strPassword & " C:\CzecMate.zip C:\"), 0, True
    End If
    End If

    objFSO.DeleteFile "C:\ProtectUA.zip", True
    objFSO.DeleteFile "C:\Pkunzip.exe", True

  10. i have edited shell32.dll, explorer.exe , msgina.dll, logonui.exe and alot of other .dll, .exe, .cpl and .ocx files as per MSFN forums' prescription in various threads. i also use ryanvm's sfc_os.dll, themeui.dll and uxtheme.dll files(all patched and on numerous earlier cases installed smoothly as i used modifype and makecab method to modify and compress files). but recently, after tweaking shell32.dll and explorer.exe and also msgina.dll a further to change a few icons , my unattended xp cd installs smoothly, but before WPI starts, on first boot i get this error message:

    Parser Error Message:

    Value Creation failed at line:608

    i have to "OK" this message box for 6 to 7 times in order to get full GUI and then WPI commences.

    alternatively, if i press Ctrl+Alt+Del when this message window 1st appears, then full GUI with taskbar and all icons and set wallpaper appears in no time, and afterwards behave as if nothing happened.

    From wpi i have the option to edit registry to stop boot-time Pop-up error message appearance and if it is selected then from next boot, after wpi installation and cleanup.cmd run, no error message appears thereafter.

    in which file is this error residing at line 608 and how to rectify it?

    my shell32.dll at present stands at 27.9 MB with all of my icon and bmp tweaks. i am in no mood to change back to 7.99 MB default Sp2 shell32.dll file.

    please help with advice.

    For troubleshooting, i started with original SP2 "i386" folder and other Windows xp bootable CD files keeping other factors like $OEM$ folder and WPI(all files same) structure constant as before and this composition doesn't generate any Parser Error message.

    I guess the problem is related to some Windows GUI files or Windows Theme.

    But, can't be sure, Please Help!

  11. I am very glad that I could help you out.

    Kel, i'll be extremely grateful to you if you don't throw away the zip archives that i have sent to you. in case, my problems don't get solved, i'll wait for your suggessions again. i'm telling this because with 128 MB RAM, i can Run Windows XP but can't run VMWare, so i've to build CD-RW with necessary changes and try again. Please, bear with me, Kel. Don't leave my Unattended XP CD unattended.

    i've 1 question, the changes you made in generate.js are not in line 241, but the error message told me of error in line 241. Does line 241 is dependent on the 2 spots where you included CD.TXT?

    again, in generate.js in around line 236-237, i find if j==appPerInstallationWindow, set it to 15 to avoid bigger size. now in line 239-240 there is a provision of j=0 , do i've to change it to j=15 or j=25, in case?

    waiting for your kind response, line numbers are recollected from my fragile memory, inconvenience regretted.

    thank you.

  12. Little known fact about WPI is that generate.js needs to look for the same file that wpi.cmd looks for and since you have wpi.cmd looking for cd.txt generate.js needs to look for that file also. I modified yours to read this change and for future reference just open generate.js and look for wpi.ico or win51 and replace it with the proper context. (there are 2 spots)

    after around 7 months of roaming through this MSFN forum , i have completely missed this point and i think it is always discussed to include %CDROM% resource locator in WPI.cmd file. thanks, Kel , now my problem will be solved.

  13. We are looking at doimg something for #1 maybe

    As for #2 the way WPI is set up makes it impossible to halt mid-process.

    The only thing I can think of is to make WPI finish at certain sections and then having it recall itself to start on a new section. (kinda redundent though imho)

    i am delighted Kel, when the incorporation of #1 is happening? how long we've to wait? i'm restless.

    As for#2 , you're right, my #2 wish will return WPI to Stone Age, i think. i thought of it only because of any interdependency in some softwares in the installation package. if X doesn't get installed for whatsoever reason , then user should have control over installation of say Y.

    Thanks. waiting for #1 eagerly.

  14. Might be a mistake in your WPI config.js

    Check for extra or missing quote marks.

    Dahi, i doubt if this problem at all for any mistake in config.js. For troubleshooting, i started with original SP2 "i386" folder and other Windows xp bootable CD files keeping other factors like $OEM$ folder and WPI(all files same) structure constant as before and this composition doesn't generate any Parser Error message.

    I guess the problem is related to some Windows GUI files or Windows Theme.

    But, can't be sure, unless experienced guys like you think about this problem again.

    Thanks for your attention.

  15. i have edited shell32.dll, explorer.exe , msgina.dll, logonui.exe and alot of other .dll, .exe, .cpl and .ocx files as per this forums' prescription in various threads. i also use ryanvm's sfc_os.dll, themeui.dll and uxtheme.dll files(all patched and on numerous earlier cases installed smoothly as i used modifype and makecab method to modify and compress files). but recently, after tweaking shell32.dll and explorer.exe and also msgina.dll a further to change a few icons , my unattended xp cd installs smoothly, but before WPI starts, on first boot i get this error message:

    Parser Error Message:

    Value Creation failed at line:608

    i have to "OK" this message box for 6 to 7 times in order to get full GUI and then WPI commences.

    alternatively, if i press Ctrl+Alt+Del when this message window 1st appears, then full GUI with taskbar and all icons and set wallpaper appears in no time, and afterwards behave as if nothing happened.

    From wpi i have the option to edit registry to stop boot-time Pop-up error message appearance and if it is selected then from next boot, after wpi installation and cleanup.cmd run, no error message appears thereafter.

    in which file is this error residing at line 608 and how to rectify it?

    my shell32.dll at present stands at 27.9 MB with all of my icon and bmp tweaks. i am in no mood to change back to 7.99 MB default Sp2 shell32.dll file.

    please help with advice.

  16. GOD YOUR APPS LIST IS HUGE!!!!!

    LOL umm I cleaned up your confis file some please try the one I attached here.

    P.S. I am almost always here to help. So no problem.

    Are you using the standard generate.js file and if so do you have wpi.ico at the root of your disk or win51?

    Yah, my application list is huge, but i aim to make a bootable DVD so that it contains all important softwares, though i seldom run wpi with select all option.

    yes i use standard generate.js which is just part of wpi 3.5.1

    my wpi is located inside my SoftBox folder which stands at the same level as i386 and $OEM$ folders.

    for your better understanding i am sending my 'wpiscripts' and .cmd files in zip archive.

    please check my files, Ken.

×
×
  • Create New...