i actually saw this a few days ago when googling to see if its possible to do graphics in native mode still cursed to see a Linux terminal with the windows native mode font
This is pretty cool! This makes me wonder if it’s possible to make a driver that runs after a bugcheck that saves the current work and reloads the windows processes allowing for almost instant restart or something.
@-ルナール- lmao oh so true...I've used Linux as primary OS for all but gaming for years and can count the ones I've seen on a single hand...and most were me experimenting and learning, never through normal use like Windows. Was just saying the two are the same fundamentally
hi ntdev, I am a big fan of your builds, it so happened that I have a not very powerful and old laptop, and just your tiny10 build was a salvation for me. you recently released an updated version, but only 32-bit, its problem is that it does not fully tell the potential of the processor, I think this is due to the fact that it has only 32 bits. I tested on the old version (2209) but 64-bit, in cpu-z it turned out 400 points, and in the new 32-bit only 180, which is very small. and in itself, the behavior of windows has become a little sluggish, which makes me very sad. I would like to ask you to release a 64-bit version on build 2303, I hope you will notice my message. thank you for your hard work
This is impressive. I wonder if it'd be possible to build an EFI version, and potentially even bootstrap into a linux kernel directly, I don't know if Windows has anything like kexec or not, or if some things already beint initialized would break that
Hey! The hw being initialized removes direct bootstrap without a form of kexec iirc at least on vanilla Linux as the hardware wouldn’t be in the expected state and some things do not take kindly to being re-inited
Hear me out now. What if you had like super stripped Linux that runs KVM with Windows with gpu passthrough. So you your PC boots linux, that loads windows, but then somehow overlay linux apps so that you can access them too for privacy.
On my old Windows 8.0 laptop I was getting Windows 7-like blue screens very frequently. Although Windows 8.0 on my PC didn't seem to get blue screens at all and, when called manually (Stopping csrss.exe) it showed the all-new ":(" Blue screen.
How is this possible? You can't run executables during Windows blue screen. While a BSOD has occurred, the entire system/kernel is shut down, and all it does is collects detailed information (sometimes it does not). To my knowledge, even drivers no longer work while a blue screen has occurred
As mentioned in the video, the Windows kernel's bugcheck (BSoD) has a callback ability and I'm assuming that this RISC-V emu is not a regular .exe file, but rather a bootable, OS-independent binary executable.
Well it's basically native mode of windows. To better understand that, Native mode is the mode before csrss.exe starts. That's why a windows instance can't exist without it.
You can run some executable in the bsod but they have to be specificly made for that purpose. When you run these executables in normal windows mode an error will say 'This program cannot be run in Win32 mode'
As long as it's running on NTFS, with a big enough hard drive, you can do upgrade installs from XP to Vista, then 7, then 10. It does work, too. People have started with MS-DOS and Windows 1, and done upgrade installs with every version all the way through to 10.
@@Acorn_Anomaly well you need more modern cpu for Windows 8+ since it will not run without certain features not found in old cpu (we are talking like Pentium 3 here though)
@@NTDEV you can use capslock but then it's really inconvenient switching it on and off Edit: yes the driver is really that awkward to make use of capslock as shift
@@rodrigo1593_ be aware though. BSODs exist for a (very important) reason. BSODs are what Windows does in case something goes *very* wrong that could potentially corrupt system memory, and even data. Without BSODs, you're opening yourself to play a risky game of data corruption.
@@Bomkz its dumb to say that bc you will still lose data or get corrupted files if the system shutdowns unexpectedly or get an bsod while doing something or hdd is working rn man
@@rodrigo1593_ only in SSDs, SSDs have a buffer that immediately gets flushed when power is lost, and mostly just SSDs with cache in them. while hard drives would get data corruption, it would to a lesser degree, as in, 3 or 4 files affected during data transfer, while SSDs it's much bigger. Also, with the right circumstances, you might end up nuking your whole data.
If you are talking about porting windows, in short form, no. CPU architectures are different. Technically you can run ARM version of Windows (the version used by Microsoft Surface Laptops) but it is not a good idea. Even if the naming is same, it is different from the version you used to. You don't have practical reason to do it.
![Tee Grizzley - Blow for Blow (feat. J. Cole) [Official Video]](http://i.ytimg.com/vi/wNLN5xsx5dc/mqdefault.jpg)
Hey! Thank you for checking out the project and for your kind words. It means alot to me.
Remember to unpin the comment
@@_lun4r_stuuupid
@@_lun4r_goddammit, it's the owner of the project who commented, also quit annoying ppl to unpin, you're only making yourself look bad, not others
@@_lun4r_why
i actually saw this a few days ago when googling to see if its possible to do graphics in native mode
still cursed to see a Linux terminal with the windows native mode font
This is pretty cool! This makes me wonder if it’s possible to make a driver that runs after a bugcheck that saves the current work and reloads the windows processes allowing for almost instant restart or something.
Factual, Linux doesn't just greet you with a bluescreen like Windows
Linux just do a crash dump black and white
I've seem it sometimes.
Yeah a bluescreen is just a glorified kernel panic, Linux has those too just a black screen grey text like they said above
@@templet45 kernel panic doesn't happen as often as a bluescreen though
@-ルナール- lmao oh so true...I've used Linux as primary OS for all but gaming for years and can count the ones I've seen on a single hand...and most were me experimenting and learning, never through normal use like Windows. Was just saying the two are the same fundamentally
The hypercam2 video format is unironically the best and needs a comeback
hi ntdev, I am a big fan of your builds, it so happened that I have a not very powerful and old laptop, and just your tiny10 build was a salvation for me. you recently released an updated version, but only 32-bit, its problem is that it does not fully tell the potential of the processor, I think this is due to the fact that it has only 32 bits. I tested on the old version (2209) but 64-bit, in cpu-z it turned out 400 points, and in the new 32-bit only 180, which is very small. and in itself, the behavior of windows has become a little sluggish, which makes me very sad. I would like to ask you to release a 64-bit version on build 2303, I hope you will notice my message. thank you for your hard work
This is impressive. I wonder if it'd be possible to build an EFI version, and potentially even bootstrap into a linux kernel directly, I don't know if Windows has anything like kexec or not, or if some things already beint initialized would break that
Hey! The hw being initialized removes direct bootstrap without a form of kexec iirc at least on vanilla Linux as the hardware wouldn’t be in the expected state and some things do not take kindly to being re-inited
Hear me out now. What if you had like super stripped Linux that runs KVM with Windows with gpu passthrough. So you your PC boots linux, that loads windows, but then somehow overlay linux apps so that you can access them too for privacy.
thats called proxmox virtualization
Is it possible to return to good old text-based BSOD (which still must be present)? Or "SOS" boot mode (which also must be present)?
Well, since this is possible, someone could write a driver that displays the classic blue screen
it is possible since it uses the old text for rendering (0:39), would need to be callbacked after the new bsod though
On my old Windows 8.0 laptop I was getting Windows 7-like blue screens very frequently. Although Windows 8.0 on my PC didn't seem to get blue screens at all and, when called manually (Stopping csrss.exe) it showed the all-new ":(" Blue screen.
Damn your content does never stop to amaze me.
Hello bud when u will do a part 2 to of updating windows 8.1 to windows 7?
me who switched to linux on my lap~~top~~ a few days ago
Is it possible to install tiny11 on a thumbstick? like not the installation versionn but the full one
Yes with an official way called WindowsToGo, it can work with NT versions from 8/8.1, 10 and 11
How is this possible? You can't run executables during Windows blue screen. While a BSOD has occurred, the entire system/kernel is shut down, and all it does is collects detailed information (sometimes it does not). To my knowledge, even drivers no longer work while a blue screen has occurred
As mentioned in the video, the Windows kernel's bugcheck (BSoD) has a callback ability and I'm assuming that this RISC-V emu is not a regular .exe file, but rather a bootable, OS-independent binary executable.
Well it's basically native mode of windows. To better understand that, Native mode is the mode before csrss.exe starts. That's why a windows instance can't exist without it.
@@simplyhexagon correct, it is not an executable, but rather a .sys kernel level (ring 0) driver.
Why is it a RISC-V emu? Linux runs natively on x86.
You can run some executable in the bsod but they have to be specificly made for that purpose. When you run these executables in normal windows mode an error will say 'This program cannot be run in Win32 mode'
Wait so it boots linux without needing for the computer reboots just like instantly???!
No. It runs an emulator that boots Linux.
Windows: why is the bluescreen using a gigabyte of ram?
Someone could probably make it play bad apple in the bsod
Can you try to upgrade Windows XP to Windows 10 using a normal installer method (if its even possible) ?
As long as it's running on NTFS, with a big enough hard drive, you can do upgrade installs from XP to Vista, then 7, then 10.
It does work, too. People have started with MS-DOS and Windows 1, and done upgrade installs with every version all the way through to 10.
@@Acorn_Anomaly well you need more modern cpu for Windows 8+ since it will not run without certain features not found in old cpu (we are talking like Pentium 3 here though)
what the heck
Holy shit that's genius lol
Why it needs to be riscv emulator? No x86 native?
you can start lines in sh with # for them to be comments btw
Yes, but you can't do shift+3 to type #
@@NTDEV ohh so that's why lol mb
@@NTDEV you can use capslock but then it's really inconvenient switching it on and off
Edit: yes the driver is really that awkward to make use of capslock as shift
Tiny 10 or 11
Tiny 10 or 11
can that developer make a bluescreen bypass for windows 7 onwards?
NoMoreBugCheck should work on Windows 7. Probably one would have to rebuild the driver targeting Windows 7.
@@nsg650 i see i see... thanks !!!
@@rodrigo1593_ be aware though. BSODs exist for a (very important) reason. BSODs are what Windows does in case something goes *very* wrong that could potentially corrupt system memory, and even data. Without BSODs, you're opening yourself to play a risky game of data corruption.
@@Bomkz its dumb to say that bc you will still lose data or get corrupted files if the system shutdowns unexpectedly or get an bsod while doing something or hdd is working rn man
@@rodrigo1593_ only in SSDs, SSDs have a buffer that immediately gets flushed when power is lost, and mostly just SSDs with cache in them. while hard drives would get data corruption, it would to a lesser degree, as in, 3 or 4 files affected during data transfer, while SSDs it's much bigger.
Also, with the right circumstances, you might end up nuking your whole data.
Isit possible a port for Android device
Absolutly not. Windows is Windows and Android is Android (heavily modified old linux kernel).
If you are talking about porting windows, in short form, no. CPU architectures are different.
Technically you can run ARM version of Windows (the version used by Microsoft Surface Laptops) but it is not a good idea. Even if the naming is same, it is different from the version you used to. You don't have practical reason to do it.
holyy
This demo is useless. The music is grating and distracting. No real functionality is displayed.