• 0

How to build an operaing system ?


Question

Recommended Posts

  • 0

lol , look what i found in autoexec.bat

SET windir=D:\WINXP

SET winbootdir=D:\WINXP

(((((((( SET COMSPEC=D:\WINXP\COMMAND.COM ))))))))

SET PATH=D:\WINXP;D:\WINXP\COMMAND

SET PROMPT=$p$g

SET TEMP=D:\WINXP\TEMP

SET TMP=D:\WINXP\TEMP

what do you think now gameguy ?

  • 0

NT does not have any dependency on MS-DOS. As for your autoexec.bat, that is strange because it should be empty, and unless you set it up, Windows XP doesn't even parse autoexec.bat.

  • 0

Elagizy

what you said about running windows from dos going into the i386 folder etc, sound like you started the installation from dos and installed it that way, rather than booting from the cd. as for you autoexe.bat, thats probably a result of that process, from a clean install onto a blank hdd my autoexe.bat is empty!

as for testing an os to check if it will work on differewnt computers .... all computers are different, youd have to make sure your operating system could handle different types of hardware through some sort of divers or by embedding it all into one kernel (much the way bsd does things)

as for windows 95/98 AND me ... they all were based on the 9x kernel which was run in dos (yes me ran on dos but it was hidden from the user)

as for nt/2000/xp/2003 they all require the ntldr to boot the system and use one file mainly to run (ntoskrnl), THERE IS NO DOS anywhere with xp 2003 etc, trhey mainly use those files you talked about for legacy and configuration reasons

as for writting your own operating system, if you needed these questions answered your going to be in for a tough reason, to create anything usefull youll need to know assembly to bootstrap your system and id say a fair amount of c. Youd also do weel to look into compiler design!

http://www.ansanest.com/josh/ goes through the very very basic steps of creating a bootable os, all be it slow practically useless and basic!

http://cs.wwc.edu/~aabyan/464/Book/ that is a book on compiler design, if you want to look at how things go through and compile to usable code, usefull if you want to progress into a fuller featured environment

few notes

linux is the kernel of an os, the full os would be correctly referenced as GNU/linux as its the other (gnu) programs running on linux that make the os what it is, linux distributions all package different software!

dos is basically like a small kernel and a a load of applications making it useful! windows 95/98/me all used dos to boot and interact with some of the hardware

windows xp/2000/2003 uses the nt loader and nt kernel which is NOT WHERE NEAR to being dos!

freebsd openbsd and company all use one single kernel for interacting with all hardware and providing a lot of functionality, again its the packages by other authors that allow it to be usefull

if you really are stuggling to understand most of this id suggest a few things before going into fully fledged os design

1) maybe try going through something like a gentoo install/compilation to see how much that alone invloves and get a true sense of how it installs

2) maybe even try creating your own linux distribution, that alon is hard enough but not wuite as hard as making a nicly working os!

http://www.se.linuxfromscratch.org/lfs/news.html linuxfromsctach is basically a free online book showing you how to build your own distibution (like gentoo but you do EVERYTHING) that would give you an excelent insight into it all and with it youd be handling souce code so by the end its your distribution and you can see all th work thats gone into it!

3) if linux isnt your thing id say get a working freedos environment and bootable http://www.freedos.org/ or http://freedos-32.sourceforge.net/ (a 32bit kernel for freedos) then from there start by coding your own envirment for it maybe? basically doing the step microsoft did with windows 3.1 ... making something usefull of a dos environment!

http://fxr.watson.org/ is a very cool site, you can explore a few kernels for yourself to see ALL the cod3e behind the very heart of the os! linux, bsd, darwin there all there and browsable so you can see what sort of coding is done to make something usefull and worthwhile!

  • 0

I think he just confused autoexec.bat with autoexec.nt. Windows XP has an autoexec.nt and config.nt file in windows\system32 that gets run every time you run an old DOS app. The blank DOS files in the roor of the active HD are just there for legacy purposes so that any DOS apps that look for them don't crap themselves. As for Windows XP needing DOS to boot, it's not true in any sense. To elaborate on how berz explained the boot process, the boot process for XP is such (from what I know): the BIOS looks at the hard drive which you have configured to boot, reads the partition table and finds the active partition, uses the MBR to find the boot sector, and then executes it. The boot sector is already part of XP and it loads the boot loader (ntldr). ntldr has theability to either load another boot sector (such as one for Windows 9x if you're dual booting) or load an installation of NT. ntldr also has a minimal ability to read NTFS partitions so when you tell it to boot, for example, "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS" (which it reads from boot.ini), it will look in that folder on that partition load the NT kernel, hal, etc. and then the services (drivers and subsystems) will load in whatever order they're configured as in the registry (sort of like runlevels). Once that's done, the GUI starts up and depending on whether there's a security system (usually there is, unless the install was made with Windows Embedded and it was taken out), a user will have to authenticate themselves. After that, the default shell is loaded (usually explorer.exe) and whatever else is specified in the registry is executed, and XP will have finished booting. There's also a slightly different way of booting which does involve DOS, in which the partition with XP on it must be FAT32 (unless you have an NTFS driver loaded, although I've never tried it) and you run good old win.com as if you were booting Windows 3.x, and win.com will load the kernel and whatever else the way ntldr would. Also, when booting from DOS, win.com will completely wipe it from memory since XP has full hardware control and if you run any DOS apps from XP they will run from XP's DOS subsystem.

  • 0
