jaclaz

Well, Ranish likes to play it safe, he had for something like one year version 2.38 Beta, then he just renamed it to 2.40 stable. I have used both 2.40 and 2.43 beta with no problems whatsoever, actually the only (I think) difference, it is the number of partitions: Version 2.37: can help you have 30 primary partitions but does not work with disks having a capacity greater than 8GB. Version 2.40: can work with disks > 8GB but does not support more than 4 primary partitions (this is same as version 2.38 but just the version number got changed) Version 2.43: can work with disks > 8GB; also, it can support up to 30 primary partitions. As I would never want to have more than 4 Primary Partitions, I stay on 2.40. Never tested 2.44 BETA-BETA-BETA jaclaz

Try FONTTWISTER: http://www.neuber.com/twister/index.html jaclaz

It looks like you have a problem here: %RAMD%:\extract /y /e /l %RAMD%: ebd.cab > NUL it looks like RAMD is empty, make sure that BEFORE you assign a drive leteer to RAMD, like this: SET RAMD=X: then, I think you have a problem with "\" and ":" If RAMD = something like X: you do not need the : If RAMD = something like X:\ you do not need the \ If RAMD = something like X you miss a \ in the second part. Moreover I do not think that EXTRACT.EXE is ALREADY on RAMD! Assumed that RAMD is something like X your line should be: extract /y /e /l %RAMD%:\ebd.cab > NUL jaclaz

Get this nifty FREEWARE: RANISH PARTITION MANAGER http://www.ranish.com/part/ READ THE INSTRUCTIONS USE IT PROBLEM SOLVED (please note that Powerquest Partition Manager, in a few occasions, deals with partitions in non-standard ways, so, even if all works with it, double check the settings of the partitions with Ranish's) jaclaz

To make it safe, you should always run the command like this: xcopy32 [source]:\*.* [destination]\*.* /i /s /e /r /v /k /f /c /h or xcopy32 [source]:\*.* [destination]\*.* /i /s /e /r /v /k /f /c /h /y if you don't have it in your COPYCMD Note: Xcopy is just a redirection to XCOPY32 /s and /e could be condensed in just /e, but as Nick Rage put it, We even made it easy to remember.. I SERVe Kentucky Fried Chicken Hot! or I SERVe Kentucky Fried Chicken Hot, Yeah! jaclaz

Actually, it is possible to recover data even on encrypted partitions, but it will cost you: http://www.elcomsoft.com/prs.html#aefsdr jaclaz

Easier way is to use Franck Uberto's RAMDISK. At boot you just need the basic Dos files and a config.sys/autoexec.bat that creates the RAMDISK, then you copy all Dos files to RAMDISK, not unlike a "normal" 98 boot diskette does. Frank Uberto's is better because you do not have the limit in size of the MS RAMDISK, 32 Mb. You can even, with some caveats, run Windows 3.11, 95, 98 or ME from RAMDISK. Find here some useful info: http://www.geocities.com/politalk/rmdrv/index.html jaclaz

@SiMoNsAyS Well, no, the copywriter Mikio or Mikko seems having had a lack of fantasy, it's the same thing over and over: 1J) Kan Co Co to ne jo e jo ko so=1E)Welcome to Japan and Korea 2J) Ganbareh=2E)Go ahead, and have lots of fun! 3J)Wa ure cap udi sen di ne Sens egarega ni hon to can co=3E)The World Cup 2002 is right now and so the whole world is watching Japan and Korea ...and then it goes on 2) 2) 3) 2) 2) 2) 3) 2) 2) jaclaz

It is japanese, Ganbareh means either: "Go Out and Play" or "Go ahead, and have lots of fun!" See info here: http://users.pandora.be/gertje1/disc.bak and a possible translation here: http://www.planetsash.co.uk/Low/Low/Transl...Translation.htm jaclaz

You might want to have a look at 7zip, it is quite compact and easily modifiable: http://www.7-zip.org/ it does not actually need to be installed, all libraries you do not need can be deleted, writes very little info to the registry when run. jaclaz

Most probably you were looking for this info: http://support.microsoft.com/default.aspx?...&NoWebContent=1 and this might be useful too: http://support.microsoft.com/?id=227707 In your case it should go like this: Disk 1: 1st primary <-if ACTIVE gets letter C: 2nd primary <-this one is ignored, or skipped, then assigned J: (but not always, depends on which system/which filesystem) 1st logical <-this one is skipped at first pass, then becomes E: Disk 2: 1st primary <-gets letter D: 1st, 2nd, 3rd 4th logical <-these are skipped at first pass, then become F:,G:,H:,I: CD1 (DVD); <-finally gets letter J: or K: (see above) CD2 (CD-RW); <-finally gets letter K: or L: (see above) It is NOT RECOMMENDED to have more than one PRIMARY partition visible to NT/2K/XP. Moreover, the best thing is to plan the partitioning so that Dos/Windows and NT/2K/XP give the same letters to the same drives. Hope the above helps. jaclaz

