• 0

Neowin Toolbar?


Question

Recommended Posts

  • 0

Looking great you guys! This is coming along very nicely!

One issue. I am very up tight about the organization of my browser. I like to use the toolbar, but I only want it activated when I am using NeoWin.

When I leave the NeoWin site, I disable the toolbar. However, when I go back to reenable it later (after the browser has been closed and reopened), the toolbar always starts to the far right of my bottom toolbar row (instead of remembering it's previous position). Is there any way to force it to either remember it's previous position, or position itself in a new row by default?

All the hassel that I have to go through to unlock my toolbar, enable the toolbar, then reposition the toolbar before I can start using it... well makes it almost not worth the trouble. I am afraid that I will stop using the toolbar because of the inconvienance... which would really be too bad because it is quite useful. :)

Since I have never built a desk band object before, I have no idea if your application even has any control over it's positioning. It is possible that Internet Explorer wouldn't allow you to set the position.

  • 0

I've found the best layout that works for me is to get rid of a couple of the "junk" buttons(search, aim, icq, msn, etc) and keeping the neowin toolbar to it fits perfectly to the right of these buttons and to the edge of the screen, cutting off the "beta" at the end. Also you'd have to make sure you get rid of the text labels for it to fit right. Here is a link to a jpg of what my toolbar looks like if anyone's interested in checking out what I'm talking about.

  • 0

i dont know if it has been posted yet, but ever time i close IE I get an error says IE is causing problems and will be closed. This is after i either File->Close or the X, also tried Alt+F4. Happens both on my home machine and laptop.

XP

IE 6

Neowin Toolbar beta .51

/edit only happens the first time i open IE after I start up.

  • 0

Yeah I noticed it too lately, but more frequently than just the first time I run IE after boot up. I don't really mind it though, I'm sure it will be fixed eventually. I know a lot of the time it tells me the crash(after I close it anyway) is due to neowinband.dll, which I know is the file the toolbar uses.

  • 0

Unfortunately that is one of the major bugs we have yet to track down. I think it might have to do with the dynamic updating of the bar, but I could be wrong. I know I always had a problem with a Sysfader type error, and if I'm right this is similar to the error you all are encountering. I took a few days off of programming the bar because I just got a new 64MB vid card and was giving it a thorough hammering, but I will begin looking at it again tomorrow to try and track this bug down and finish the plugin api. If I'm lucky I'll be able to confine the bug to the exact area I believe it to be. If I track it down I'll PM Vader with a fix for you all, and until then I ask on behalf of Vader and myself to kindly endure this bug as we work on it. Thanks for reporting the errors, and if possible in the future, please PM me or Vader with a screenshot of the error, or place a screenshot of it here.

PiMPiN

  • 0

Hi all,

The bug that is being discribed is a problem I'm working on now. I ocurres when the toolbar can not get a windows handle to it self or if windows deletes the current one. The menu issue that hapens (See further up) is due to the Delphi implemtation or the windows menu structure so I've been recoding the thing over the last couple of days :) is hopefully it should be fixed on the next release.

I know this bug is a right pain in the rear but please bare with us as PiMPiN said hopefully it will be fixed soon.

Thanks,

Vader

  • 0

Here's a screenshot of an error I get about once or twice a day(happens either when I close it or click a link):

toolbar_error.jpg

The error that happens every time I close IE basically is just the regular error that says IE closed unexpectedly and has an option to restart it(checked by default :devious: ). I assume this is due to the toolbar since it started happening a lot after I installed one of the toolbar versions.

  • 0

I just installed Windows XP Pro last night and noticed another thing with the toolbar. It is a slightly different color then the rest of the toolbars, which I can't seem to fix by playing around with the Appearence -> Advanced settings. If I change the "3D Objects" color it changes the Neowin toolbar but not the others, so thats no good. Anyway, I'm still anxiously awaiting the next realease ;)

  • 0

Hi,

Sorry for any delay with the reply but I've been working away alot :)

1. The bar is takes it's colour from the 3d Objects as you found (I've added it to the list of 'Issues' :).

2. Hopefullt I've killed the bug where it crashes (Fingers crossed, as I've not had it crash in 2 days).

I should have a new version up tomorrow sometime which I'll need testing quite heavly, and it comes in a little different style ;) as I'm using a re-coded object and menus.

Cheers,

Vader

  • 0

Ok just uploaded a new version (0.63).

Neowin toolbar

So download and enjoy :)

Can anyone who downloads this either PM me or post a reply with comments (good and bad), ideas, bugs or basicly anything

Also now the toolbar is at the stage I starting to be happy with it it probably requires some icons for it, so any volentieers ;)

PimPin check your PM's for the source code

Cheero,

Vader

  • 0