Elagizy

what you said about running windows from dos going into the i386 folder etc, sound like you started the installation from dos and installed it that way, rather than booting from the cd. as for you autoexe.bat, thats probably a result of that process, from a clean install onto a blank hdd my autoexe.bat is empty!

as for testing an os to check if it will work on differewnt computers .... all computers are different, youd have to make sure your operating system could handle different types of hardware through some sort of divers or by embedding it all into one kernel (much the way bsd does things)

as for windows 95/98 AND me ... they all were based on the 9x kernel which was run in dos (yes me ran on dos but it was hidden from the user)

as for nt/2000/xp/2003 they all require the ntldr to boot the system and use one file mainly to run (ntoskrnl), THERE IS NO DOS anywhere with xp 2003 etc, trhey mainly use those files you talked about for legacy and configuration reasons

as for writting your own operating system, if you needed these questions answered your going to be in for a tough reason, to create anything usefull youll need to know assembly to bootstrap your system and id say a fair amount of c. Youd also do weel to look into compiler design!

http://www.ansanest.com/josh/ goes through the very very basic steps of creating a bootable os, all be it slow practically useless and basic!

http://cs.wwc.edu/~aabyan/464/Book/ that is a book on compiler design, if you want to look at how things go through and compile to usable code, usefull if you want to progress into a fuller featured environment

few notes

linux is the kernel of an os, the full os would be correctly referenced as GNU/linux as its the other (gnu) programs running on linux that make the os what it is, linux distributions all package different software!

dos is basically like a small kernel and a a load of applications making it useful! windows 95/98/me all used dos to boot and interact with some of the hardware

windows xp/2000/2003 uses the nt loader and nt kernel which is NOT WHERE NEAR to being dos!

freebsd openbsd and company all use one single kernel for interacting with all hardware and providing a lot of functionality, again its the packages by other authors that allow it to be usefull

if you really are stuggling to understand most of this id suggest a few things before going into fully fledged os design

1) maybe try going through something like a gentoo install/compilation to see how much that alone invloves and get a true sense of how it installs

2) maybe even try creating your own linux distribution, that alon is hard enough but not wuite as hard as making a nicly working os!

http://www.se.linuxfromscratch.org/lfs/news.html  linuxfromsctach is basically a free online book showing you how to build your own distibution (like gentoo but you do EVERYTHING) that would give you an excelent insight into it all and with it youd be handling souce code so by the end its your distribution and you can see all th work thats gone into it!

3) if linux isnt your thing id say get a working freedos environment and bootable http://www.freedos.org/ or http://freedos-32.sourceforge.net/ (a 32bit kernel for freedos) then from there start by coding your own envirment for it maybe? basically doing the step microsoft did with windows 3.1 ... making something usefull of a dos environment!

http://fxr.watson.org/ is a very cool site, you can explore a few kernels for yourself to see ALL the cod3e behind the very heart of the os! linux, bsd, darwin there all there and browsable so you can see what sort of coding is done to make something usefull and worthwhile!

585121668[/snapback]

Thank you wehttam, you got a lot of experience in this , your links is great i think i will spend all the holiday to read them

  • 0
I think he just confused autoexec.bat with autoexec.nt. Windows XP has an autoexec.nt and config.nt file in windows\system32 that gets run every time you run an old DOS app. The blank DOS files in the roor of the active HD are just there for legacy purposes so that any DOS apps that look for them don't crap themselves. As for Windows XP needing DOS to boot, it's not true in any sense. To elaborate on how berz explained the boot process, the boot process for XP is such (from what I know): the BIOS looks at the hard drive which you have configured to boot, reads the partition table and finds the active partition, uses the MBR to find the boot sector, and then executes it. The boot sector is already part of XP and it loads the boot loader (ntldr). ntldr has theability to either load another boot sector (such as one for Windows 9x if you're dual booting) or load an installation of NT. ntldr also has a minimal ability to read NTFS partitions so when you tell it to boot, for example, "multi(0)disk(0)rdisk(0)partition(1)\WINDOWS" (which it reads from boot.ini), it will look in that folder on that partition load the NT kernel, hal, etc. and then the services (drivers and subsystems) will load in whatever order they're configured as in the registry (sort of like runlevels). Once that's done, the GUI starts up and depending on whether there's a security system (usually there is, unless the install was made with Windows Embedded and it was taken out), a user will have to authenticate themselves. After that, the default shell is loaded (usually explorer.exe) and whatever else is specified in the registry is executed, and XP will have finished booting. There's also a slightly different way of booting which does involve DOS, in which the partition with XP on it must be FAT32 (unless you have an NTFS driver loaded, although I've never tried it) and you run good old win.com as if you were booting Windows 3.x, and win.com will load the kernel and whatever else the way ntldr would. Also, when booting from DOS, win.com will completely wipe it from memory since XP has full hardware control and if you run any DOS apps from XP they will run from XP's DOS subsystem.