My two cents: if you just want to give a "windows look" to an installer program you already have written as .bat or .cmd, have a look at this little nifty tool: http://wizapp.sourceforge.net/ I have found it very easy to convert existing batches in "pseudo" windows apps. The .exe is only 70 kb. jaclaz

Well, it seems that the idea of having two mice is not new, but of course there are reasons why you should NEVER have two mice together: jaclaz

Yep. lpl is right, What nodiaque should have posted is, presumably, this: C, 1, 20 Gigs PRIMARY D, 1, 100 Gigs LOGICAL E, 2, 40 Gigs PRIMARY F, 3, 160 Gigs LOGICAL Any DOS/WINDOWS adopts this convention, (as you might know, no MS kind of FDISK allows you to make more than one primary partition per each disk): Letter A: is reserved for first floppy Letter B: is reserved for second floppy Letter C: is reserved for first PRIMARY partition on first drive Subsequent letters are given to all other PRIMARY partitions in the order of the number of the drive. When all PRIMARY partitions have got their letters assigned, lettering restarts from first LOGICAL partition on first drive and goes on like above. The solutions to your problem could be to convert the PRIMARY partitions on second drive to LOGICAL. This COULD be made with Partition Magic, but there are reports of people LOOSING DATA in the process, so I would rather MAKE A FULL BACKUP OF DATA before attempting to do it. As a general rule, one must plan the partitioning of disks in a manner that letter assigning, at least for the partitions where system files reside, is the same as the automatic given one. jaclaz

@Aaron as correctly pointed out by Alanoll, there is this little (22kb) standalone utility that can manage shortcuts and much more: NirComLine v1.20 Copyright © 2003 Nir Sofer NIRCOMLINE.EXE shortcut [filename] [folder] [shortcut title] {arguments} {icon file} {icon resource number} {ShowCmd} {Start In Folder} Creates a shortcut to a file. The parameters: [filename]: Create a shortcut to this filename. [folder]: Specify that destination folder that inside it the shortcut will be created. You can specify any valid folder (like "c:\temp\1234") or one of the following special folder values: /desktop - Creates the shortcut in the user desktop folder. /startup - Creates the shortcut in the user startup folder. /programs - Creates the shortcut in the user start menu\programs folder. /start_menu - Creates the shortcut in the user start menu folder /common_desktop - Creates the shortcut in the desktop folder of all users. /common_startup - Creates the shortcut in the startup folder of all users. /common_programs - Creates the shortcut in the start menu\programs folder of all users. /common_start_menu - Creates the shortcut in the start menu folder of all users [shortcut title]: The text displayed in the shortcut. {arguments}: Optional parameter - Additional arguments to execute the filename. {icon file}: Optional parameter - Use this parameter if your want that the shortcut will be displayed with icon other than the default one. {icon resource number}: Optional parameter - The resource number inside the icon file. {ShowCmd}: Optional parameter - Use this parameter if you want to maximize or minimize the window of the program. Specify "max" to maximize the window or "min" to minimize it. {Start In Folder}: Optional parameter - Specifies the "Start In" folder. If you don't specify this parameter, the "Start In" folder is automatically filled with the folder of the program you specify in [filename] parameter. Examples: shortcut "f:\winnt\system32\calc.exe" /desktop "Windows Calculator" shortcut "f:\Program Files\KaZaA\Kazaa.exe" "c:\temp\MyShortcuts" "Kazaa" shortcut "f:\Program Files" "c:\temp\MyShortcuts" "Program Files Folder" "" "f:\winnt\system32\shell32.dll" 45 shortcut "f:\Program Files" "c:\temp\MyShortcuts" "Program Files Folder" "" "" "" "max" that you can find here: http://nirsoft.multiservers.com/ jaclaz

From the type of error you get it seems like the command interpreter takes one of the parameters as the name of a file, and, not finding it, gives the error. You COULD try something like the following: SET COMMAND1="C:\Program Files\DIKO\FreeEnc\FreeEnc.exe" SET PARAM1=/i SET COMMAND2=C:\finals\scripts\11.avs SET PARAM2=/o SET COMMAND3=C:\finals\mpvs\11.mpv SET PARAM3=/2 /b 2000 /aspectratio 4:3 /gopsize 18 /maxbitrate 4000 /priority 5 /dc 8 /mpeg2 /scene /extreme /maxbframes 2 /kvcd /auto /close start /wait %COMMAND1% %PARAM1% %COMMAND2% %PARAM2% %COMMAND3% %PARAM3% ::Clear up Environment Variables used SET COMMAND1= SET PARAM1= SET COMMAND2= SET PARAM2= SET COMMAND3= SET PARAM3= and partialize it to understand which part causes the error. Though seemingly more complex, this way it makes it easier to change paths to the files. Please note that you only need quotes in the COMMAND1 string as there is a space between 'Program' and 'Files' jaclaz

