Open lazna opened 3 years ago
adoxa
commented
3 years ago Not dead, but I've yet to muster up the energy to make the changes for the newer versions. Keep getting sidetracked with other projects. The lack of response on dostips was a little disheartening, too. I'll see if I can at least get it working with recent versions after I finish my current project. Don't be afraid to keep reminding me...
lazna
commented
3 years ago Thanks for reply. Could you tell me please: Why EB is fixed only for tested versions of cmd.exe, does it changing from version to version so much, that EB will not work on it without an adaptation? How someone could test it (and possibly make positive response for you) when he is unable to run it on actual windows? Should not be whole process vice versa, so people run it and report errors if cmd.exe updates broke something? But maybe I do not understand it at all :-/
adoxa
commented
3 years ago I have to disassemble CMD.EXE to determine how to patch it. Some features could work without patches (that's why there are two test files, one generic, the other for patches), but Carlos decided it should be all or nothing.
lazna
commented
3 years ago But it make this piece of SW practically unusable, correct me if I am wrong. When I decide to contribute, I dont expect this is will be just a geeks toy :-/
adoxa
commented
3 years ago It's an enhancement to batch, it's already a geek's toy. :) Only you know what you can contribute. If your intention is to support a new version of CMD.EXE you're going to need to know x86 assembly.
lazna
commented
3 years ago you're going to need to know x86 assembly
I can see this, but should not this fact be mented on head of EB web page? This C written code is publicly available and people may not aware of additional skills requirements. People should be informed this SW will stop working on every next windows update and there is a need of special skill to make it working again. Its not fair to conceal such important info
carlos-montiers
commented
3 years ago Hello @adoxa and @lazna
The lack of response on dostips was a little disheartening, too.
That was really unexpected for me. I think maybe in batch.xoo.it would have more comments. Anyways it was an early version.
I think this a cool geek project alive, a little bit paused. But it still have pending some design features. After it, the idea is only update the offsets, thus the maintain should be more easy.
Every time I got a Windows update, I check the cmd version and if is a new version I send it to Jason. Currentyl are pending to be supported: 10.0.19041.1 10.0.19041.546 10.0.19041.746
Some features could work without patches (that's why there are two test files, one generic, the other for patches), but Carlos decided it should be all or nothing.
I thought that maybe some auto update system can be useful. EB read the new offsets from some binary file, thus every time is outdated it ask the user to download the offsets file that is a good alternative in the sense the base dll will remain intact.
The pending features that I wanted to release the first version was:
$ prefix.In my free time I'm working mainly in my Sokoboxes project, that will have a game, current development here: https://sokoboxes.com/penguin-dev
But I not renounced to EB.
Not dead, but I've yet to muster up the energy to make the changes for the newer versions.
I think the same. My last development effort was to refactor the code a little bit to support heap context with khash. I still have pending do it.
Carlos
No adaptations for actual windows versions, people cant use this SW (without deep knowledge needed for self-adaptation). This state persist for many months. As I did not contributed with any code, but spent some time with arising this piece of code, so my question: Is EB a dead project? Are there any particular plans for future? Does it fully depend on Adoxa single person?