TheMadGuy

This is very weird, i have hardly tried to reproduce this error, using different winntbbu.dll's and making no or different changes. I just cant raise this error would you be willing to run a special debug version, if so i will build one which will produce a special .log file, since i currently have no idea why a lock is kept open! Besides that it would be nice if you could look at this Post and get unlocker to verify it's the editor itself keeping the lock open. Any help is highly appreciated on this one

Hi! The current version doesnt support complete removel of those logos yet, for now you can as a workaround replace it with a 1x1 image, or remove it with the ResourceEditor of your choice. The next version however will allow you to remove the logo with the editor aswell!

Mhhh, maxXPsoft already reported a similar problem, i cant reproduce this error though. Can you give me a step by step report of what you did to the point where the error came up ?

Take your time! Any help on this is very welcome! On a side note, As it seems, there have to be additional sources for texts displayed. During setup there are texts which seem not to have their origin in either winntbbu nor syssetup.dll. So if any one can point me in the direction where to look for them.... I'm listening

Hi! Thnx! This has already been suggested and has been added to the ToDo List, so expect it to be added in one of the coming versions sometime. This is a low priority Freature at the moment though. So dont expect it in the next version yet. But still any suggestions are welcome!

Ok, solved the MakeCab issue aswell, i had assumed MakeCab would cab the file in the same dir as the sourcefile, which isnt true, it cabs to the current path. Now i pass a path to the call aswell, seems to be working fine now Next release will have it working.

Nothing to be ashamed of The worst and boring part is, you have to sit next to setup and watch it the whole time, note down all the texts that get displayed in the bottom left. Then open syssetup.dll e.g. in ResourceHacker and go through the StringTables, if you find a matching string note down its ID (in ResourceHacker the number on the left) and post them here. Thats all

Oh Boy! Stupid me! The filename check, if it is a compressed dll, which determined by the suffix of .dl_, is case sensitive Shame on me.... if you rename your file from ".DL_" to ".dl_" it instantly works .... Will fix this in the next release 4 sure! But Saving & Cabbing works fine for me, even with your dll when in the same dir as startet with, but i'll look further into it aswell. @maxXPsoft Maybe you can grab Unlocker and see if there are any locks open ? This would already help!

Mhhh, seems theres still is a lock open on the file.... Have to look into that... But i totally dont understand why makecab doesnt work..... anyways, will try to figure it all out...

Well me removing my shell.reg is like me sneeezing, been messing with the registry since it was introduced in Win95. I get the right click WinntbbuED on the .dl_ but it errors out telling me its not a valid winntbbu.dll file and then it loads his program with the program defaults, in Deutsch. I'd presume you not really editing something then. Then I take a look at my CD copys of XP Home/Pro and 64 bit and find that only the 64 bit has that dll compressed for actual source. I'm just telling TheMadGuy what I'm seeing so he can look at those things, Feedback is necessary to all programmers, that I KNOW. I don't know if he expands the .dl_ when you right click it and its not happening on my system. <{POST_SNAPBACK}> Totally Agreed! Any Feedback is good! So, I'm reading the file's version information of the winntbbu.dll to verify its actually a valid one so it seem expanding did take place... Can you verify that ?! and if so, can you send me the dll, so i can check where the version info differs from the ones i test with?!

Hi Guys 'n' Girls. as mentioned before a few times, i really lack sparetime. but i still would like to bring support for editing syssetup.dll strings in WinntbbuED to you as fast as possible. So why dont you give me a hand in doing so ??? What i need are the resource Id's of the strings that are used while CDBOOT GUI Setup runs. The ones that look particular intesteing to me right now are: 54 (yeah, KMan you were right...) 1164 - 1170 1177 - 1180 If you know, or can figure out any more, this would help bringing the support for editing to life much faster, then if i had to research it all by myself. Come on, this doesnt seems a too hard task, does it ? All help welcome here TIA

Thank You! And added to the mirror List!

Glad you like it As i said before, all help of any kind is appreciated, no reason not to show it

Good question, i dont know either, but it was requested. And as i mentioned before i try to consider any request i get. Thats why i put up the poll to see if a majority would prefer a setup. Mhh.... That would be a pretty short section in help for now, as the name suggests in its current version it can edit: winntbbu.dll! Not more, not less.... But i get your point. Sadly i learned from past projects you usually can write as much info as you want, the questions still come, a lot of ppl are to lazy to read. The whole idea behind the Limitation menu item is to explain what goes and what not. On a ruff estemation i would guess 5% of the ppl using it read that. Just compare the downloads to the ppl taking actively part in the thread and you'll know... Enough Developer Crying Just one more good reason to appreciate the feedback and help i get. The Credits reflect that

Actually this is not a problem! It's just a not yet implemented feature. This was already on the ToDo List for the next version. So just wait a bit longer and this will be solved aswell...

I added both mirrors to the currently active post. Thanks again for setting them up!

quick answer: YES I'm now pretty happy with most of the winntbbu.dll stuff, so syssetup support has moved up to No. 1 on my ToDo list. Only for the moment i am a little short on sparetime, as it looks i wont be able to continue development before early next week. But then the focus will be on syssetup.dll support.

O.K. Guys 'n' Girls I'm a little short with my time, so before i start spending it on making an installer for my little app, i would like to know your opinion bout that.

Thnx 4 mirroring again! 10x Of Course! np. Hope you dont mind if i dont release an update just for that Next version will have it capatilized.

Nope, i dont mind at all! You are very welcome spreading the word

Taken from the 1st post in this thread: Cool! i always wanted to quote myself *lol* I'm Already doing so since the 9th of July, actually since piXelatedEmpire pointed this out the first time. But as it seems no one is reading the 1st post, so no one noticed yet And just to make sure i also added the current version link to my signature about an hour ago aswell. Hope this will make it easier to find the current release

Thats strange, can you expand that file, go to properties of the expanded .dll, version and post whats the internal name is set to ??? or simply post the .dl_ file ?

? Errors out ? What kind of error ? And yes, basicly thats what the Shell Extension menu does, though its a slightly different approach, i dont use (overwrite) the edit\command Regvalue, instead i add a "WinntbbuED" entry to the context menu, this is a bit more friendly for anyone who already has associated dll's edit\command to something else like e.g. a HexEditor But it's based on your suggestion, btw did you check the about lately?

Thnx! I'm pretty proud of that too B) Was quite some job to figure it out.... I'm using VB6 SP6

Thats an Easy one: You only need the \ infront of double quotes when you are having REG_SZ Keys as plain text in your reg file, the command string you set is a REG_EXPAND_SZ in hex form, where you dont need the backslash. Taken from your earlier post it should, to make it working, look like this: [HKEY_CLASSES_ROOT\...\shell\Edit\command] @=hex(2):25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,73,00,79,00,73,\ 00,74,00,65,00,6d,00,33,00,32,00,5c,00,57,00,69,00,6e,00,6e,00,74,00,62,00,\ 62,00,75,00,45,00,44,00,30,00,32,00,30,00,2e,00,65,00,78,00,65,00,20,00,22,\ 00,25,00,31,00,22,00,00,00 Note: this is just a correction of your earlier post, it would still point to %windir%\system32\WinntbbuED020.exe "%1" and i replaced the classname with "..." above, since its the same for dllfile and dl_file Hope you get the idea anyways. And you can also use the (Un)Register option in the editor itself if you like