Boot.ini is quite simple, here is an example: [Boot Loader] ::This is the title of the 1st section Timeout=5 ::This is the timeout before default item is loaded Default=multi(0)disk(0)rdisk(0)partition(3)\WINNT ::This is the default item [Operating Systems] ::This is the title of the 2nd section ::Following are actual entries ::First part is the arc path to the partition ::Second part (after the = sign) is the text you see followed by OPTIONS multi(0)disk(0)rdisk(0)partition(1)\WINNT="Win2k 1st disk 1st partition" /fastdetect multi(0)disk(0)rdisk(0)partition(2)\WINNT="Win2k 1st disk 2nd partition" /fastdetect multi(0)disk(0)rdisk(0)partition(3)\WINNT="Win2k 1st disk 3rd partition" /fastdetect :: and so on... multi(0)disk(0)rdisk(1)partition(1)\WINNT="Win2k 2nd disk 1st partition" /fastdetect multi(0)disk(0)rdisk(1)partition(2)\WINNT="Win2k 2nd disk 2nd partition" /fastdetect multi(0)disk(0)rdisk(1)partition(3)\WINNT="Win2k 2nd disk 3rd partition" /fastdetect :: and so on... Here is the complete reference to arc paths: http://support.microsoft.com/default.aspx?...b;en-us;q102873 Here is the complete reference to OPTIONS: http://www.sysinternals.com/ntw2k/info/bootini.shtml Here is a good GUI editor for Boot.ini: http://www.dx21.com/SOFTWARE/Dx21/ViewItem...I=2&SI=2&OID=14 Here is the "MAGIC" program that lets you repair Boot.ini, the bootsector of the drive and many more: http://www.winimage.com/bootpart.htm jaclaz

Your original listing works in Opera, however. Maybe it is some settings in your copy of Firefox. jaclaz

Well, as John Newbigin, author of dd for windows and rawrite for NT, clearly states, Real programmers drink Coke! http://uranus.it.swin.edu.au/~jn/coke.htm jaclaz

This is a good site with photos of REAL SIGNS: http://www.getawaytoafrica.com/content/mag...signs/index.asp Here is a good example: jaclaz

