Recommended Posts

Can do but it'd depend on if they want grub installed or not, plus the type of grub (EFI vs BIOS) plus if it'd need to add windows or other OS's and whatnot :/

Could you not have those options underneath an "Advanced" tab?

Can do but it'd depend on if they want grub installed or not, plus the type of grub (EFI vs BIOS) plus if it'd need to add windows or other OS's and whatnot :/

could you not set it up to auto detect whether the computer uses EFI or BIOS?

could you not set it up to auto detect whether the computer uses EFI or BIOS?

I don't have a clue how to do that, not sure if there is an easy way to do that.

Adding another tab would really be ass-ache :p The other 2 tabs both currently look like this;

post-160466-0-54654400-1348435340.png

Maybe somewhere in the installer we could ask the question on installing default apps

such as

Browser

Mail

IM

and link this in with the installer so it only install the ones you choose?

is this becoming too advanced?

Eh? That's the idea but not what I mean.

How to display/edit the partitions on the GUI is what I mean, e.g a listview or a graphical pi chart or other chart or what?

Couldnt you do it like where it is a bar going across divided into sections for each partition with a more detailed list underneath?

On arch you do it all yourself via CLI using fdisk/gparted.

If you had a blank drive or spare space it's easy, but when it comes to resizing, it's kinda annoying and slighty more dangerous, plus if they've already got (MBR) 4 partitions or 3 and want to make 2 more, with 4 it's not possible to do and with 3 it'd need to be made as an extended partition, or they can have upto 64 with GPT! So it's gonna be a pain to do.

Plus I'm now at uni :p so time is limited.

Pretty basic thing I just knocked up using arial with PHP-GD and some false partition data.

(Or heck, we could get even more geeky and do it using gplot http://gplot.sourceforge.net/ or gnuplot http://www.gnuplot.info/ :?)

post-160466-0-18414200-1349038755.png

  • Like 2

On arch you do it all yourself via CLI using fdisk/gparted.

If you had a blank drive or spare space it's easy, but when it comes to resizing, it's kinda annoying and slighty more dangerous, plus if they've already got (MBR) 4 partitions or 3 and want to make 2 more, with 4 it's not possible to do and with 3 it'd need to be made as an extended partition, or they can have upto 64 with GPT! So it's gonna be a pain to do.

Plus I'm now at uni :p so time is limited.

cfdisk would be much easier, in my opinion.

Hey, everybody, just a quick little thing but I feel we should get it out of the way before we go any further - what license should we use?

IMO, the MS-PL is a pretty straight-forward license, but since we're using Arch, aren't we required to use Arch's license?

Whatever we make (script wise) is under whatever license we want it to be under, whatever license the OS is under depends upon what software is included with it, some packages are GPL, some are BSD, some are others, etc.

Also, I've not looked it up but does cfdisk support GPT? fdisk doesn't so it rules that out.

OK so I just quickly added the PHP-GD code to the installer code (after compiling php-gd twice!) and made it change the first image to see if it'd work. It did! So then I got it working via a GDKPixBuf using a GD image instead of having to save the file at all, so it's pretty nifty!

post-160466-0-37680800-1349213215.png

So I still can't find a way to work out if the system is booted via EFI or BIOS! I guess in theory we could make the EFI grub pass an extra kernel parameter maybe? Would need to compile it differently.

I found this but not sure how to tell if it's EFI or not ? http://smackerelofopinion.blogspot.co.uk/2009/10/dumping-acpi-tables-using-acpidump-and.html

So I still can't find a way to work out if the system is booted via EFI or BIOS! I guess in theory we could make the EFI grub pass an extra kernel parameter maybe? Would need to compile it differently.

I found this but not sure how to tell if it's EFI or not ? http://smackerelofop...pidump-and.html

You could always read the partition table of the block device. A EFI disk will consist of a legacy protective MBR, and the rest of the GUID table. The legacy MBR contains a single partition with a type of 0xEE. That can be used to determine if the block device is EFI or standard bios.

I wrote a little code to play around with reading partition tables of block devices, but I haven't worked out how to extract the correct disk geometry yet so the values are wrong, but it runs and parses the partition table. Specifically, it's a bit of a pain extracting sector and cylinder information from CHS. But I'll have a look at it again later.

disk.zip

This topic is now closed to further replies.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • 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.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • 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
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!