Windows 7 32-bit with full 4 GB or 8 GB RAM support


Recommended Posts

Which you don't know at all. Personally I think running patches like this is stupid, but I wouldn't be so quick to insist that it doesn't work. From a theoretical aspect, it can certainly work.

There is no such thing as a "PAE-aware" application. The 2GB limitation always applies, even on 32-bit versions of Windows that support more than 4GB (the server line.) The only way around this is for applications to do their own memory management by mapping chunks of memory in and out of their address space, but this is fairly rare. A few server programs did it years and years ago, but nothing else does.

Why doesn't it work? What are you basing this claim on? You do know that Microsoft sells a whole range of 32-bit operating systems that support up to 128GB of memory, right? It's called their server products. As you probably know, the server and client edition is virtually identical (to the point where binaries literally are identical for Vista and 2008). With this in mind, I don't know why you believe it is completely impossible to patch the part of the kernel and loader that decides how much memory you get to use. It doesn't have to be more than a few bytes to change.

"Theoreticaly" isn't real world. It doesn't work. Do some research.

Quit with the FUD please. 32 bit is 32 bit not 36.

"Quit with the fear, uncertainty and doubt?" What on earth does that sentence even mean?

Just because the CPU architecture is 32-bit, does not mean that the addressing has to be. Modern systems support >36-bit addressing, and this is implemented with three-level translation. It's a completely standard thing, supported by all platforms from Windows Server to OS X to Linux to FreeBSD to most other platforms still in development.

Why doesn't it work? What are you basing this claim on? You do know that Microsoft sells a whole range of 32-bit operating systems that support up to 128GB of memory, right? It's called their server products. As you probably know, the server and client edition is virtually identical (to the point where binaries literally are identical for Vista and 2008). With this in mind, I don't know why you believe it is completely impossible to patch the part of the kernel and loader that decides how much memory you get to use. It doesn't have to be more than a few bytes to change.

Is it that hard to read what I said before you respond?... This is not about server products or any of that. If the server products can already address more memory, then it would not need this.

For the second or third time, this is for the mainstream 32-bit system that you piece together from Newegg or whatever. NOT SERVER HARDWARE.

For this casual user with a 32-bit system, this will not work because the hardware and software will not allow it. That's it, no excuses. If you honest think it will work, go try it yourself and report back to us...

Seriously. Get a clue. It won't work. Do some research.

No, you get a clue. What I said was absolutely correct. I suggest that you contact Microsoft and Apple immediately and inform them that their products that support PAE do in fact not work. I'm sure they would be surprised to find out. You get right on that.

Is it that hard to read what I said before you respond?... This is not about server products or any of that. If the server products can already address more memory, then it would not need this.

For the second or third time, this is for the mainstream 32-bit system that you piece together from Newegg or whatever. NOT SERVER HARDWARE.

For this casual user with a 32-bit system, this will not work because the hardware and software will not allow it. That's it, no excuses. If you honest think it will work, go try it yourself and report back to us...

You are absolutely wrong. It is supported by most current consumer hardware. The server versions of Windows support it because they are licensed to use more than 4GB and because they do not have an artificial limit imposed for driver compatibility (which the client edition does.) The logic is that people who run the server edition are able to pick components that they know support it, so that the compatibility issue doesn't matter as much.

Now, whether this particular patch works, I do not know, but it is a simple fact that everything needed to support it is already present in Windows, but is just disabled in the client edition (which is mostly identical to the server edition, with different settings.) This means that it could certainly be possible to do it from a technical aspect. The people here who are claiming it doesn't work or can't be done, are not basing this claim on any facts.

Seriously. You need to do your homework. It's not gonna happen no matter what you wish in this world. You're wrong, let it go.

You need to state what I am wrong about. I have said several things, so please be specific. Am I wrong about it being possible to go beyond 32-bit addressing on 32-bit systems with PAE? Am I wrong about the fact that Microsoft sells 32-bit versions of Windows that support up to 128GB? Am I wrong about the server and client line being virtually identical? What am I wrong about? Be specific.

