Recommended Posts

I wanted to change the appearance of the window (Browser Preferences) that comes up on Alt, Tools, Options in Firefox to make it darker (and minimal).

This is what I came up with using Aurora on WinXP SP3.

I relied quite a bit on this style (http://userstyles.org/styles/42333/firefox-4-options-in-content-style-horizontal) as a starting point.

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);

* {text-shadow: none !important}

*[disabled = "true"] {color:#555!important; font-weight: bold!important}

tooltip { -moz-appearance: none !important; color: #666611 !important; background-color: black !important; font-size: 15px !important; border: 2px solid #666633 !important; -moz-border-radius: 3px !important}

menupopup, popup { background-color: grey !important; border: 3px solid #666611 !important; -moz-border-radius: 6px !important}

button, menulist 
{ -moz-appearance: none !important; background: -moz-linear-gradient(top, #454545, #252525)!important; border-radius: 3px !important; color: orange !important; font-weight: bold !important; border: 2px solid #777 !important}


@-moz-document url("chrome://browser/content/preferences/preferences.xul") {

#BrowserPreferences { background-color: #444 !important}

.paneSelector { border: 0 !important; background: transparent !important}

.paneDeckContainer { background-color: #444 !important}

#paneMain, #paneTabs, #paneContent, #paneApplications, #panePrivacy, #paneSecurity, #paneSync, #paneAdvanced {background: #444 !important}

groupbox { -moz-appearance: none !important; background: #555 !important; border: none !important; box-shadow: none !important}

.groupbox-body { -moz-appearance: none !important; background: #555 !important; border: none !important; box-shadow: none !important}

.caption-text, .text-link { color: maroon !important; font-weight: bold !important}

.caption-text { font-size: 120% !important; margin-bottom: 2em !important}

caption { -moz-appearance: none !important; background: none !important; margin-bottom: -2em !important}

.menulist-label-box { border: 1px solid transparent !important; background: #444 !important}

.menulist-label-box > .menulist-label { color: #888 !important; font-weight: bold !important}

menulist[open] .menulist-label-box > .menulist-label { color: pink !important}

.menulist-dropmarker { -moz-appearance: none !important; border: 0 !important; background: #777!important; padding: 0 !important}

menulist[open] .menulist-dropmarker { list-style-image: url(chrome://browser/skin/appmenu-dropmarker.png) !important}

/* Textboxes */
filefield { -moz-appearance: none !important; border: 0 !important; margin: 3px 4px !important}

filefield .fileFieldContentBox, textbox:not(.fileFieldLabel) { -moz-appearance: none !important; border-radius: 2px !important; border: 1px solid #222 !important; background-color: #555 !important}

/*Richlistbox/item */
richlistitem { max-height: 35px !important; min-height: 35px !important}
richlistitem .actionsMenu { -moz-margin-end:15px !important}
#handlersView .box-inherit.scrollbox-innerbox { padding-bottom: 2px !important}

/* Tabs */
#tabsElement tab { -moz-appearance: none !important; -moz-transition: none !important; background: #444 !important; color: #777 !important; font-weight: bold !important; border: none !important}

#tabsElement tab[selected="true"] { -moz-appearance: none !important; -moz-transition: none !important; color: orange!important; border: none !important; margin: 0 0 0 0 !important; border-bottom: 0 !important; padding: 0 7px 0 7px !important}

#tabsElement { -moz-appearance: none !important; border-bottom: 1px solid #444 !important; background: none !important; padding: 0 3px !important}

tabpanels { -moz-appearance: none !important; border: none !important; background: #444 !important}
.tabs-right { border: 0 !important}

/* SpinButtons*/
spinbuttons { -moz-appearance: spinner; cursor: default}

.spinbuttons-button { min-width: 13px; min-height: 11px; margin: 0 !important; border: none !important; background: none !important}

.spinbuttons-button > .button-box { border: 0}

.spinbuttons-up { list-style-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAkAAAAGCAIAAACepSOSAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAZ0lEQVR4nI2NIQ4EIQwAOVFDeEUtSPgCpp9F8xdIKvoDEnrFrNlLLqt25IwY596QUmqtxRifoZQy59x7jzFyzrcFACISETM755iZiBARADhEZGZV/f5QVWZGxI/3vtYaQvhfrLV67xcIJTc0rm8x5wAAAABJRU5ErkJggg==) !important}

.spinbuttons-down { list-style-image: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAkAAAAGCAIAAACepSOSAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAYklEQVR4nG3MMQrAIAxA0XQUvEN2cc0NzHW9gFdJxtxAMI1Lp9JS+tYP/0gpMXPOGV7mnGMMQEQRcffz5u4igogAAMxsZhGx944IM2utPRMiUtW1lqoSEXzUWnvvpZRv+HUBquQ2s8aPQ64AAAAASUVORK5CYII=) !important}

}

Hi, this is my current layout.

W5CGf.png

Would someone please help me with some issues I've been trying to fix (via stylish scripts)? I have pointed to the areas I want help with along with numbers corresponding to the list below.

1. How can I change inactive tab so that it's glassy and translucent like an old firefox 4 mockup here http://tungule.files...me-windows.jpg? I only want the translucent background though, not the round corners and other stuff.

2. I'm currently using this for my navigation ba

#navigator-toolbox[tabsontop=true] #nav-bar
{
padding-top: 4px !important;
padding-bottom: 4px !important;
background: -moz-linear-gradient(top, rgba(242,246,251,1), rgba(255,255,255,.0)) !important;
}

I like that there's some transparency in the navbar. However, this does not match the current tab and there's a noticeble line dividing the different colors/transperencies. How can I change the active tab so that it'll have the same look as my navbar?

3. There's quite some space between the tabgroup button and the minimize button. This is even more noticeable when you maximize the window. How can I get rid of some of the blank space?

4. I removed the dropdown in the URL bar using this code.

#appmenuSecondaryPane { box-shadow: none !important; }

.autocomplete-history-dropmarker.urlbar-history-dropmarker{ display:none !important;}

#star-button { -moz-box-ordinal-group: 2 !important; }

Now, the bookmark star is too close to the refresh button. How can I create some blank space?

5. How can I change this corner to be sharp? (i.e. rectangular corner instead of rounded corner) Same for the corresponding corner for the right side...

6. The window frame is significantly thicker for Firefox than for other windows applications like notepad etc. Is it possible to reduce the thickness of the window frame to be like other windows applications?

7. Also, I found a way to remove the tab close button on inactive tabs unless you hover on them. I can't seem to find it anymore...

I'm sorry if some of these have been addressed. I already tried searching this thread but perhaps it's hard for me to think of good search queries. Any help will be very appreciated! Thanks in advance!

Also, sorry for duplicate post in the other thread (which is mainly for showing browser layout not for discussing stylish scripts). I posted in the wrong one by accident and can't delete it anymore.. Hopefully a mod will kindly delete it for me.

Thanks trag3dy.

I've actually fixed the tab background gradients to fit what I want though so I don't think I'll need stratiform for the tab transparency stuff anymore?

So now I have 3-7 left that I want to fix. Any help will be greatly appreciated!

Thanks trag3dy.

I've actually fixed the tab background gradients to fit what I want though so I don't think I'll need stratiform for the tab transparency stuff anymore?

So now I have 3-7 left that I want to fix. Any help will be greatly appreciated!

4.

#star-button { -moz-box-ordinal-group: 2 !important; margin-right: 2px !important;}

5.

#nav-bar {border-radius: 0 !important}

7. This will hide the close button on inactive tabs until you hover the tab, not sure if that's what you were wanting:

.tabbrowser-tab:not([selected="true"]) .tab-close-button {
visibility: hidden !important;}

.tabbrowser-tab:not([selected="true"]):hover .tab-close-button {
visibility: visible !important;}

Wow thank! Those work great!

The tab close button does not appear even on hover when you have a lot of tabs open because that's how Firefox operates by default. I guess it's not possible to make it appear on hover because the UI element is probably not even there?

I found out how to remove some space between the tab groups button and the minimized button when the window is not maximized by editting the -moz-padding-end as below.

#main-window[sizemode=normal] #navigator-toolbox[tabsontop] > #toolbar-menubar[autohide] ~ #TabsToolbar {
-moz-padding-start:0px!important;
-moz-padding-end:103px!important;
}

But I can't do it when it's maximized. Does anyone know how?

Wow thank! Those work great!

The tab close button does not appear even on hover when you have a lot of tabs open because that's how Firefox operates by default. I guess it's not possible to make it appear on hover because the UI element is probably not even there?

ok, try this instead:

.tabbrowser-tab:not([selected="true"]) .tab-close-button {
visibility: hidden !important;}

.tabbrowser-tab:not([selected="true"]):hover .tab-close-button {
visibility: visible !important;
display: -moz-box !important;}

and for the tab groups button try this:

#TabsToolbar > .titlebar-placeholder:last-child { 
    margin-left: 8px !important; 
}

Distancestabbarffstuff.png

How can I get the gap between the FF button and my first tab to be the same as the distances on the FF button's other 2 edges?

Edit: That tiny gap above the tabs bothers me as well. I kinda want it either gone, or being the same distance as the other gaps.

Are we only able to edit a post a limited number of times? I don't see the edit button on my last post anymore.

Anyway, does anyone know of a way to make it so when you use an image in the progress bar of status-4-evar, it stretches the image instead of tiling it?

Thank you so much foxxyn8!! Those work great!

I have only two tiny details left now.

nITW8.png

This is when it's maximized. How can I get rid of the space on the left? Also, can I get rid of the 1 pixel above the tabs as well?

CLGPj.png

The borders of the tab and the navbar seem inconsistent. How do I make them consistent, especially that one pixel between the tab and the navbar that's much darker than the rest? I have not done anything to any of the borders. Relevant codes would include:

.tabbrowser-tab[selected] {
background-image: -moz-linear-gradient(rgba(242,246,251,.5), rgba(231,237,246,1)) !important;
}

.tabbrowser-tab:not([selected]){
background-image: -moz-linear-gradient(rgba(242,246,251,.1), rgba(231,237,246,.2)) !important;
}

.tabbrowser-tab:not([selected]):hover{
background-image: -moz-linear-gradient(rgba(242,246,251,.4), rgba(231,237,246,.55)) !important;
}

.tabs-newtab-button {
background-image: -moz-linear-gradient(rgba(242,246,251,.1), rgba(231,237,246,.2)) !important;
}

.tabs-newtab-button:hover{
background-image: -moz-linear-gradient(rgba(242,246,251,.4), rgba(231,237,246,.55)) !important;
}

and

#navigator-toolbox[tabsontop=true] #nav-bar
{
padding-top: 4px !important;
padding-bottom: 4px !important;
background: -moz-linear-gradient(top,rgba(231,237,246,1), rgba(255,255,255,.6)) !important;
border-radius: 0 !important;
}

Oh, also, can I make the tab close button actually gone altogether instead of just hidden? The difference would be that the name of the webpage can extend and occupy where the tab close button was, instead of having a blank space there.

Thank you so much in advance. I really appreciate your kind help!

Sorry for double post. This editing time limit thing is really unnecessary I think...

I've managed to fix some of the things I asked on my own. :)

Removing the 1 pixel padding above tabs when maximized:

#main-window[sizemode="maximized"] #titlebar  {
  margin-bottom: -23px !important;
}

Make the tab title actually occupying the old space of where the tab close button was:

.tabbrowser-tab:not([selected="true"]) .tab-close-button {
display: none !important;
}

The difference is that I used "display: none" instead of "visibility: hidden"

I'm still looking for ways to remove the left padding of tabs when maximized and to fix the tab border not being consistent with the navbar border. Any help would be gladly appreciated. Thanks!

Any idea how to darken the page that we get when we click on a cache item?

url(about:cache) catches what we get when we type about:cache

url(about:cache?device=disk) works for the next part.

But I don't know how to get the page that will show individual cache items to work. For example, about:cache-entry?client=HTTP&sb=1&key=https://www.neowin.net/forum/public/style_extra/post_icons/icon6.gif

This is what I have for now:

@-moz-document 
url(about:about), 
url(about:blank), 
url(about:), 
url(about:cache), 
url(about:cache?device=disk), 
url-prefix(about:neterror), 
url-prefix(about:neterror?e=netTimeout), 
url-prefix(about:certerror) 
{ 
  html 
         { background-color: black !important;
         } 
}

Any chance of getting the firefox 4.0 buttons back in the latest nightlys? They reduced the drop shadows and rounded corners :(

I've been digging through the firefox 4.0 code but couldn't quite figure it out without messing up everything.

5643609595_ba1c6e5041_o.png

I really hope someone can help me out here. Thanks in advance :)

Any idea how to darken the page that we get when we click on a cache item?

url(about:cache) catches what we get when we type about:cache

url(about:cache?device=disk) works for the next part.

But I don't know how to get the page that will show individual cache items to work. For example, about:cache-entry?client=HTTP&sb=1&key=https://www.neowin.net/forum/public/style_extra/post_icons/icon6.gif

url-prefix(about:cache) isn't working for that purpose?

url-prefix(about:cache) isn't working for that purpose?

Not only does it work :) , but I then don't need the other two entries. This url-prefix trick is quite neat. Staring at the DOM Inspector screen for ages didn't help!

In edit:

I guess that both these aren't needed either:

url-prefix(about:neterror)

url-prefix(about:neterror?e=netTimeout)

Just the first should do. Let's see. I commented out the second for now.

How can I align the tab bar with the address bar both maximized and minimized? I'm sure it's already been posted, but I can't find it.

unled1uqs.png

Normal Window:

#main-window[sizemode=normal] #navigator-toolbox[tabsontop] > #toolbar-menubar[autohide] ~ #TabsToolbar {
-moz-padding-start:0px!important;
}

Maximized Window:

#TabsToolbar > .titlebar-placeholder { 
    margin-left: 0px !important; 
}

Hope that helps.

Normal Window:

#main-window[sizemode=normal] #navigator-toolbox[tabsontop] > #toolbar-menubar[autohide] ~ #TabsToolbar {
-moz-padding-start:0px!important;
}

Maximized Window:

#TabsToolbar > .titlebar-placeholder { 
    margin-left: 0px !important; 
}

Hope that helps.

Thanks. The normal window worked, but I'm still 1 pixel off on the maximized. I tried adjusting the number in the script and nothing happened no matter what number I put.

unled1zc.png

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

    • No registered users viewing this page.
  • Posts

    • AMD RX 9070 GRE AI, Blender benchmarks vs 9070 XT, 7800XT, Nvidia RTX 5070, 4070 by Sayan Sen Earlier this week, we shared the first part of our review of AMD's new RX 9070 GRE. It was about the gaming performance of the GPU, and we gave it an 8 out of 10. As a follow-up, similar to how we did with the 9070 XT and non-XT, we are doing a dedicated productivity review for the RX 9070 GRE as well, where we compare it against the 9070 XT, 9070, 7800 XT, as well as Nvidia's 5070 and 4070. This will include AI, rendering, compute, and more benchmarks. AI performance, especially, is a very important metric in today's world, and AMD also promised big improvements thanks to its underlying architectural improvements. We will be pitching it against the data we already have for the RX 9070, and RX 9070 XT, but also the Nvidia 5070 FE, MSI GeForce RTX 4070 VENTUS 2X 12G, and Gigabyte Radeon RX 7800 XT GAMING OC 16G as they are in a similar price class, but also because we do not have a comparable 5060 Ti card lying around here that we can compare it against. Before we get underway, this is a collaboration between Sayan Sen and Steven Parker, who lent me his test bed. Also, there was no editorial input from AMD. First up, the specs of the RX 9070, 9070 XT, and 9070 GRE, which were given to us by AMD: Radeon RX 9070 GRE Radeon RX 9070 Radeon RX 9070 XT Boost Clock: Game Clock: up to 2.79GHz up to 2.20GHz up to 2.52GHz up to 2.07GHz up to 2.97GHz up to 2.40GHz Stream Processors 3,072 (48 CU) 3,584 (56 CU) 4,096 (64 CU) Ray Accelerator 48 56 64 AI Accelerator 96 112 128 ROPs 96 128 Texture Mapping Units 192 224 256 Memory 12 GB GDDR6, 18Gbps Clock, 192-bit Bus 432 GB/s 16 GB GDDR6, 20Gbps Clock, 256-bit Bus Effective Memory Bandwidth: 640 GB/s Infinity Cache 48 MB (3rd Gen) 64 MB (3rd Gen) Card Bus PCI-E 5.0 X16 Output 2x HDMI 2.1b 2x DisplayPort 2.1a Power consumption 220W 304W Recommended PSU 650W 750W Slot width 2x 3x Price (SEP) $549 $599 As you can see from the specs above, it is less than the standard RX 9070 in every way that counts, except for slightly higher Boost and Game clock speed. Design Moving on, the RX 9070 GRE we were given is an XFX Swift triple-fan, dual-slot design with two 8-pin connectors. At 30cm (self-measured), it will fit in most systems easily. There is no RGB either. The AMD Radeon RX 9070 GRE by XFX from all angles. Test system Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS Z890 ProArt Creator WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 25H2 (Build 26200.8246) AMD shared a press driver based on the recently released Adrenaline 26.5.2 that we were required to use. We now move on to our benchmarks. First up, we have Geekbench AI running on ONNX. For some reason, the 9070 GRE does exceptionally well here in both half-precision (FP16) and single-precision (FP32). It manages to beat the RTX 5070 and RX 9070 non-XT, and is only behind the 9070 XT. Since Geekbench runs in short bursts instead of continuously hammering the graphics card, it seems the GRE's faster boost clocks are helping here. Next up, we move to the UL Procyon AI test suite, starting with the image generation benchmark. We chose the Stable Diffusion XL FP16 test since it is the most intense workload available on Procyon. The Nvidia cards do very well here, as even the 4070 out-muscles AMD's best fairy easily. The positive thing about the GRE is that it gets quite close to the 9070 non-XT in this test; this indicates that the VRAM does not play a very big role here, as SD XL relies on float16 (FP16). So this is something to keep in mind again. If you wish to work with float32 AI workloads, graphics cards with larger than 12 GB buffers would likely emerge as victors. Regardless, the gains are still massive on AMD's 9000 series compared to the 7000 series. Following image generation, we move to the text generation benchmark. This is one test where the 9070 GRE struggled, quite a lot. It seems that the 12 GB VRAM and lower memory bandwidth of the new Radeon 9070 GRE are hurting it quite a bit; the split is massive, especially in a test like Llama2, which packs 13 billion parameters. As such, in all the tests, the 9070 GRE is the slowest of the lot. Next, we tried Blender, and here the AMD GPUs were beaten by Nvidia. Rendering is something the Green team has always had a lead over the Red side, and it has not changed so far. On the positive side, though, the 9070 GRE shows significantly better results than the 7800 XT, which means AMD is on the right path. Catching up to Nvidia, though, will require a lot more effort. And we hope HIP and ROCm can keep improving. Wrapping up AI testing, we measured OpenCL throughput in the Geekbench compute benchmark. The RX 9070 GRE alongside the 9070 did not fare well here at all, even falling behind the 7800 XT. Interestingly, even the RTX 5070 could not beat the 4070 on OpenCL, so perhaps this suggests that OpenCL optimization may not have been a priority for either AMD or Nvidia in the modern era. Conclusion We reached the end of our productivity performance review of the 9070 GRE, and we have to say it's a mixed bag. Unlike the 9070 and 9070 XT, the GRE excels in some areas while losing ground fairly easily in others. Similar to how it happened in gaming, any time the card's memory subsystem gets hammered, it tends to fall behind the others. This was the case with text generation, wherein we saw the VRAM sometimes hit its maximum available 12 GB of usage with larger model sizes. So what do we make of the RX 9070 as a productivity hardware? It can certainly be used, but you have to know it has its limitations. For those looking for a GPU that can deal with more, AMD recently unveiled the Radeon AI PRO R9700, which is essentially a 32 GB refresh of the 9070 XT with some additional workstation-based optimizations. On a similar note, the new Ryzen AI Halo platform is something you can consider if you want to set up a local AI processing station. Considering everything, we rate AMD's Radeon RX 9070 GRE a 7.5 out of 10 for its productivity performance. Price is less of a factor for those looking at productivity cases compared to those considering the GPU for gaming, and as such, we felt it did quite decently on many occasions and can be handy if you need a 12 GB GPU and, for some reason, don't want to get Nvidia. Purchase links: RX 9070 / XT / GRE (Amazon US) As an Amazon Associate, we earn from qualifying purchases.
    • Does anyone here know if these updates are integrated into the UUP dump isos?
    • Motrix Next 3.9.4 by Razvan Serea Motrix Next is a modern, open-source cross-platform download manager built as the official next-generation successor to the original Motrix project. It has been completely rewritten using Tauri 2, Vue 3, TypeScript, and Rust, while still relying on the powerful Aria2 download engine for high-speed multi-protocol transfers. The app supports HTTP, HTTPS, FTP, BitTorrent, ED2K and magnet links, offering advanced features like multi-connection acceleration, task scheduling, bandwidth control, and batch download management. With a significantly reduced install size (around 20MB), it focuses on being lightweight, fast, and resource-efficient compared to traditional Electron-based download tools. Designed for Windows, macOS, and Linux, Motrix Next delivers a clean, modern UI inspired by Material Design 3 principles, with smooth animations and a minimal workflow. It improves usability through better download organization, system tray integration, and enhanced torrent handling including selective file downloads and tracker management. Motrix Next features: Multi-protocol downloads — HTTP, FTP, BitTorrent, Magnet, .torrent, ED2K, and Metalink tasks BitTorrent — Selective file download, DHT, peer exchange, encryption controls, metadata caching, GeoIP peer flags, and tracker probing Browser extension integration — Embedded Extension API with independent authentication, download confirmation, smart auto-submit, filename hints, referer/cookie forwarding, and real-time controls (Chrome Web Store · Edge Add-ons) Safe filename handling — Content-Disposition, RFC 2047, non-UTF-8, percent-encoded, and extensionless URL resolution with path traversal sanitization Download organization — Favorite and recent folders, optional file-type categorization, stale-record cleanup, and completed history backed by SQLite Concurrent downloads — Independent controls for active tasks, HTTP connections per server, segments per file, and BT peer limits Speed control — Global and per-task upload/download limits with day-of-week and time-of-day scheduling System integration — Tray operation, optional tray speed display, macOS Dock badge/progress, protocol handlers for magnet://, thunder://, and motrixnext:// Lightweight mode — Destroys the WebView on minimize-to-tray while Rust keeps the engine, task monitor, notifications, history, and extension routing alive Notifications and power options — Native task start/complete/failure notifications, keep-awake during downloads, and optional shutdown after completion Network controls — Scoped proxy support for downloads, app updates, and tracker updates, plus system proxy detection Auto-update channels — Stable, Beta, and Latest Across Channels policies with separate download and install phases Diagnostics — Structured logs, exportable diagnostic ZIPs, database integrity checks, automatic DB rebuild, and Linux GPU rendering fallback Personalization — Light/dark/system theme, 10 color schemes, 26 languages, and first-launch system language detection Motrix Next 3.9.4 changelog: Motrix Next 3.9.4 promotes the 3.9.4 beta cycle to stable. This release refreshes bundled engine binaries, improves task detail readability and copy actions, expands link handling for magnet and ED2K workflows, polishes responsive navigation and text wrapping, updates browser extension documentation, and refines network preference controls. New Features Task Detail copy actions — Added copyable values for task metadata and reusable render functions for long text fields. Magnet and ED2K lifecycle support — Added task lifecycle handling for magnet and ED2K links. History cleanup for deleted tasks — Deleted tasks can now remove matching history records. User-Agent management — Added user-agent management and improved related network preference controls. Browser extension documentation — Added the Firefox Add-ons link for the Motrix Next extension. Improvements Engine binaries — Updated bundled binaries for supported architectures. Task Detail readability — Long task names, URLs, tracker values, and copyable metadata now render more clearly. Deletion messaging — Refined localized task deletion text for clarity and consistency. Text wrapping — Improved URI input wrapping and task name multiline display. Navigation layout — Improved sub-navigation responsiveness. Disk allocation default — Changed the default file allocation method to trunc. Proxy controls — Improved proxy button styling in network preferences. Download: Motrix Next 64-bit | ARM64 | macOS ~20.0 MB (Open Source) Links: Website | macOS / Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • NVIDIA officially supports Ubuntu, as linked above with the GeForce NOW Hands on I did in collaboration with Paul Hill.
    • TO be clear I am not running linux today, however I keep thinking about it. And I want to make sure there are minimal obstacles if I decide to make that switch in the coming months.
  • Recent Achievements

    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
    • Dedicated
      Mark Spruce earned a badge
      Dedicated
    • Collaborator
      conkir earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      479
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Steven P.
      72
    4. 4
      FloatingFatMan
      66
    5. 5
      +Edouard
      66
  • Tell a friend

    Love Neowin? Tell a friend!