I haven't tried this in a few weeks, and I like what I see. Although, I am not so sure the pink tinted buttons are appropiate for my Windows 2000 machine here at work, I am very pleased that the toolbar remembers its last position. :D

Don't get me wrong BTW... I really like the fancy XP style buttons. Do those buttons support OS color values? If so you could use the 3D Button color to color the background.

Unfortunately, I have two issue to report. BTW could you include a text file with the install in the future which includes a list of revisions and known issues? I kind of blew right past that screen during the install. There does not appear to be a copy in the program folder as I had hoped. So, I apologize if I am reporting something that anything which was already known. :o

ISSUE #1

When any interface object (such as a button) on the toolbar is selected, and I am for instance typing this reply in the web page, the standard Windows shortcut keys are not functional. I cannot use CTRL + C, CTRL + X, or CTRL + V to copy, cut, or paste my text.

The only way I have been able to get around this problem has been to either disable the NeoWin Toolbar (which only fixes the problem until I reenable it again) or close and reopen Intenret Exporer while being careful to not click any of the buttons on the NeoWin toolbar.

ISSUE #2

I have always installed the toolbar to "C:Program FilesNeowinToolbar". This install was no different. I even verified the Install path under HKEY_LOCAL_MACHINESoftwareNeowinToolbar also pointed to this location, and it does.

At the end of the installation I allowed the installer to open the Configuration dialog. After tweaking my forum list, I clicked the OK button to save the changes. Then an error dialog appeared which read "Unable to write to C:Program FilesNeowin ToolbarConfig.ini."

I have been able to manually work around the problem by creating the "Neowin Toolbar" folder, saving the changes, then copying the Config.ini file over to the "NeoWinToolbar" folder (where the Toolbar was installed to).

Perhaps this path be hard-coded in the options dialog?

  • 0

Hi BeeJay

The button colour should be a silver grey. Can you post a screen shot?

1. Not much I can do with this at the moment with out rewriting the IE deskbar interface :( The way to get around it is to press the tab key and they should then work :), however I will try to find a way around the problem.

2. Thanks I had left a reference to the standard dir in the program, which is now gone.

3. The position of the toolbar is not savable again it will need the same thing as no.1, This is from a MS employee that deals with the IE programming.

EDIT:

I may of found a way to stop the CTRL+ keys not working so if you can give the version I've just uploaded a go BeeJay. If this works for you I'll place the details in the change log - Thanks

/EDIT

So I've upoaded the new version with the above and a couple of other fixes

Cheerio,

Vader.

  • 0

I figured it would be easier to send you the screen shot directly... so check your hotmail account.

Hmm... perhaps it is just my monitor... but the buttons look like they have an ever so slightly pinkish tint to them. Although, upon further examination, it appears to be very similar to the light background color that is used through out the standard blue gray NeoWin interface. I will take a look at the screen shot at home to see if it still looks pink on that monitor.

It is not a horrid pink color. It just stands out a bit much from the current shade of gray I am using right now. This is just an aesthetic observation... this certainly won't stop me from using it though, so no need to worry about it. :)

Sweet! Your focus fix/hack works beautifully (even with any of the toolbar buttons appearing to have focus)! :)

  • 0
Originally posted by Vader

What is the error you get?

EDIT:

Ok I've just tried to replicate this error and can't, so anyone else with the problem??

Just so you know the installer writes a registry entry in HKLMSoftwareNeowinToolbar which contains the install dir and the toolbar then works from this.

Vader

sorry bout the slow reply. it tries to update the ini file on the c: drive even though i installed it on d:

  • 0

Problem..

When you type in a search.. you cant backspace.. atleast i am not able to.. :( and one more thing.. can u make it so that after the search it clears the field :ermm:

Thanks for the toolbar :)

  • 0
Originally posted by twist

damn you guys are quick!

Hehe... what an interesting coincidence. This just happend to get fixed today because I happened to download a new version to play with. :) Since I also happened to install it to a custom folder, I was able to reproduce this error. After providing Vader with a bug report, as well as my theory to the cause of the problem, the issue was (probably) quite easy to locate and correct. ;)

Vader deserves lots of praise for all of the work he has put into this project! Thanks again Vader! This is turning out quite nicely.

  • 0

Sweet... I like the new style a lot and it seems to be near perfect(the backspace thing is the only thing I noticed) so far. Hopefully the bug that made IE crash randomly or when you close it is fixed, haven't seen any post about it so that could be good. Oh yeah and that difference in color thing that bothered me using XP is fixed now too :) Great job guys, thanks again.

  • 0

Here's another idea that I haven't been able to perfect yet, chevons. If you're not sure what a chevron is, it's the little ? that appears when a toolbar is too long for the current window. Vader, I know it's possible with the toolbar toolkit, but I haven't found it yet.

PiMPiN

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!