I am now tired of you. PAE was never an issue. I believe you brought it into the discussion. As far as the server/client issue. Do you not think that a company would even have a server/client if there wasn't an advantage and a purpose to either? Go away.

im amazed at people still wanting to use 4+ gigs of memory on a 32bit system, 32bit is on its way out so why use something that will not use all your memory, and not use something that will make a better overall computer system. I hope Windows 8 is the last of 32bit software and they move to 64bit windows with windows9. I have heard that the current windows server is the last of 32bit and the next will be only 64bit. It seems like people have had mixed results with PAE and that its not worth having it... in the end i think people should try both and see how the feel!

You need to state what I am wrong about. I have said several things, so please be specific. Am I wrong about it being possible to go beyond 32-bit addressing on 32-bit systems with PAE? Am I wrong about the fact that Microsoft sells 32-bit versions of Windows that support up to 128GB? Am I wrong about the server and client line being virtually identical? What am I wrong about? Be specific.

hdood, stop living under a rock and upgrade to x64.

And to everyone else, Windows does support 36bit addressing via PAE, but, it's a hardware problem with drivers etc. Server based products can be tailored to support it since it's a server environment, but for standard consumer hardware like Graphics cards etc, they need to be designed and have drivers to fully support it or you'll have system crashes and so on. This "hack" will only cause system instability which can be avoided by either just staying with 32bit version of Windows or upgrading to x64.

All this crap needs to stop, retail versions of Windows Vista/7 (I think some OEM copies) can go from 32bit to 64bit without any additional cost since the CD keys will work with both products.

x64 is no just about more memory, it's the extra CPU registerers etc that are good for speed increases for applications that support/take advantage of x64 based hardware. And if I hear someone say "Well, 32bit is 'emulated' in x64 version of Windows", please stfu, really, the performance differences for this type of 'emulation' is near to nothing.

  • Like 1
You are absolutely wrong. It is supported by most current consumer hardware. The server versions of Windows support it because they are licensed to use more than 4GB and because they do not have an artificial limit imposed for driver compatibility (which the client edition does.) The logic is that people who run the server edition are able to pick components that they know support it, so that the compatibility issue doesn't matter as much.

Now, whether this particular patch works, I do not know, but it is a simple fact that everything needed to support it is already present in Windows, but is just disabled in the client edition (which is mostly identical to the server edition, with different settings.) This means that it could certainly be possible to do it from a technical aspect. The people here who are claiming it doesn't work or can't be done, are not basing this claim on any facts.

Seriously, can you please stop going on about server hardware/software? For the fourth time, this is NOT about that.

If you want to convince us that this works, please go try it. I mean no disrespect, but you won't convince us with anything until you give us physical proof that it will work.

hdood, stop living under a rock and upgrade to x64.

And to everyone else, Windows does support 36bit addressing via PAE, but, it's a hardware problem with drivers etc. Server based products can be tailored to support it since it's a server environment, but for standard consumer hardware like Graphics cards etc, they need to be designed and have drivers to fully support it or you'll have system crashes and so on. This "hack" will only cause system instability which can be avoided by either just staying with 32bit version of Windows or upgrading to x64.

All this crap needs to stop, retail versions of Windows Vista/7 (I think some OEM copies) can go from 32bit to 64bit without any additional cost since the CD keys will work with both products.

x64 is no just about more memory, it's the extra CPU registerers etc that are good for speed increases for applications that support/take advantage of x64 based hardware. And if I hear someone say "Well, 32bit is 'emulated' in x64 version of Windows", please stfu, really, the performance differences for this type of 'emulation' is near to nothing.

Not emulated. Virtualized. ;)

Seriously. You need to do your homework. It's not gonna happen no matter what you wish in this world. You're wrong, let it go. Supported HARDWARE WISE- not SOFTWARE unless you have the correct OS.

What is likely happening with this patch is that they are modifying the kernel to act like the kernel from the server lines of Windows, which support more than 4GB on 32-bit. There is your OS support right there. Now what exactly are you saying won't work?

