jdoe

iron_du, There is no way to reduce ISO file from 883Mb to real CD limits. You'll have to think about burning a DVD or remove stuff from your CD.

some1, .bat and .cmd are batch files but .cmd only runs on NT and for 9x you must use .bat Each version of Windows have their supported command-lines so a .bat or a .cmd may not work on each Windows version. It depends on the features of a specific Windows. Maybe there is others distinctions but I only know these.

Sorry but this is not the String Table I expected and for editing the exe directly it will be hard to find the good one (and I suspect that maybe the text is taken from the registry). No luck

What is the exe. Post it and I will look at it. What is the string you want to change ?

I don't know Resource Tuner but you can search in the STRINGTABLE resource for the string you want to change. Other than that, I think you will need to play with disassembly and you'll be able to change some strings but not make it larger like you want. Good luck

I didn't play very much with Vista but for now only two things come to my mind about Vista that I don't like... 1) The minimum computer resource requirements 2) The classic Explorer Shell is gone These two points will make me wait for a new computer and then make a decision if I want those new GUI stuff before XP is not supported anymore by M$. Until then, I'm very happy with XP and will stick to it.

I'm another Notepad2 user because it is self contain into a single exe. It is a very smooth syntax highlighting for coding purpose. Support ASCII and UNICODE. And it is very stable. The only thing that was annoying to me was the message "Are you sure you want to open this large file...". I removed this message by patching offset 56ECh from 7338 to EB38 (version 1.0.12). I tried all the others text editors mentionned but they are too much for my needs. BTW, one bad side about Notepad2... it seems to be no development on it anymore.

Jorex, You are the one who don't understand. Not all programs get registered like that. ricktendo64 showed you how DriverGenius get registered. It is a key file in the same directory of DriverGenius. Don't search your registry for that key, you won't find it. When you run DriverGenius, the program search for that file and read the contents and the program know if it is registered or not. Do you need more help ?

Like this it could work... >>diag%x%.rc echo STYLE DS_FIXEDSYS ^| DS_MODALFRAME ^| DS_CENTER ^| WS_POPUP ASCII 94 before |

@jaclaz, My post was not technically strong as yours. You did a good search. My post only refer to a test I did long time ago about the idea of using UPX to compress Windows Portable Executables and it was leading to a considerably slow OS. I don't have any technical information to prove my point but I know that in a real test, I got that result.

@Francesco, It would make the Windows install smaller but surely not faster. Compression means decompression and it take extra time for PE to loads so the OS will be SLOWER.

Read this... Naming a File

Type con and alt+255 to get characters by their number (not only for ASCII but for UNICODE either) ---------------------------- Reserved device name CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9

4758

For VB6 I think it should look like this... Option Base 1 'Not sure but... Dim iPrevDigit As Long Dim iCount As Long Dim sUnlock As String Dim sSerialNo() As String ... ... ... iPrevDigit = 17 sUnlock = "" For iCount = UBound(sSerialNo) To 1 Step-1 sUnlock = CStr(CInt(sSerialNo(iCount)) + iPrevDigit) & sUnlock iPrevDigit = CLng(sSerialNo(iCount)) + 17 + Int(iCount / 2) Next iCount ... ... ... I don't know Delphi or very few, so I can be wrong.

@Silurian Ok, you have a problem with a stock program which seem to be some kind of coding homework because as far as I remember, teachers always ask to build a stock program. Your lucky, this board don't have rules about homework. Is it difficult at this point to post what your problem is (and maybe give some source code to look at), this way someone could give you an answer. I repeat. IS IT DIFFICULT AT THIS POINT TO POST WHAT YOUR PROBLEM IS. Are you familiar with boards. Do you know the basic rules about it. I won't help because I never used Delphi but you seem to not knowing what you want and you won't get any help without a question.

YES, there is all language coders on this board. You should post your real question about your current coding problem instead.

With Windows XP you don't need choice.com anymore. Search this forum or the web for the SET /P command. I'm sure you'll find what you need with full of examples.

B) Const test = "KB1234567.exe" Dim strFileName Dim lngKbNumber strFileName = test If UCase(Left(strFileName,2)) = "KB" Then If UCase(Right(strFileName,4)) = ".EXE" Then On Error Resume Next lngKbNumber = CLng(Mid(strFileName,3,InStrRev(strFileName,".")-2)) On Error Goto 0 If Err = 0 Then 'Your code here End If End If End If

