r3incarnat0r

If you need so many variables, you should rather consider to use an array of them imo: Dim tmp(2) As Integer 'array of 3 integers - tmp(0), tmp(1) and tmp(2) Dim ints() As Integer = {2, 4, 0, 5, -1} 'array of 5 integers Dim tmpint As Integer = 0 For i = 0 To ints.Length - 1 'i.e. ints(0) to ints(4) tmpint += ints(i) 'adds all values Next 'tmpint will be 2 + 4 + 0 + 5 - 1 = 10

Thanks for suggestions, but I think I already decided - the app will be DriverSeek, if there are no cons until next release.

TextBox3.Text = CInt(TextBox1.Text) + CInt(TextBox2.Text) or if you have option strict on: TextBox3.Text = CStr(CInt(TextBox1.Text) + CInt(TextBox2.Text))

Thanks for reply. I agree with trailing ".NET", makes the name long and complicated. However, there's another problem - "DeviceTool" name indicates that the app should do something with devices, but actually it will be rather intended to do something with drivers. This led to rename the app to "DriverTool" (which was my original idea anyway), but such things already exist. Then I started to looking for a word to replace the "Tool" string and found some nice examples in english dictionary: bring, direct, expose, point, fetch, seek, probe, locate, quest, stalk, hunt, find, reveal, hit, uncover, sight, espy I was also thinking if the name based on "Driver" is acceptable, because it's not obvious what kind of "driver" is meant - device driver, bus driver, ... Fortunately I remembered the name "Windows", so I decided the "Driver" is not a big deal. Considering my naming conditions (must not exist, not too long, not complicated, well pronounceable, can't sound stupid/weird/extremely cool), I got several acceptable results: DriverSeek, DriverProbe, DriverHunt, DriverUncover B) I liked the "DriverSeeker" variant, it sounds good to me and reminded me "Legend of the Seeker" but Google returned exact matches, so I cut it just to "DriverSeek". So it looks like there's one decision left (to choose the one of the proposed names) instead of more "excogitation". You're right with the name, that's me who's mad, but some minor features will be introduced first, since they're basically products of my code adjustments and preparing the architecture to be more flexible, so I could be able to add future upgrades much easier. As I said, I'm a beginner in VB.NET, until now I was just writing some .CMD scripts from time to time, so I'm fighting a bit with the object oriented way of programming and as I'm trying to write, sort and separate the code to classes, modules, structures etc., it forces me to think a lot and I need to proceed step by step, because the mess in the code and the need to rewrite the whole app from the scratch would probably lead to discontinue the project due to my laziness.

OK, now I have an idea, which is not so scary as my previous ones - what about DeviceTool.NET?

Hi, I have recently begun discovering Visual Basic 2008 Express Edition. After I learned how to make classes and such, I've finally started to develop an experimental application. At the moment it can do nothing except displaying list of devices in system (and worse than the Device Manager so far), so basically it's not useful at all (yet). How does it work? The program searches through registry keys like... HKLM\SYSTEM\CurrentControlSet\Enum\{enumerator}\{deviceID}\{deviceInstance} HKLM\SYSTEM\CurrentControlSet\Control\Class\{classGUID}\{driver}...to read, filter and store a list of device instances including some info. It means the program does not enumerate any devices by itself, just reads from registry, so in the future it shouldn't be a problem to display the devices' state for example from a damaged system of a different computer, after connecting its registry hive. B) Why am I doing this? 1) I want to use this app for some service purposes (see long-term TODO list). 2) I want to practice VB.NET and then try to make a bigger project or something. My weird problem is that I don't know how to name the application. The names I thought up either already exist or I just didn't like them, so I'm asking you for suggestions. If you are willing to help, please look at the TODO list below to see what features are expected and know what the program is supposed to do. VB.NET 2008 apps require .NET 3.5 by default, but I compiled it to require just 2.0. 0.1 TODO list: [#1] General: Name of the app!!! (required for release) [#2] General: Choose a license 0.2 TODO list: [#3] Internal: Optimize ClassGUID loading [#4] Feature: Properties window (only devices for now) [#5] Feature: Log window (info, warnings and errors go here) [#6] UI: Icons for devices (depends on #3) Long-term TODO list: [#?] Major feature: Mount off-line registry hives (probably using REG.EXE) [#?] Major feature: Help to identify an unknown hardware (off-line XML database + on-line web search) [#?] Major feature: Ability to backup/export drivers (even from off-line damaged system, I hope) Screenshot: Executable (in 7z archive) is attached, if you want to try out. hwlist_0010_20090408.7z

Hi, 1) Go to Unattended page > RunOnce tab. 2) Copy/paste following text, customize the highlighted string and add as command. 3) Do not select Internet Explorer\Set Homepage tweak