585121673[/snapback]

:whistle: ooooooh , i understand now , seems reasonable for me , and i think i understand every line in BOOT.INI thanks for help

  • 0
Ok, but why when i setup WINDOWS XP in DOS !! ( when i goto in DOS and run smartdrv.exe then goto i386 and then winnt.exe ) that means that windows depends on DOS

No, that means that the WINNT.exe program depends on DOS. Which is not the same as Windows XP itself. XP doesn't need DOS. It uses "ntldr" to run. Nothing more.

also try to remove the 3 DOS files msdos.sys , io.sys, command.com , u will face a lot of troubles ........ all of that prove that Windows depends on DOS

Hmmm...

C:\>dir /ah
 Volume in drive C is Naomi
 Volume Serial Number is 6C57-3DED

 Directory of C:\

30/08/2004  12:15               211 boot.ini
18/12/2004  11:06     1,073,270,784 hiberfil.sys
30/08/2004  12:22                 0 IO.SYS
30/08/2004  12:22                 0 MSDOS.SYS
03/08/2004  21:38            47,564 NTDETECT.COM
03/08/2004  21:59           250,032 ntldr
18/12/2004  11:06     1,610,612,736 pagefile.sys
30/08/2004  14:27    <DIR>          RECYCLER
30/08/2004  12:27    <DIR>          System Volume Information
01/11/2004  20:01            23,821 _NavCClt.Log
               8 File(s)  2,684,205,148 bytes
               2 Dir(s)  64,280,051,712 bytes free

So, removing the two zero-length files IO.SYS and MSDOS.SYS will cause a "lot of troubles", will it? Oh dear.

COMMAND.COM is the MS-DOS command line interpreter. You can quite happily delete it. COMMAND.COM has been superseded by CMD.EXE anyway.

ok so tell me what is the files which make windows depends on emulated DOS ,

CMD.EXE. And COMMAND.COM if you want to use that (which you don't, as it's rubbish).

as i think smartdrv.exe makes the computer thinks that its working on winxp

SMARTDRV speeds up DOS drive I/O operations. See here. It has NOTHING to do with pretending to be XP.

yes u right but we must say that dos files was the KEY files to make you start windows

No, read this. It tells you how it all works. It uses NTLDR. Not DOS.

i wonder how this 3 intelligent dos files recognize all of that which are you talking about on different pcs with different bios and different devices ....... ohhhh amazing ........ i think IO.sys has the responsibility for this task.

How can IO.SYS, a zero-length file possibly do anything?