im amazed at people still wanting to use 4+ gigs of memory on a 32bit system, 32bit is on its way out so why use something that will not use all your memory, and not use something that will make a better overall computer system. I hope Windows 8 is the last of 32bit software and they move to 64bit windows with windows9. I have heard that the current windows server is the last of 32bit and the next will be only 64bit. It seems like people have had mixed results with PAE and that its not worth having it... in the end i think people should try both and see how the feel!

Most probably would LIKE to go to 64 bit, BUT 32 bit ONLY CPU's still do exist. And obviously 64 bit wont install if the CPU is only 32 bit. And the only way they'll be able to get out of 32 bit, is if they update everything. So, it'll support it

I am now tired of you. PAE was never an issue. I believe you brought it into the discussion. As far as the server/client issue. Do you not think that a company would even have a server/client if there wasn't an advantage and a purpose to either? Go away.

Please answer my question. PAE was never an issue? What do you mean? PAE is the feature that lets you use >32-bit addressing on 32-bit platforms (something you claimed wasn't possible).

Again, tell me what was wrong?

Was it that it is it possible to go beyond 32-bit addressing on 32-bit systems with PAE?

Was it that Microsoft sells 32-bit versions of Windows that support up to 128GB?

Was it that the server and client line is virtually identical?

Since you know for a fact that this patch can't work, could you take a few minutes to explain to us how the memory initialization during startup works in Windows, and how it differs between Vista and Server 2008? How do you know that the difference is any more substantial than simply setting a flag? It's not unreasonable to suspect this, so how do you know otherwise? I trust that you can enlighten us, since you clearly know the facts here.

Most probably would LIKE to go to 64 bit, BUT 32 bit ONLY CPU's still do exist. And obviously 64 bit wont install if the CPU is only 32 bit. And the only way they'll be able to get out of 32 bit, is if they update everything. So, it'll support it

Well, technically they do, but they're no longer made except for certain mobile processors. I doubt there's any great number of people out there with old 32-bit Pentiums or Athlons and >4GB of memory they're dying to get to work. When this topic comes up, it's almost exclusively people with fairly high-end modern hardware.

What is likely happening with this patch is that they are modifying the kernel to act like the kernel from the server lines of Windows, which support more than 4GB on 32-bit. There is your OS support right there. Now what exactly are you saying won't work?

What "patch"? The kernel is what it is. You can't alter 32 bit code to do what 64 bit code does. Go away with the FUD.

Seriously, can you please stop going on about server hardware/software? For the fourth time, this is NOT about that.

As I (and others) have stated, this patch is most likely making a hybrid kernel that has the memory support from the server software patched into the kernel for the client OS. That is why people keep mentioning the fact that the server version support it. You and ShamRocker1 are the ones who keep claiming that it simply isn't possible at all without stating any facts to back up your claims.

http://www.geoffchappell.com/viewer.htm?do...ense/memory.htm

Read please.

That 32-bit editions of Windows Vista are limited to 4GB is not because of any technical constraint on 32-bit operating systems. The 32-bit editions of Windows Vista all contain code for using physical memory above 4GB. Microsoft just doesn’t license you to use that code.

ps. Please don't whinge that its about Vista, the same applies to 7

What "patch"? The kernel is what it is. You can't alter 32 bit code to do what 64 bit code does. Go away with the FUD.

I don't think you understand. The ability to use 36-bit addressing is already present in 32-bit Windows. It's solid, fully tested implementation that has been around for ages. If you want some examples of what the various 32-bit versions of Windows Server can support, you can click here.

The server and client version of Windows aren't two separate operating systems. They're the same OS, built from the same code, but with different settings. They even share many binaries (this makes servicing much easier.) It's perfectly rational to suspect that the configuration is decided at runtime with a simple flag, and that you can patch the kernel to enable the functionality that is really intended for the server editions. This doesn't have to be more than a few bytes.

It's a silly thing to do, and leaves your OS in an unsupported state, but it can be possible.

As I (and others) have stated, this patch is most likely making a hybrid kernel that has the memory support from the server software patched into the kernel for the client OS. That is why people keep mentioning the fact that the server version support it. You and ShamRocker1 are the ones who keep claiming that it simply isn't possible at all without stating any facts to back up your claims.

Well. We managed to get 4 pages of crap.

No, it didn't, and it isn't (supported).

Actually, XP did originally support it. The license limited it to 4GB, but you could use the whole 4GB with PAE (and not lose any address space to things like the graphics card.) It was disabled in SP1 because of compatibility issues with incorrectly designed drivers.

I don't think you understand. The ability to use 36-bit addressing is already present in 32-bit Windows. It's solid, fully tested implementation that has been around for ages. If you want some examples of what the various 32-bit versions of Windows Server can support, you can click here.

The server and client version of Windows aren't two separate operating systems. They're the same OS, built from the same code, but with different settings. They even share many binaries (this makes servicing much easier.) It's perfectly rational to suspect that the configuration is decided at runtime with a simple flag, and that you can patch the kernel to enable the functionality that is really intended for the server editions. This doesn't have to be more than a few bytes.

It's a silly thing to do, and leaves your OS in an unsupported state, but it can be possible.

Are you still talking about PAE? Reading this thread it seems to me that nobody denied the existence of PAE or its ability to extend memory usage in a 32-bit OS under the right conditions, but rather that it isn't practical for consumers using standard consumer hardware because of incompatibilities.

As I (and others) have stated, this patch is most likely making a hybrid kernel that has the memory support from the server software patched into the kernel for the client OS. That is why people keep mentioning the fact that the server version support it. You and ShamRocker1 are the ones who keep claiming that it simply isn't possible at all without stating any facts to back up your claims.

Well. We managed to get pages of crap.

Why did you quote me there without using quote tags??

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

    • No registered users viewing this page.
  • Posts

    • DVD only? What kind of self-respecting optical disk backup/ripping tool doesn't support Blu-ray these days? I burned all my DVDs like 15+ years ago...
    • ...but you're Johnny, from Australia?    
    • Glow 26.9 by Razvan Serea Glow provides detailed reporting on every hardware component in your computer, saving you valuable time typically spent searching for CPU, motherboard, RAM, graphics card, and other stats. With Glow, all the information is conveniently presented in one clean interface, allowing you to easily access and review the comprehensive hardware details of your system. Glow provides detailed information on various system aspects, including OS, motherboard, processor, memory, graphics card, storage, network, battery, drivers, and services. The well-organized format ensures easy access to the required information. You can export all the gathered data to a plain text file, facilitating sharing with others for troubleshooting purposes. No installation needed. Just decompress the archive, launch the executable, and access computer-related information. Glow runs on Windows 11 and Windows 10 64-bit versions. Glow 26.9 changelog: New Features The processor hardware detection engine has been significantly enhanced beyond traditional Intel and AMD architectures. Native support is now available for modern platforms such as Apple Silicon (M-Series) and the newly introduced NVIDIA Spark. In addition, all ARM-based processors can now be accurately distinguished between ARM32 and ARM64 architectures, providing precise hardware reporting. This marks a major milestone for Glow's hardware detection capabilities. The RAM manufacturer identification algorithm has been expanded. JEDEC vendor codes for popular brands such as Patriot, PNY, Team Group, GeIL, Lexar (Longsys), and Asgard/Gloway have been integrated into the database. This significantly reduces the likelihood of incorrect or "Unknown Manufacturer" results and improves overall hardware detection accuracy. New Public IP Address and Internet Service Provider (ISP) features have been added to the Network section. To ensure reliability, this information is retrieved from the trusted service ipwho.is. When Hiding Mode is enabled, no requests are sent and these features remain hidden, as they may expose sensitive information. The search engine used in the Installed Drivers, Installed Services, and Installed Applications sections has been enhanced. You can now perform more flexible and accurate searches using initials, partial matches, and loosely arranged character sequences. The TS Preloader loading bar has been rebuilt using our modern TS Custom Controls graphics library, developed entirely in-house. As a result of this infrastructure upgrade, the loading bar now features smooth rendering and rounded corners that align with the visual style of Windows 11. [TS Updater] A new validation algorithm has been added to check whether the target application is currently running before the update process begins. Bug Fixes Resolved a condition that could prevent TS Preloader from shutting down safely during rare application crash scenarios. Fixed a text alignment issue in the Network section affecting the display of DNS addresses. Alignment is now rendered correctly. [TS Updater] Fixed an issue that could prevent the updated application's executable "*.exe" file from being located after the update process. [TS Updater] Fixed a bug that could leave outdated "*.sha256" files in the application directory after an update. [TS Updater] Fixed a rare issue that could cause subfolders to be moved into the root directory after an update. [TS Updater] Fixed an issue during the first launch that could cause flickering and a temporary white window appearance due to Windows Defender interactions. Changes A small improvement has been made to the internet connectivity detection algorithm. Connectivity checks are now performed in the background with minimal impact on the user interface thread. The keyboard shortcuts in the top menu have been reorganized and simplified to provide a consistent experience across all Türkaysoft applications and to avoid potential conflicts with standard Windows shortcuts. The TS Preloader splash image has been updated with a Türkiye-themed stadium design to celebrate Türkiye's qualification for the 2026 FIFA World Cup—its first appearance in 24 years. Congratulations, Türkiye! The TS Custom Controls module has been updated to version 26.6, delivering improved stability and a more polished visual appearance. [TS Updater] The application icon has been redesigned to provide a more modern and refined look. Note: Always unzip the program before using it. Otherwise you may get an error. Download: Glow 26.9 | 1.8 MB (Open Source) Links: Glow Homepage | Screenshot | Github Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • DWARF mini review: the world's smallest smart telescope for night and day sky captures by Steven Parker DWARFLAB reached out to me asking if I was interested in checking out the DWARF mini, which is a portable astronomy telescope designed for amateur astronomers. Why do I say it's for amateurs? Well, for starters, it's not what you'd call "high end"; it's more of a professional-grade starting point for amateurs serious about capturing what's up there in our night and day skies. A typical amateur astronomer is most likely thousands of dollars deep into the hobby, and I will make no claims that this DWARF mini (at a fraction of the cost) could replace it all, okay? Well, if you read on, it will be clearer what I am trying to convey. Disclosure: DWARFLAB provided a free sample without any editorial input or review pre-approval. I have always been interested in looking up and observing the night sky. I see satellites crossing the sky above my garden most nights, and I am always looking at the moon. Yeah, I have a 200MP camera on my phone, but at 200X zoom, AI takes over and makes the pretty moon pictures that I snap, the DWARF mini does not, you get an actual true picture of what you can barely see with the naked eye. Before we start, let's share the highlights of the DWARF mini in bite-sized format: Pocket-Sized & Ultra-Lightweight Weighing just 1.85 lbs (840g), the DWARF mini easily fits into a backpack or large pocket. Its all-in-one, compact design makes it the ultimate grab-and-go digital telescope for hiking, camping, or traveling to dark-sky locations. Intuitive App Control & Built-in Sky Atlas Go from unboxing to your first shot in just 3 minutes! The DWARFLAB App provides a seamless experience with an interactive star map. Simply select your target and start exploring without the steep learning curve of traditional setups. Auto GOTO & 360° Pivot Freedom Enjoy pinpoint automated tracking with full 360° rotation. Powered by a high-sensitivity Sony IMX662 sensor (1/2.8-inch, 2.9μm pixels), it captures amazing, low-noise astro details, bringing faint nebulas and star clusters to life with stunning clarity. Pro-Level EQ Mode & Long Exposure Unlock advanced deep-space imaging with Equatorial (EQ) Mode. Supporting impressive single-frame exposures up to 90 seconds and featuring built-in light pollution filters, it easily cuts through city glow to reveal intricate celestial structures. Smart Cloud Processing & All-Ages Fun Effortlessly enhance your raw data with integrated cloud processing for professional-grade results. Perfect for beginners, kids, and adults, this telescope makes exploring and sharing the wonders of the universe an exciting, family-friendly adventure. The packaging is a pretty minimal affair with the outer box opening like a flap to reveal the plastic mould of the DWARF mini sitting in it. Below, the Sun filter, charging cable, cleaning cloth, and documentation can be found. DWARFLAB also provided a Mini Hydraulic Tripod ($89.99), and I highly recommend getting it if you plan on purchasing the DWARF mini, as it fully supports the motorized tracking feature of the telescope; plus, at 840g, the weight of the telescope, you will need a tripod that supports more than the weight of a smartphone anyway. What's in the box DWARF Mini Smart Telescope × 1 Sun Filter x 1 Type-C to Type-C Cord x 1 Cleaning Cloth x 1 User Guide With that out of the way, here are the full specs: DWARF mini Dimensions (DWH): 60.70 mm x 100.38 × 183.61 (2.39" x 3.95" x 7.23") Weight: 840g (1.85lbs) Aperture diameter: 30 mm (telephoto), 3.4 mm (wide angle) Image Sensor: SONY IMX662 1/2.8" (Telephoto) OmniVision OS02K10 1/2.8" (Wide-angle) Focal length: 150 mm (telephoto), 6.7 mm (wide-angle) Equivalent focal length: 1016 mm (telephoto), 45 mm (wide-angle) Shutter Speed: Tele - 1/10000-90s, Wide - 1/10000-30s Maximum exposure time: 90s (telephoto & wide-angle), Both in EQ mode Rotation range: Lens: 225°, Base: 360° Effective Pixels: 2.07M Maximum Resolution: 1920 × 1080 (Telephoto & Wide-angle) Built-in filters: Astro, Dark, Duo-Band (Telephoto), Astro (Wide-angle) Output: JPG, FITS, TIFF, MP4 Shooting Mode: Photos, Videos, Astronomy, Burst Shooting, Time-lapse Photography Storage: 64 GB Battery: Built-in 7000 mAh, supports external USB charging Charging Port: Type-C NPU: 1 TOPS Features: WiFi, NFC NFC One-Touch Connection Astronomy Post-Processing/Appointment Shooting/Astronomy Mosaic Wi-Fi Transmission Range: 15m (open environment) Color: Black Compatibility: iOS & Android smartphones/tablets Warranty: 2-years (24-months) MSRP: $399 Design Charge port On/off button Lens On the DWARF mini itself, it is a pretty minimal affair. On one side, there is a Type-C USB port to charge the non-removable 7000 mAh battery, and on the other side, a large button to power on or off the telescope. The button is flanked by an LED that is green when connected via the DWARFLAB app, or lights up red when being powered off. Below the button, there are four LEDs that indicate battery power. The DWARF mini does not have any sharp edges as all sides are rounded off; it has a good heft to it, but the weight of it feels quite balanced in the hand, so it isn't top or bottom-heavy. On the front there is the DWARFLAB logo which is quite small and there are no other markings on it. The tripod offers full 360° rotation of the motorized base, which allows for tracking for the time-lapse mode, but also for the 90-second captures of nearer objects in the sky, such as the Sun or the moon. Usage To get started, simply power on the DWARF mini and open the DWARFLAB app, tap on Connect, and it will scan for the DWARF mini over the Wi-Fi network. The device supports both 2.4 GHz and 5 GHz Wi-Fi, as well as Bluetooth for discovery, so connection issues were minimal in my experience with it. As previously noted in the specs, the DWARF mini will stay connected with a phone or tablet up to 15 meters in an open environment, such as a backyard. Lighting status Powering on: The green circular light will rotate and breathe in turn Powering off: The red circular light is gradually extinguished Connecting: Green light strip rotating Connected: Green light strip solid/always on 4 lights 1= 0-25%, 2= 25-50%, 3= 50-75%, 4= 75-100% battery power To view the full lighting status, such as tracking mode and connection failure, you can check the user guide on the official DWARFLAB page. DWARFLAB app Above, you can see the steps undertaken to connect the DWARFLAB app to my Galaxy S26 Ultra. Weirdly, I got an alert that a firmware update failed to get uploaded to the DWARF mini the first time, but upon retrying, it worked. Then place the DWARF mini outside, make sure your smartphone or tablet is connected to it, and then head back inside, because you can manage it from the comfort of your home. Simply enter the Atlas tab in the app and search for what you want to capture, and then tap on the camera icon; the DWARF mini will then attempt to track the object and give you a live view right on your connected device. Results I've had the DWARF mini since April, but even though my garden is south-facing, I had a lot of trouble trying to capture a good image of the moon. In the end, it was possible after I took it with me on a trip to my parents in Southend, UK, at the end of May. Here is a capture of the moon, resulting from 20 stacked images over a 90-second exposure. What you are seeing here is not AI-assisted. A good example of what I mean is the latest flagships with their 200MP cameras claiming to capture things like closeups of the moon, and while they are not as good as the above example on the DWARF mini, the resulting image on smartphones is actually AI-assisted above 30X zoom. Here is an example of a similar shot at the moon at 200X zoom using an HONOR Magic8 Pro. The difference is clear. Next, here we have a shot of the daytime moon. Here is a shot of Arcturus, the red giant star, which is the fourth brightest in the night sky. As previously mentioned, it could be a bit clearer, but clouds passing in front of it muddied the shot a bit. The Sun The DWARF mini also ships with a sun filter, meaning you can take great shots of the sun as well. Tracking Sun Resulting (stacked) shot Live zoom The pictures themselves are limited to Full HD, and some of the examples actually came out in HD (1280x720), but this is because the standard telescopic result is in 720p while "Wide" is in 1080p. Above you can see how in the app the Sun is tracked, the resulting capture, and Live zoom. I have only scratched the surface of what is possible with this telescope; I found several examples online of shots of the Milky Way, among others, such as nebulae and galaxies. All of this requires patience and knowledge, although if you know what you are looking for, simply enter it in the Atlas tab in the DWARFLAB app, tap the camera icon, and the telescope will attempt to track it. Conclusion The good The DWARF mini definitely places itself in a price point that makes astrology accessible to anyone looking to get started in the hobby. Say you want to have a closer look at the moon, simply enter it in the Atlas, and the Live view also lets you zoom in and snap pictures. The bad Some issues I came across while operating the DWARF mini were that it sometimes failed to connect unless I held my smartphone right next to it, and finding and tracking sometimes took several attempts to get it calibrated. I discovered that it helped if I sort of positioned and pointed the telescope in the general area it was supposed to detect, but this obviously wouldn't work with objects you can't see with the naked eye; more testing is required for that. Another bit of advice is to ensure that the lens is clean. While making the examples of live zooming on the sun, I discovered that the telescope lens and sun filter were not completely clean, and only after cleaning with a microfiber cloth was I able to get a decent shot of the sun. Where to buy and a coupon Okay, $399 is not cheap for a side hobby, but nor is a $1,500 smartphone flagship that you'll most likely have for a couple of years. This is a one-time entrance into astrology, and it won't become obsolete in one year like a smartphone. It's a thumbs up from me. The DWARF mini is available to buy right now in the U.S. and U.K. at the links below. DWARF mini for $399 on the official site DWARF mini for $399 on Amazon U.S. Use the NEOWIN5OFF coupon code for an additional 5% off at checkout (expires June 21) As an Amazon Associate, I earn from qualifying purchases.
  • Recent Achievements

    • One Month Later
      lamborghiniv10 earned a badge
      One Month Later
    • Week One Done
      lamborghiniv10 earned a badge
      Week One Done
    • Reacting Well
      X-No-file earned a badge
      Reacting Well
    • One Month Later
      pestcontrol46 earned a badge
      One Month Later
    • Week One Done
      pestcontrol46 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      PsYcHoKiLLa
      270
    3. 3
      +Edouard
      75
    4. 4
      Skyfrog
      74
    5. 5
      Steven P.
      71
  • Tell a friend

    Love Neowin? Tell a friend!