This is one way: Windows NT and Windows 2000 You can disable Ctrl-Alt-Del on NT and 2K but this is very risky. It can prevent you from ever being able to log on again! Be sure to enable Automatic Logon by specifying DefaultDomainName, DefaultUserName, DefaultPassword and AutoAdminLogin in the registry under Windows Login. Otherwise you will not be able to logon again. See Knowledge Base article Q114615 for details - there is a link on my links page. You may also want to read my disclaimer page. After you set up automatic logon the logon dialog no longer appears at startup. You are then unable to logon as a different user until the automatic logon and below code is disabled in the registry. You may be able to temporarily bypass the automatic logon by holding down the Shift key as windows is starting This code was donated by Paul Johnston. Public Sub SetupScancodeMap() Dim bArray(1 To 48) As Byte On Error Resume Next If g_bDebugMode = True Then Exit Sub ' ' Setup the keyboard scancode mapping to disable the Windows keys ' and Context menu keys ' bArray(1) = &H0 bArray(2) = &H0 bArray(3) = &H0 bArray(4) = &H0 bArray(5) = &H0 bArray(6) = &H0 bArray(7) = &H0 bArray(8) = &H0 ' ' Number of keys ' bArray(9) = &H6 bArray(10) = &H0 bArray(11) = &H0 bArray(12) = &H0 ' ' Windows key ' bArray(13) = &H0 bArray(14) = &H0 bArray(15) = &H5B bArray(16) = &HE0 ' ' Windows key ' bArray(17) = &H0 bArray(18) = &H0 bArray(19) = &H5C bArray(20) = &HE0 ' ' Windows menu key ' bArray(21) = &H0 bArray(22) = &H0 bArray(23) = &H5D bArray(24) = &HE0 ' ' F10 key ' bArray(25) = &H0 bArray(26) = &H0 bArray(27) = &H44 bArray(28) = &H0 ' ' Left Ctrl-key ' bArray(29) = &H0 bArray(30) = &H0 bArray(31) = &H1D bArray(32) = &H0 ' ' Left Alt-key ' bArray(33) = &H0 bArray(34) = &H0 bArray(35) = &H38 bArray(36) = &H0 ' ' Right Ctrl-key ' bArray(37) = &H0 bArray(38) = &H0 bArray(39) = &H1D bArray(40) = &HE0 ' ' Right Alt-key ' bArray(41) = &H0 bArray(42) = &H0 bArray(43) = &H38 bArray(44) = &HE0 ' ' Null terminator ' bArray(45) = &H0 bArray(46) = &H0 bArray(47) = &H0 bArray(48) = &H0 ' ' Set the new registry value, does not take effect until the next reboot. ' You can use my registry module or your own routine to write the value to the registry. ' Reg_SetKeyValue HKEY_LOCAL_MACHINE, "SYSTEM\CurrentControlSet\Control\Keyboard Layout", "Scancode Map", bArray, REG_BINARY End Sub If you use this code, please mention "www.TheScarms.com" Found here: http://www.thescarms.com/vbasic/StopReBoot.asp And here is another method, involving a new GINA STUB: http://www.dotnet247.com/247reference/msgs/36/181489.aspx Hello, Thanks for your post. As I understand, you want to trap and disable Ctrl-Alt-Delete programmatically in Win2K. Please correct me if there is any misunderstanding. I reviewed your description carefully, and now I'd like to share the following information with you: 1. As documented in the article to which you pointed, you can use DisableTaskMgr to disable Ctrl+Alt+Del. To trap Ctrl+Alt+Del, you have three options: write a GINA stub, write a keyboard driver, or replace TaskMgr.exe with your own program. I recommend you create a GINA stub which is comparatively easy to implement among these three options. 2. However, we have to use VC instead of VB to implement a GINA Stub. As you know, a GINA Stub is a native dynamic-link library (DLL) exported to Winlogon that requires a valid, consistent function to call into. This requires a DLL export, which .NET Framework does not support. Managed code (VB .NET, C#) has no concept of a consistent value for a function pointer because these function pointers are proxies that are built dynamically. 3. There is an existing GINA Stub sample in MSDN. To trap/disable Ctrl-Alt-Delete, you just need to replace its WlxLoggedOnSAS with the one in my code snippet below. GinaStub Sample: Pass-through "Stub" Gina http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcsample98/ html/vcsmpginastubsample.asp?frame=true /*----------------------------code snippet----------------------*/ int WINAPI WlxLoggedOnSAS( PVOID pWlxContext, DWORD dwSasType, PVOID pReserved) { if (dwSasType == WLX_SAS_TYPE_CTRL_ALT_DEL) { /* Add additional code of you own */ return WLX_SAS_ACTION_NONE; } else return GWlxLoggedOnSAS( pWlxContext, dwSasType, pReserved ); } /*-----------------------------end of--------------------------------*/ In addition, I believe the following MSDN aritcles are helpful: WlxLoggedOnSAS http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/se curity/wlxloggedonsas.asp Loading and Running a GINA DLL http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/se curity/loading_and_running_a_gina_dll.asp Please feel free to let me know if you have any problems or concerns. Have a nice day! Regards, HuangTM Microsoft Online Partner Support MCSE/MCSD jaclaz

Ali1978, if I get it right, you just need to make some remote registry modifications, right? Could you not just boot up all PC's normally, then remotely modify the registry, something along the lines of this articles? http://www.windowsitlibrary.com/Content/69/07/1.html (old) http://www.winnetmag.com/Windows/Articles/...714/pg/2/2.html (new) jaclaz

I like RegSeeker, FREEWARE for personal use. http://www.hoverdesk.net/freeware.htm I never tried RegSupreme, (suggested above), but I did try a variety of other regcleaners, and this one stands out. Together with it I use these also: Oleclean http://www.geocities.com/drdole/ScreenShots/OleClean.html and Regctrls http://www.softcircuits.com which are very good in refining the job done by RegSeeker. jaclaz

@FloDiggs If the problem is just to password protect BOOTING in WinPE, you could use a boot manager like XOSL that can password protect some boot items. XOSL page: http://www.ranish.com/part/xosl.htm jaclaz

You could try to use this nifty utility from Nirsoft: http://nirsoft.multiservers.com/ To enable/disable service from command line or batch file. NIRCOMLINE http://nirsoft.multiservers.com/utils/nircomline.html But before that, try interactively with the in built Service Manager or (better) with this other Nirsoft utility: SERVIWIN http://nirsoft.multiservers.com/utils/serviwin.html With which is easier to manage dependencies. (I suspect that setting the start as automatic does not actualy start the service if there are any stopped depencies or until reboot, so you should try starting the service manually, see if it works, then reboot) if it doesn't work, check dependecies first, than experiment with the other possible settings, i.e. 0 or 1 for the "Start" key BOOT_START 0x00000000 SYSTEM_START 0x00000001 AUTO_START 0x00000002 DEMAND_START 0x00000003 DISABLED 0x00000004 jaclaz