Jump to content


Photo

Shout out


  • Please log in to reply
2 replies to this topic

#1 parity_bit

parity_bit

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 04 February 2021 - 02:29 AM

Hello, 
new here, 
just a note to say, I appreciate this existing.  
 
I used to use alternative shells back with Windows 95, and I am glad to see the movement is still around.  
 
Keep doing what ya do!
 
(Right now I use cmd.com as a winlogon shell with doskey to function as a menu, but would like the option of a higher level UI other than taskmgr should the occasion warrant.)


  • pitkon, Paz and xoblite like this

#2 pitkon

pitkon

    Administrator

  • Head Administrator
  • 1,329 posts
  • LocationAthens & Nafplio, Greece

Posted 14 February 2021 - 05:49 AM

Hello to you too and welcome!

Thanks for your kind words, it's people like you that keep this site and the alternative shell community alive.S

So, thank you too!


  • parity_bit likes this

#3 parity_bit

parity_bit

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 14 February 2021 - 08:42 PM

Hello to you too and welcome!

Thanks for your kind words, it's people like you that keep this site and the alternative shell community alive.S

So, thank you too!

It's so liberating to be able to use MS.Win like linux, that is, scaling back or forward?(up) as necessary.  This is the real drawback of Explorer as a shell.  It's sooo bloated, they felt the 'need' to cram everything "under the hood".  

Want a web browers?  We're M$Soft, we have that!  We'll call it, IE (irrecoverable error) and when that is clearly proprietary and obsolete we'll call it Edge, because if you're not careful, it'll cut you!  lol kidding a little.

 

I had a question, might as well ask it here:

I'm on a computer that is in sore need of some ddr3 DIMMs and so it's only got 1 gig of room to work in.  I was wondering if anyone has done a memory workup of the footprint of blackbox front-ends?  

With experience, I've learned that Explorer is too taxing on that lean memory diet, but taskmgr works well, and cmd far better.  

What I notice is that taskmgr will run a task and the module (libreoffice, anything else) will not just have own memory space allocated, but will also increase footprint of calling program (taskmgr).  This problem seems to go away with cmd, and it seems (could be wrong) that every process merely gets its own heap-space?  After comparing bblean to Explorer, it does far better.  I think it also is better than taskmgr because as well as it works, it still has so many tentacles back into the OS proper.  bblean seems to avoid this by nullifying some of the calls to the OS and implementing better alternatives.  (maybe I'll write an FAQ or youtube commercial, lol)  

 

Anyone have any experience in this area, could tell me if my observations are indeed correct?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users