If Base 1 is not specified, dwSum(0), dwSum(1), dwSum(2) and dwSum(3) are the four Long needed. From the include file MDxSum STRUCT dwSum1 dd 0 dwSum2 dd 0 dwSum3 dd 0 dwSum4 dd 0 MDxSum ENDS

Hi Guitaraholic, It's been a long time since I play with winnt.sif but giving a fast look at your .sif I can point a mistake from the [unattended] section. [Unattended] UattendSwitch="yes" should be... [Unattended] UnattendSwitch=Yes Just a missing N and quotes are only needed when there is spaces (KeyboardLayout="United Kingdom")

Search on this board (or Google) for WINNT.SIF and the [PCHealth] section This is what I have in mine... [PCHealth] ER_Display_UI=0 ER_Enable_Applications=None ER_Enable_Kernel_Errors=0 ER_Enable_Reporting=0 ER_Enable_Windows_Components=0 ER_Include_MSApps=0 ER_Include_Shutdown_Errs=0

Hi there, I was loosing time looking at my site stats and I saw this link. I don't think COM+ is the same as COM. COM is deeply a part of Windows so it can't be removed because important part of it wouldn't work without it. Let me show you a way to do it (but it is untested). Make sure catsrvut.dll is not removed by nLite. All the registry keys and values will be added if you register catsrvut.dll with this command "regsvr32.exe catsrvut.dll" (after or while the setup process). That's all. -------------- I'm pretty sure it's going to solve the problem. Let me know

I found it funny that VB.NET doesn't solved that behavior that was in VB6 also. Using APIs this is what I did with VB6 to avoid form freeze and not taking too much resource. Public Function RunCommand( _ ByRef r_sCommand As String, _ Optional ByRef r_lWindowStyle As Long = API_SW_SHOWNORMAL) As Long Dim udtSA As SECURITY_ATTRIBUTES_API Dim udtSI As STARTUPINFO_API Dim udtPI As PROCESS_INFORMATION_API Dim lExitCode As Long RunCommand = -1234567891 udtSA.nLength = Len(udtSA) udtSI.cb = Len(udtSI) udtSI.dwFlags = API_STARTF_USESHOWWINDOW udtSI.wShowWindow = r_lWindowStyle If ApiCreateProcess(vbNullString$, BetweenQuotes(r_sCommand), udtSA, udtSA, _ API_TRUE&, API_NULL&, ByVal API_NULL&, vbNullString$, udtSI, udtPI) Then While ApiWaitForSingleObject(udtPI.hProcess&, 100&) = API_WAIT_TIMEOUT DoEvents Wend If ApiGetExitCodeProcess(udtPI.hProcess&, lExitCode&) Then RunCommand = lExitCode Else RunCommand = -1234567890 End If ApiCloseHandle udtPI.hThread& ApiCloseHandle udtPI.hProcess& End If End Function Hoping it can be translate to VB.NET.

which one should i change? I have PM nuhi hoping he would find some time to answer. Instead of storing two copy SYSSETUB.DL_ and SYSSETUP.DL_ in source folder and renaming it with nlhive.inf at 1st GUI launch we can try to reverse patch on the patched DLL and get back to original unpatched syssetup.dll Could you help me to write the xsc script. Or for starting with this stuff, is the example for patching XP SP2 ENU syssetup.dll according to infos posted at your patches Webpage correct. something like: %ProgramFiles%\xvi32\XVI32.exe %temp%\syssetup.dll /S=%ProgramFiles%\xvi32\syssetuprepl.xsc 33679 73 72 REM goto offset %1 ADR $%1 REPLACE %2 BY %3 Merci pour l'aide que tu pourras m'apporter, ami francophone de l'autre côté de l'océan. Thanks for help. @Bilou_Gateux I replied to your PM before reading this post. Now I know what you are trying to do. Maybe I'm not aware of something but what is the problem with keeping the patched syssetup.dll after the installation. About reversing the patch, it could be done but I think WFP will block writing the dll. Like I said in the PM I sent you, it is easy to write a very small program (something like 3-4Kb) that will patch and unpatch from command line with a switch like /P and /U but does Windows will let writing to it without complains. I don't know.