Follow this link... http://www.msfn.org/board/Revert-Tweak-t104496.html

Looks like you don't require too much to fall in love...

To revert the tweak, merge a *.REG file with this content: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer] "NoInstrumentation"=- "NoStartMenuMFUprogramsList"=- [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\Settings] "NoEncrypt"=- "NoLog"=-

This post explains the difference: http://www.msfn.org/board/index.php?s=&amp...st&p=587678 Imo there's no performance harm after changing this tweak, but as you use classic style without fx, "Normal" option should be default for you.

Apply a REG file containing: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\exefile\DefaultIcon] @="%1"

If you enable "Show Advanced", "Enable" and "Disable" options appear in its branch. So I guess that nuhi forgot (or had an another reason) to make this object hidden (as well as "Allow receiving Remote Assistance").

OK, there's a solution: If you want to edit registry defaults for new users in already installed system, run regedit.exe, click on the HKEY_USERS item, File menu, Load Hive..., open C:\Documents and Settings\Default User\NTUSER.DAT. Enter any key name, then browse to its Software\...\RunOnce subkey and create a required value there. Don't forget to unload the hive, before you exit the editor. (source) If you wish to add a command to nLited installation files, open the I386\NLITE.INF file (compessed by CAB) and to the [TO] section add an entry similar to a line containing "nltide_3" string (copy/paste/edit value name and value). To edit the NLITE.IN_ file, you may use this script.

@0d14r3: np @gulias: I just tried it and you're right - it doesn't work. I'm gonna figure it out soon.

Sure. Run regedit.exe and expand HKEY_USERS key...

What registry value did you create? (Export to *.REG please, so I can see exactly what's wrong.)

Try to search files containing text "NoRecentDocsMenu". Try to not to use Windows Explorer, it has a search bug. If you find it, make sure the value is 0. I recommend to do so. I meant it in this way, but I'm not sure, if it's the best method. Each nLite version is little different, so check all the options again anyway. (By "check" I mean "revise", not make all the checkboxes checked. ) You are expected to know it. Perhaps the newest one?

Hi, I guess that it should work if you add such command to this registry key: HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\RunOnce

That's all kinda weird. You don't need to delete Last Session.ini. You should always use a clean installation and load the Last Session.ini file to make the most of your previous settings automatically selected before nLitement. It's because the nLite is under development and new versions could contain some bugfixes, solve some compatibility issues, etc. So if you are still "recycling" old installation source, old bugs have to be kept as well. Imho you're lucky that you have a problem only with the tweak. nLite does not use nlhive.inf method to apply tweaks anymore, i.e. this file shouldn't be present. Anyway, this file has a similar structure like nlite.inf, so just search for the values we were talking about in the posts above and delete the lines which contain them.

Unchecked selection in nLite does nothing - setting is written only if it's checked. If the selection is checked automatically, depends only on Last Session.ini. So if a setting is already applied in the installation, imho it shouldn't be removed this way (I guess). Do you mean that you're nliting already nlited installation? Do you have a nlhive.inf file present somewhere in your installation files? It has never worked for me, too. Did you integrate gpu driver?

Hi, use makecab command to compress the file: MAKECAB NLITE.INF Btw, I wrote a small CMD script which allows to edit NLITE.INF comfortably. Place it to a nlited windows installation directory and run. This will: make a backup of NLITE.IN_, extract the INF file, open it with Notepad and when you exit the Notepad, edited file will be compressed back. B) @echo off & set workdir= if exist NLITE.IN_ set workdir=%CD% if exist I386\NLITE.IN_ set workdir=%CD%\I386 if not defined workdir ( echo NLITE.IN_ not found. & pause & goto :EOF ) chdir /D "%workdir%" if not exist NLITE.BAK copy NLITE.IN_ NLITE.BAK if exist NLITE.INF del /F NLITE.INF expand.exe -r NLITE.IN_ start /WAIT notepad.exe NLITE.INF del /F NLITE.IN_ makecab.exe NLITE.INF if exist NLITE.IN_ del /F NLITE.INF

It's stored in I386\NLITE.IN_ - an INF file compressed by CAB format. Search for entries I posted above and delete the lines containing them.

The last character is a hyphen. I expected you to copy/paste the text directly to a file. I'm not sure if I understood the second sentence. Did you mean that recent documents menu item was not shown at all or it's content (a list of recently opened files) had been deleted? There's also a tweak which forces the recent docs list removal on each logoff. In that case this will disable it: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "ClearRecentDocsOnExit"=-

The REG I posted reverts the tweak called "Disable and remove Documents list from the Start Menu". If it will fix it, just uncheck this option on the "Tweaks" page in the "Start Menu" branch.