i think i have found an EQUIVALENT to this 3 files which windows in a bad need to them cause i always face some troubles with them when i got a virus and correct me if i am wrong , what about HIMEM.SYS, Hiberfil.sys, NTldr and finally you need to tell me what about ((((((((((((( CONFIG.DOS, BOOTSECT.DOS ))))))))) now i guess some body will say to me THAT IS THE EMULATED DOS , in my opinion it is exactly dos files but in other name

HIMEM.SYS is a throwback to the olden days. It's not relevant.

HIBERFIL.SYS is the file that is used when you put your computer into hibernation (i.e. when you do a soft power off).

NTLDR loads XP. It's called from the boot sector in your XP drive.

My AUTOEXEC.BAT file is empty (another of those very powerful zero-length files - how fearsome).

CONFIG.DOS and BOOTSECT.DOS are (according to MSDN) used when you plan to boot more than one operating system on your computer (e.g. XP and Me, and so on).

More resources:

NT boot process.

Boot sector.

Win2K boot process.

Files required to start Win2K.

  • 0
Hmmm...

C:\>dir /ah
 Volume in drive C is Naomi
 Volume Serial Number is 6C57-3DED

 Directory of C:\

30/08/2004 ?12:15 ? ? ? ? ? ? ? 211 boot.ini
18/12/2004 ?11:06 ? ? 1,073,270,784 hiberfil.sys
30/08/2004 ?12:22 ? ? ? ? ? ? ? ? 0 IO.SYS
30/08/2004 ?12:22 ? ? ? ? ? ? ? ? 0 MSDOS.SYS
03/08/2004 ?21:38 ? ? ? ? ? ?47,564 NTDETECT.COM
03/08/2004 ?21:59 ? ? ? ? ? 250,032 ntldr
18/12/2004 ?11:06 ? ? 1,610,612,736 pagefile.sys
30/08/2004 ?14:27 ? ?<DIR> ? ? ? ? ?RECYCLER
30/08/2004 ?12:27 ? ?<DIR> ? ? ? ? ?System Volume Information
01/11/2004 ?20:01 ? ? ? ? ? ?23,821 _NavCClt.Log
 ? ? ? ? ? ? ? 8 File(s) ?2,684,205,148 bytes
 ? ? ? ? ? ? ? 2 Dir(s) ?64,280,051,712 bytes free

So, removing the two zero-length files IO.SYS and MSDOS.SYS will cause a "lot of troubles", will it?  Oh dear.

COMMAND.COM is the MS-DOS command line interpreter.  You can quite happily delete it.  COMMAND.COM has been superseded by CMD.EXE anyway.

CMD.EXE.  And COMMAND.COM if you want to use that (which you don't, as it's rubbish).

SMARTDRV speeds up DOS drive I/O operations.  See here.  It has NOTHING to do with pretending to be XP.

No, read this.  It tells you how it all works.  It uses NTLDR.  Not DOS.

How can IO.SYS, a zero-length file possibly do anything?

HIMEM.SYS is a throwback to the olden days.  It's not relevant.

HIBERFIL.SYS is the file that is used when you put your computer into hibernation (i.e. when you do a soft power off).

NTLDR loads XP.  It's called from the boot sector in your XP drive.

My AUTOEXEC.BAT file is empty (another of those very powerful zero-length files - how fearsome).

CONFIG.DOS and BOOTSECT.DOS are (according to MSDN) used when you plan to boot more than one operating system on your computer (e.g. XP and Me, and so on).

More resources:

NT boot process.

Boot sector.

Win2K boot process.

Files required to start Win2K.

585121788[/snapback]

Thanks DrZoidberg for making this clear , i think my winxp is not a clean install and actually i don't have a bootable cd so i thought thats normal in any kind of installation. but can you tell me please why people said that windows longhorn will be faster in installing and in performance, they said it will be installed like as you are using a GHOST copy, is that true ?

  • 0
Longhorn will install quickly because it just copies an image of a pre-made installation over to the hard drive. After that it's just a matter of installing drivers and setting up users.

585122061[/snapback]

Do you mean it has the mechanism of Norton Ghost ?

  • 0
Ok, but why when i setup WINDOWS XP in DOS !! ( when i goto in DOS and run smartdrv.exe then goto i386 and then winnt.exe ) that means that windows depends on DOS

And if you had a good copy of the Windows CD AND your bios set to boot from the CD... You'd know that Windows NT does not need DOS to install ;)

  • 0
i think i have found an EQUIVALENT to this 3 files which windows in a bad need to them cause i always face some troubles with them when i got a virus and correct me if i am wrong , what about HIMEM.SYS, Hiberfil.sys, NTldr  and finally you need to tell me what about ((((((((((((( CONFIG.DOS, BOOTSECT.DOS ))))))))) now i guess some body will say to me THAT IS THE EMULATED DOS , in my opinion it is exactly dos files but in other name :)

585121581[/snapback]

:laugh: Do you even know what those files are?

himem.sys - DOS memory manager, superseded by Windows 9x, nonexistant in NT systems.

hiberfil.sys - Hibernation file for storing RAM contents during a hibernation.

NTLDR - Boot loader for NT systems.

config.dos - Old config.sys created by NT setup routine, config.sys is then erased.

bootsect.dos - Created by NT setup, the previous boot sector that launched DOS, used when booting into DOS via NT boot menu.

  • 0
lol , look what i found in autoexec.bat

SET windir=D:\WINXP

SET winbootdir=D:\WINXP

(((((((( SET COMSPEC=D:\WINXP\COMMAND.COM ))))))))

SET PATH=D:\WINXP;D:\WINXP\COMMAND

SET PROMPT=$p$g

SET TEMP=D:\WINXP\TEMP

SET TMP=D:\WINXP\TEMP

what do you think now gameguy ?

585121588[/snapback]

I think you found what XP setup wanted to be found by legacy applications. DOS applications are more or less emulated (not quite, but I don't know the right word) on XP, and those applications still have the ability (and right) to use autoexec.bat if they want to. Notice the third line, the comspec is command.com? Not in XP it isn't, but this file is only used by DOS applications, not Windows.

  • 0
DOS applications are more or less emulated (not quite, but I don't know the right word) on XP...

585123463[/snapback]

I guess the term would be virtualized. (or something similar). No emulation takes place. What happens is windows loads the program into memory, changes pages tables to make the memory look continuous and then creates a task. That task refers to the memory where the program is loaded, but also has the EFLAGS.VM bit set. When this new task is switched to, the processor will see the VM bit and switch to virtual mode. In virtual mode, the DOS program will act normally since as far as it's concerned, it's running in real mode (which is what DOS programs run in). If the dos programs executes a privilaged instruction or an exception occurs, control of the CPU is handed back to a piece of OS code called a virtual machine monitor. The monitor will handle the exception in such a way as to look normal to the DOS program. When done, execution is handed back to the DOS program until such a time as another exception occurs or a task switch. There are obviously a lot more details, but this is the jist of it.

  • 0
I think you found what XP setup wanted to be found by legacy applications. DOS applications are more or less emulated (not quite, but I don't know the right word) on XP, and those applications still have the ability (and right) to use autoexec.bat if they want to. Notice the third line, the comspec is command.com? Not in XP it isn't, but this file is only used by DOS applications, not Windows.

585123463[/snapback]

That's correct. NT OSes use a virtual machine in the form of ntvdm.exe that allows 16-bit programs to be run on 32-bit systems. You often see wow.exe, or something similar, in the process list, too. That's Windows On Windows which provides the framework for 16-bit windows apps to run. This is why there is still a system directory in addition to the system32 directory, and why many of the older libraries exist in an XP install. I think this article sums up all the legacy dependencies.

Backward compatibility was MS's focus. They knew it would be critical to allow for older apps to run on newer operating systems in order for them to gain/maintain dominance. I'm certain this trend will continue as we move toward 64-bit computing. It's made even better by CPUs supporting both 32 and 64-bit apps.

  • 0
I think you found what XP setup wanted to be found by legacy applications. DOS applications are more or less emulated (not quite, but I don't know the right word) on XP, and those applications still have the ability (and right) to use autoexec.bat if they want to. Notice the third line, the comspec is command.com? Not in XP it isn't, but this file is only used by DOS applications, not Windows.

585123463[/snapback]

BTW, i forgot to tell you that i have winme with winxp , is that a reason for making my autoexec.bat full of lines instead of being empty ?

and if the answer is yes , does it mean that winME needs dos to boot ?

  • 0

winme, contrary to popular beleif is actuall still dos based, and uses the windows 9x kernel, its just hidden from the user as opposed to windows 98, there are still ways to boot to dos when me is installed tho :D and its highly likely some of your odd files are to do with windowsme being installed

  • 0
Interesting discussion we have here but not many posts on how to make an operating system lol I suppose its a topic you could spend every hour of the day discussing and go on forever.

585127982[/snapback]

There is some posts including a very usefull links , you may need them without needing to read these posts.... ;)

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

    • No registered users viewing this page.
  • Posts

    • In the way that you framed it incorrectly. You wrote: "The constant need to close all browser sessions and wait for a new version to install" There's no "constant need to close all browser sessions". That's factually incorrect. The browser downloads its updates in the background and installs them when you open it again. Silently. And there's no "wait for a new version to install", updates are small and take 2-3 extra seconds AT MOST, if any. If you have an SSD, there's zero extra time. Also, every mainstream browser operates this way. Firefox, the FOSS go-to browser, the default on almost every Linux distro, does exactly the same. Also, you don't need to constantly restart Edge for updates to install, you can completely ignore them and it doesn't even ask you to handle them, it's all silent and automatic. So I don't understand what else do you want.
    • DuRoBo Krono Review: Portable E-Ink reader with great ideas that need a bit of improvement by Taras Buria Phone-sized e-readers are gaining traction these days, with more people treating them as a getaway device to cure phone addiction (or at least they are trying to) or having a more pocket-friendly reader that is easier to carry and hold. The market now has plenty of such readers to choose from, and DuRoBo is the latest addition, a new player that offers a more interesting approach to the idea. The Krono is a $279 e-reader with an interesting twist, which tries to make the device more fun and ergonomic. Here is my review. Disclaimer: DuRoBo provided the review sample without any editorial input or pre-approval. The Krono comes in a phone-sized box with pink accents. Inside, you get the device itself, a short user manual, and a USB cable. The cable is a bit old-fashioned, Type-A to Type-C, which is a bit disappointing. Hot take: I would rather have no cable in the box rather than another Type-A cable that gets immediately thrown into my box full of similar cables I never use. The Krono also has no charger in the box, as it relies on accessories you already own, which is fine with me. Here are the specs: Dimensions 154 x 80 x 9.0 mm or 6.06" x 3.15" x 0.35" 173 g or 6.10 oz Materials Black or White plastic Display 6.13-inch E-Ink Carta 1200, 1,648 x 824 pixels, 300 ppi Touch-capacitive. Dual-tone frontlight. Processor 8-core Qualcomm Snapdragon 690 (QTI SM6350) 2 performance cores at 2.07 GHz 4 efficiency cores at 1.71 GHz Memory 6 GB Storage 128GB, non-expandable ~104GB available out-of-the-box Operating system Android 15 with a custom launcher Connectivity Wi-Fi and Bluetooth Battery 3,950 mAh battery Buttons and port USB Type-C port Power button, Volume button, Smart Dial Breathing Lights Audio Mono Speaker and Dual microphones In the box The Krono, a Type-A to Type-C cable, user manual Price $279 on Amazon First impressions Right off the bat, no, this is not a phone replacement. Do not approach this device thinking it can serve you as a dumb phone to cure your TikTok addiction. In addition to the fact that the Krono has no cellular connectivity, I strongly believe that no amount of extra devices can fix your phone addiction until you put some serious effort into it. The Krono is a phone-sized e-reader, a companion for your phone dedicated to reading without distractions. The DuRoBo Krono is made of plastic with a very fine texture. It is hardly premium, but I also cannot say it feels cheap. The device is also a bit thick, quite dense, and well-built without rattling or cracking. You get to choose between two colors: white and black. The front has quite thick bezels, which is hardly surprising for an e-ink device. These things use front light, with LEDs usually placed on the screen perimeter. While I do not mind thicker bezels, the notably larger chin cheapens the look a little. What I mind is a notable seam between the display and the main case, which, after just two days of use, collected plenty of dust and specks. The back of the Krono is what makes the device stand out. There is a cylinder (DuRoBo calls it the Axis) embedded in the back of the reader, housing three elements: a power button on the right edge, a Smart Dial on the left edge, and "Breathing Lights" on the back. An etched DuRoBo logo sits below the cylinder, and it is the only piece of branding you can find on the device. Overall, the design and materials are very unassuming, but the cylinder with additional control elements certainly elevates the look and makes it more interesting. Other physical elements include two microphones (one on the top edge and one on the bottom edge), a USB Type-C port, a volume rocker, and a single mono speaker. There is no fingerprint reader, so if you want to protect your device, a PIN is your only option. The official TPU case is not the most premium-looking Display The Krono has a 6.1-inch E-Ink Carta 1200 touchscreen display with a resolution of 1,648 x 824 pixels (300 ppi). The display is front-lit, and you can adjust the brightness and temperature from cool to warm. Unfortunately, the Krono lacks automatic brightness and temperature adjustments, and you cannot set a custom schedule for the frontlight. However, you can set it to always enable frontlight so that you can see what is happening on the screen when turning it on in a dark environment. On the bright side (get it?), the front light can get extremely dim so that the screen is barely readable in a pitch-dark room. The front light is also uniform across the screen, with no noticeable temperature gradients. I am very susceptible to uneven front light, and it is very easy for me to notice it, but the Krono is doing a very good job in this area. I also like that the edge shadow is not very prominent and barely visible in the black variant. E-Ink Carta 1200 is not the newest generation (there are Carta 1250 and 1300), but it is still a good display. It supports three modes: Clarity, Speed, and Quality. In Clarity mode, text is very sharp and easy to read, but you trade that for more ghosting, a slower refresh rate, and more artifacts when the display changes images. Speed mode, as the name suggests, boosts refresh rate and reduces ghosting, but fine print and text become more jagged. Finally, Quality mode is only available in Android apps. It has the lowest refresh rate, but in return, you get much better visuals, improved gradients, and more. Like brightness and temperature, you can toggle modes from the control center. It is available when swiping from the top-right corner of the screen (the top-left is for notifications). I also like that the Krono can work as a desk clock when not in use. It has a bunch of screensavers, including horizontal clocks with time, date, and current battery level. The screen refreshes once per minute, and battery drain is extremely low (not even 1% in 24 hours). It is a great use of the technology, and another thing I wish more e-ink devices featured. Smart Dial The Smart Dial is Krono's main party trick. It sits on the left side of the device and serves multiple purposes. You can twist or press it to perform various actions, depending on the current use case scenario. When reading books, twisting the dial flips through pages, and pressing it refreshes the screen. On the home screen, the dial adjusts the brightness, and holding the dial pressed launches voice note recording. Finally, a quick double press launches the DuRoBo AI chatbot. While the dial scroll is not notched, it is very smooth and has haptic feedback that confirms your actions, which feels very nice. As a long-term Apple Watch user, I love the idea behind the dial. It feels very natural and oddly satisfying to use, especially with that subtle haptic feedback. I never liked flipping pages with touch input, and I strongly believe each e-reader should come with some sort of physical controls for turning pages. The Krono has both volume buttons (which also work as page turners) and the dial, so you are free to use whichever you prefer. With that said, the dial is not perfect. For one, it sticks out of the case way too far for my liking, raising concerns about durability and longevity when carrying the Krono around in a pocket (it is a pocket-sized device after all). Also, it has too much wobble, which cheapens the experience and makes it feel a bit flimsy and unsecured. While there are two plastic guards on the Krono's case, they are way too small for any kind of protection. I also think DuRoBo should let users customize dial actions (the only available customization is scroll direction), particularly for long and double presses. Not everyone needs voice notes, and DuRoBo AI does not work without an active internet connection, leaving the long press essentially useless when offline. I do not mind these features, and I genuinely think they are useful, but I would rather have the ability to toggle between screen modes, turn the frontlight on/off, or launch my favorite app. I also agree with people on Reddit asking developers to let users adjust the dial sensitivity. I hope this is something DuRoBo can implement with a software update to make the experience more personalized (it is a Smart Dial, after all) and incentivize users to fiddle with the Dial more often. The Dial is a fantastic idea, so please, guys, improve it a little. As for ergonomics, they are mostly fine, but the dial's position may feel a little awkward and way too high. When I use a phone or a phone-sized gadget, I tend to rest one of its corners on my palm for a more secure grip. With the Krono, such a grip is impossible because you cannot reach the dial even with big hands. You have to lower the reader a bit and hold it like a bottle without any extra support for the bottom edge. Such a grip is not necessarily uncomfortable (the Krono is also light enough for it), but it requires a bit of muscle retraining. Sometimes, I do not bother with the dial and hold the Krono like my phone, flipping through pages with volume buttons, as they are perfectly positioned for my right-hand thumb. Interestingly, when testing the Krono, I would often find myself thinking that a roller embedded in the long plastic cylinder on the back of the device would have been a much more comfortable solution. There is a free idea for you, guys. Software The Krono runs Android 15 with a very minimal launcher on top. The home screen presents you with a list of apps, a scrollable list of widgets, and your user profile. Widgets can display time, calendar, or recent books for quick access. You can also add or remove apps from the home screen to keep the most useful stuff around without tapping "Apps." I like this minimalistic approach; it looks clean, easy to understand, and light. I understand that some may find the list of all apps way too clean, but fortunately, DuRoBo lets you switch to traditional icons. The reader also has a bunch of preinstalled apps: Read: The default app for reading. Browser: A Chromium-based browser. Files: A simple file manager. Music: A simple music player. Spark: A voice recorder with transcription support and AI summarization DuRoBo AI: A built-in AI chatbot. Transfer: An app for file transfer over Wi-Fi. If that is not enough, there is the Google Play Store, where you can download all the extra apps you need, alternative readers, podcast apps, chatbots, and more. DuRoBo is not trying to give you an all-in-one device. The standard software experience is quite minimal, which makes it easy to approach and learn. The standard reader supports EPUB, EPUB3, AZW3, MOBI, PDF, TXT, DOC, and DOCX, which is more than enough to let you read most books without third-party software. As for customizing the reading experience, you can select one of five built-in fonts, adjust size and thickness, adjust margins and spacing (only three variants for each), change text alignment and direction, toggle the reading status bar, and switch to dark mode. There is also text-to-speech, which utilizes Android's default TTS tech. While I like the simplistic approach, I cannot help but feel DuRoBo could have made the built-in reader a bit more customizable. However, I am not going to bog down on this, as you can always install any other reader you prefer using the Play Store or by sideloading an APK. Getting books to the Krono is very simple. Given that the device is an Android smartphone without cellular connectivity, you can transfer files via a USB Type-C cable, download them using the built-in browser, share them over Bluetooth, or use cloud storage. My favorite was the built-in Transfer app. It is simple, reliable, and very well-designed. I was surprised by how well-designed the web portal is. It is fast, pretty, and properly categorized. Well done! Once you have your books loaded, you can highlight or underline text, add annotations, bookmark pages, check the table of contents, and ask AI about the selected text. Unfortunately, the Krono has no built-in vocabulary, but again, that is something a third-party reader could fix. Overall, the built-in reader is light and snappy, with just the minimum amount of features for a regular user to enjoy reading books. The Krono has no built-in reading tracking, so stat nerds will have to look for third-party reading apps. However, you can set a daily reading goal, and the reader will notify you when you reach it (for example, one hour). You can also set a reminder to read at a certain time, and when the time comes, the Krono will light up its back LEDs and unlock itself to nudge you. Other than that, the rear LEDs do nothing, not even showing charging progress, which is an unfortunate misopportunity if you ask me. Quirks aside, Krono's Android runs quite snappily and bug-free. Early reviews of the Krono criticized its Android 13-based software quite a lot, but now, the reader runs Android 15, and its software has fixed plenty of initial complaints. I never experienced any issues with built-in apps. AI attempts The DuRoBo Krono comes with a built-in AI chatbot. There is no information on what model powers this thing, but the system says it was "trained by Google." You can launch the bot from the app list or by double-pressing the dial. It works just like any other chatbot, and you can ask it anything by typing or using voice input. The AI saves your chats, and you can rename, export, or delete them. DuRoBo AI requires an active internet connection, and it does not work offline. Its reach and capabilities are also limited. You can only chat in the app and use it in the reader app as a makeshift vocabulary. However, the implementation is kinda awkward. You can only send a selected portion of text to AI without giving it any requests or instructions. I highlighted the word "dumb," and it apologized to me for not being useful. You also cannot ask follow-up questions or send the generated response to a separate chat. The chatbot is also slow, even with fast Wi-Fi, making the overall experience quite frustrating, which makes me again wish for the ability to remap the double press to something else. Spark, the standard voice recording app, also uses AI for note summarization and transcribing. Neither feature works offline, unfortunately. Spark records notes up to 30 minutes using Krono's dual microphones, and you can rename or export notes. Transcription quality is decent, and the speed is alright, but you can find much better solutions in the Google Play Store. What I like about Spark is that transcribed notes are not locked, and you can always type more to elaborate on your ideas, which is handy. Overall, I like that the Krono is not shoving AI down my throat, but to be honest, there is really not that much to shove. AI features here feel raw and need improvements to be more useful. Battery Life Like most E-Ink readers, the Krono has fantastic battery life. Even with a clock as a screensaver, its standby power consumption is incredibly low. And when in use, you can get weeks of reading on a single charge. Without the front light, my unit never sipped more than one or two percent of battery during a one-hour reading session. It was nice to see plenty of battery-related settings. You can limit charging at 80% to protect battery health long-term, check the number of charging cycles, manufacturing/first-time use date, battery health, and the maximum capacity. Additionally, the Krono lets you select what hardware remains enabled when sleeping. This lets you keep Wi-Fi and Bluetooth on (say, if you want to receive notifications, for some reason) and keep audio playing when locked. Turning these features off effectively eliminates any standby battery drain. I left my Krono sitting for 24 hours with a clock screensaver on, and it did not drop a single percent. The pretty big 3,950 mAh battery justifies the device's thickness and ensures you do not have to charge it for long periods. Speaking of charging, it is capped at only 10W, which is a bit disappointing, as getting such a big battery to 100% takes a notably long time in the era of super-fast charging smartphones. DuRoBo Moodi The Moodi is a standalone, optional accessory for your Krono. It is a wireless remote with two customizable buttons that you can use to flip pages, control media, or scroll webpages. The accessory connects via Bluetooth. Despite having a built-in rechargeable battery, it is extremely light. While the Moodi's shape and form factor is not what I would call particularly ergonomic, it is not uncomfortable to hold and use. The Moodi comes with six removable magnetic buttons with various smiley faces. Buttons sit securely, and they have nice-feeling, albeit a little loud, clicks. It is a cute touch that adds a little more fun and character to the device. There is also an accented power button and a single status LED. The latter displays charging status and connection mode. The Moodi supports three modes: Reading: Buttons work as volume buttons, allowing you to flip pages in the built-in reader or other apps that support page turning with volume buttons. Media: Buttons work as skip forward/backward, which is useful when listening to audiobooks, podcasts, or music. Scroll: The third mode lets you scroll pages in the web browser or any other application The Krono properly detects the Moodi and presents you with an on-screen guide when you connect it for the first time (it also displays the battery level). However, you can only change modes by holding both buttons for a few seconds. It is also worth noting that the Moodi works with other devices. I connected it to my iPhone and it let me adjust volume or control media playback. Sadly, the scroll did not work, so you cannot use it to waste time scrolling TikToks. Overall, the Moodi is a cute little accessory, which I can recommend for those who read a lot. It is very useful for remote page flipping when you do not want to burden your hands by holding the Krono all the time. I only wish DuRoBo included a lanyard for the built-in loop. As for the battery life, after using the Moodi for a few days, I only managed to drop several percent of its 90 mAh battery. Despite the small size, it is rated for weeks of use, which is pretty impressive. At $35.99, I cannot say the Moodi is a must-have accessory, but I see the appeal. I prefer using the Krono with its Smart Dial, as I rarely read for more than 40-60 minutes in one sitting. However, if you have a stand and like reading for long periods, the Moodi is the right thing to have. It is a bit more expensive than regular page flippers on Amazon, but it is on par with similar products from Kobo or BOOX. Plus, it has a little more fun to it with removable buttons and better integration into the Krono. Conclusion At the end of the day, DuRoBo Krono is a nice pocket-sized e-reader. Its software focuses on the main things without trying to be everything at once. The smart dial idea is unique and great, and I wish more manufacturers had something similar in their devices. The display is also good, with an even frontlight and "always-on" support. I did not notice any deal-breaking issues with the Krono. However, you can feel that the idea needs some improvements, such as a slightly stiffer dial in a more ergonomic location, perhaps a little more premium materials, and better software customization. I hope the company won't give up on the idea and improve the dial and ergonomics in the second generation. Buy DuRoBo Krono Black - $279.99 on Amazon Buy DuRoBo Krono White - $279.99 on Amazon Buy DuRoBo Moodi - $35.99 on Amazon As an Amazon Associate, we earn from qualifying purchases.
    • In what way is any of what I said incorrect? To install an update you need to close all browser instances, upping it from once a month to once a fortnight is an inconvenience for users. Particularly when updates don't offer functionality that users want (notably copilot). Security updates should come as they are needed, not on a release schedule
    • Dopamine 3.0.6 by Razvan Serea Dopamine is an awesome free audio player which tries to make organizing and listening to music as simple and pretty as possible. Dopamine has been designed for Windows 7, Windows 8.x and Windows 10 and plays mp3, ogg vorbis, flac, wma and m4a/aac music formats quite well. The best part? It's created by long-time Neowin member, Raphaël Godart. If you’re looking for a music player to handle a large music collection, you should definitely give Dopamine a try. Dopamine 3.0.6 changelog: Fixed Manually edited album covers are overwritten on the next collection refresh Fixed AppImage package not working on modern GNU/Linux distributions Deleting song from playlist sometimes fails Playback controls only work when clicking on upper half of the buttons It's unclear that files must be tagged with an external ReplayGain scanner (for example rsgain) before normalization can take effect. Change to Artist or Album tags is not reflected in the song list view nor in the Now Playing information ReplayGain issues Smart playlist filters ignore text containing accents or other special characters Some MP3 files trigger an "MPEG header not found" error due to a too-narrow initial MPEG header scan range Changed Updated the Vietnamese translation Download: Dopamine 3.0.6 | 122.0 MB (Open Source) Links: Home Page | Forum Discussion | Screenshot | Other OSes Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
    • Week One Done
      ssd21345 earned a badge
      Week One Done
    • Contributor
      MarkHughes4096 went up a rank
      Contributor
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      195
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      96
    5. 5
      Steven P.
      76
  • Tell a friend

    Love Neowin? Tell a friend!