Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: new machine - Win10 takes half an hour to boot
6 views
Skip to first unread message
Arlen Holder
Nov 8, 2020, 11:32:01 AM11/8/20
to
On Sun, 8 Nov 2020 11:23:10 +0100, Roland Schweiger wrote:
> There are soooooooooo many suggestions in Google and i tried the most
> sensible ones.
I saw what you tried, and I saw what others suggested.
o Below are some native Windows diagnostics I might also suggest you try.
(There are plenty more we can suggest - but what about these first?)
1. What I didn't see anyone suggest (maybe I missed it?) was a native
*Windows boot performance diagnostic test*.
o Win+R > gpedit.msc {control+shift+enter} <=== run as admin
Computer Configuration > Administrative Templates > System >
Troubleshooting and Diagnostics > Windows Boot Performance Diagnostics >
Configure Scenario Execution Level >
Change from (o)Not Configured; Change to: (o)Enabled
Change the "Scenario Execution Level" dropdown from:
[Detection & Troubleshooting Only]
Change the "Scenario Execution Level" dropdown from:
[Detection, Troubleshooting and Resolution]
[OK][File > Exit]
Check that this new "Diagnostic Policy Service" is now running.
o Win+R > services.msc > Diagnostic Policy Service
(The service status should be "Running".)
Reboot
o Win+R > Win+R > shutdown.exe /r /f /t 5 /c "Reboot in 5s!"
2. Another test is the *windows performance recorder user interface*:
o Win+R > wprui {control+shift+enter} <== run as admin
Press [OK] to get rid of the hot key nag screen
"This tool will gather information about the interaction of the programs
and hardware running on this computer for analysis."
Change "Performance scenario" from [General] to [Boot] or [Fast Startup]
Set the additional levels of triage as desired & then click [Start].
Change the file name, if desired:
C:\Users\arlen\Documents\WPR Files\ARLEN.11-08-2020.08-24-09.etl
Description:
This is a test using Win+R > wprui
Click [Save]
3. Yet another Windows test is the *bare minimum boot diagnostic test*.
If the bare-minimum boot is fast, then, one by one, you can re-enable
services to see which, if any, are holding up the next boot process.
o Win+R > services.msc > action > export list > Text
(save the list to an editable text or csv file)
o Win+R > msconfig > General > Startup selection
(_)Normal startup
(o)Diagnostic startup
(_)Selective startup
4. Another test you can try is "*driver verifier*", which allows you to
turn off drivers, once by one, or en masse, for a diagnostic boot.
o Win+R > verifier
<https://i.postimg.cc/vTnqk9GC/bsod100.jpg>
Configure that Windows Driver Verifier Manager
o Create standard settings > Next
o Automatically select all drivers installed on this computer > Finish
o Win+R > shutdown.exe /r /f /t 5 /c "Reboot in 5 seconds!"
There are plenty more I could suggest, but what do you think of those?
--
For gory details on each of these Windows tools, see this recent thread:
o Windows 10 BSOD indicates a hardware problem - but what hardware is the problem?
<https://alt.comp.os.windows-10.narkive.com/oL7PTNKu/windows-10-bsod-indicates-a-hardware-problem-but-what-hardware-is-the-problem>
<http://www.pcbanter.net/showthread.php?t=1110105>
<https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/u0ay9h777Wg>
> There are soooooooooo many suggestions in Google and i tried the most
> sensible ones.
I saw what you tried, and I saw what others suggested.
o Below are some native Windows diagnostics I might also suggest you try.
(There are plenty more we can suggest - but what about these first?)
1. What I didn't see anyone suggest (maybe I missed it?) was a native
*Windows boot performance diagnostic test*.
o Win+R > gpedit.msc {control+shift+enter} <=== run as admin
Computer Configuration > Administrative Templates > System >
Troubleshooting and Diagnostics > Windows Boot Performance Diagnostics >
Configure Scenario Execution Level >
Change from (o)Not Configured; Change to: (o)Enabled
Change the "Scenario Execution Level" dropdown from:
[Detection & Troubleshooting Only]
Change the "Scenario Execution Level" dropdown from:
[Detection, Troubleshooting and Resolution]
[OK][File > Exit]
Check that this new "Diagnostic Policy Service" is now running.
o Win+R > services.msc > Diagnostic Policy Service
(The service status should be "Running".)
Reboot
o Win+R > Win+R > shutdown.exe /r /f /t 5 /c "Reboot in 5s!"
2. Another test is the *windows performance recorder user interface*:
o Win+R > wprui {control+shift+enter} <== run as admin
Press [OK] to get rid of the hot key nag screen
"This tool will gather information about the interaction of the programs
and hardware running on this computer for analysis."
Change "Performance scenario" from [General] to [Boot] or [Fast Startup]
Set the additional levels of triage as desired & then click [Start].
Change the file name, if desired:
C:\Users\arlen\Documents\WPR Files\ARLEN.11-08-2020.08-24-09.etl
Description:
This is a test using Win+R > wprui
Click [Save]
3. Yet another Windows test is the *bare minimum boot diagnostic test*.
If the bare-minimum boot is fast, then, one by one, you can re-enable
services to see which, if any, are holding up the next boot process.
o Win+R > services.msc > action > export list > Text
(save the list to an editable text or csv file)
o Win+R > msconfig > General > Startup selection
(_)Normal startup
(o)Diagnostic startup
(_)Selective startup
4. Another test you can try is "*driver verifier*", which allows you to
turn off drivers, once by one, or en masse, for a diagnostic boot.
o Win+R > verifier
<https://i.postimg.cc/vTnqk9GC/bsod100.jpg>
Configure that Windows Driver Verifier Manager
o Create standard settings > Next
o Automatically select all drivers installed on this computer > Finish
o Win+R > shutdown.exe /r /f /t 5 /c "Reboot in 5 seconds!"
There are plenty more I could suggest, but what do you think of those?
--
For gory details on each of these Windows tools, see this recent thread:
o Windows 10 BSOD indicates a hardware problem - but what hardware is the problem?
<https://alt.comp.os.windows-10.narkive.com/oL7PTNKu/windows-10-bsod-indicates-a-hardware-problem-but-what-hardware-is-the-problem>
<http://www.pcbanter.net/showthread.php?t=1110105>
<https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/u0ay9h777Wg>
Arlen Holder
Nov 8, 2020, 1:44:15 PM11/8/20
to
On Sun, 08 Nov 2020 16:06:30 +0000, Jim H wrote:
> If I were you I'd check what programs run by default upon startup and
> disable them all
That reminds me I didn't add these shortcut commands to my prior post:
o Win+R > ms-settings:startupapps
Some day I'll try to figure out all the possible startup locations.
o For now, see also these related startup-programs diagnostic commands.
o Win+R > shell:startup
[opens %appdata%\Microsoft\Windows\Start Menu\Programs\Startup]
[opens C:\Users\%username%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup]
o Win+R > shell:common startup
[opens C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp]
Note: Move shortcuts to the "shell:appsfolder" for safekeeping:
o Win+R > shell:appsfolder
o Win+R > taskmgr > Startup (tab) > Enable/Disable (rightclick)
o Win+R > taskschd.msc > Task Scheduler Library > Enable/Disable (rightclick)
o Win+R > regjump HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
o Win+R > regjump HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
<https://docs.microsoft.com/en-us/sysinternals/downloads/regjump>
<https://download.sysinternals.com/files/RegJump.zip>
Name: RegJump.zip
Size: 61583 bytes (60 KiB)
SHA256: 53DBC149D0BC0BF464A9970A14A1650FE0D2CA311DD80829C09589D0FE150EEC
o Win+R > autoruns (you need to add a key in AppPaths for this to work here)
[HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths]
<https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns>
<https://download.sysinternals.com/files/Autoruns.zip>
Name: Autoruns.zip
Size: 2670815 bytes (2608 KiB)
SHA256: 9B34804FE89BF35FF5400B39FE56DC4E6F191E850DFA4B5C4EB915D389233E20
--
Let us know if I missed any Windows 10 startup-related diagnostic commands.
> If I were you I'd check what programs run by default upon startup and
> disable them all
That reminds me I didn't add these shortcut commands to my prior post:
o Win+R > ms-settings:startupapps
Some day I'll try to figure out all the possible startup locations.
o For now, see also these related startup-programs diagnostic commands.
o Win+R > shell:startup
[opens %appdata%\Microsoft\Windows\Start Menu\Programs\Startup]
[opens C:\Users\%username%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup]
o Win+R > shell:common startup
[opens C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp]
Note: Move shortcuts to the "shell:appsfolder" for safekeeping:
o Win+R > shell:appsfolder
o Win+R > taskmgr > Startup (tab) > Enable/Disable (rightclick)
o Win+R > taskschd.msc > Task Scheduler Library > Enable/Disable (rightclick)
o Win+R > regjump HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
o Win+R > regjump HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
<https://docs.microsoft.com/en-us/sysinternals/downloads/regjump>
<https://download.sysinternals.com/files/RegJump.zip>
Name: RegJump.zip
Size: 61583 bytes (60 KiB)
SHA256: 53DBC149D0BC0BF464A9970A14A1650FE0D2CA311DD80829C09589D0FE150EEC
o Win+R > autoruns (you need to add a key in AppPaths for this to work here)
[HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths]
<https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns>
<https://download.sysinternals.com/files/Autoruns.zip>
Name: Autoruns.zip
Size: 2670815 bytes (2608 KiB)
SHA256: 9B34804FE89BF35FF5400B39FE56DC4E6F191E850DFA4B5C4EB915D389233E20
--
Let us know if I missed any Windows 10 startup-related diagnostic commands.
Arlen Holder
Nov 8, 2020, 3:39:01 PM11/8/20
to
On Sun, 8 Nov 2020 13:28:38 -0600, Rene Lamontagne wrote:
> I think this was mentioned already, disconnect network cable and try
> that, maybe the PC is hunting for a DHCP or something.
One trick I use to ensure my computer _never_ boots to the network
o Is simply to never set the Gateway in the network control panel
Win+R > ncpa.cpl > Rightclick on Ethernet/Wi-Fi applet > Properties
Select [Internet Protocol Version 4] > [Properties]
Default gateway === <make sure this is blank>
When my machine boots, the gateway to the router isn't set.
o When I feel like setting the gateway to get back on the network:
Win+R > network (which turns the gateway back on)
The commands to run are simply:
o Detach from the network: route delete 0.0.0.0 %defgw%
o Connect to the network: route add 0.0.0.0 mask 0.0.0.0 %defgw%
Where "%defgw%" is your default gateway (e.g., 192.168.0.1)
See also:
o LiquidVPN free killswitch batch file
<https://www.liquidvpn.com/vpn-kill-switches/>
--
See also:
o Tutorial to add a freeware killswitch which blocks software installations
from phoning home during or after the initial install process
<https://groups.google.com/forum/#!topic/alt.comp.freeware/5VPbErk7PBQ>
> I think this was mentioned already, disconnect network cable and try
> that, maybe the PC is hunting for a DHCP or something.
One trick I use to ensure my computer _never_ boots to the network
o Is simply to never set the Gateway in the network control panel
Win+R > ncpa.cpl > Rightclick on Ethernet/Wi-Fi applet > Properties
Select [Internet Protocol Version 4] > [Properties]
Default gateway === <make sure this is blank>
When my machine boots, the gateway to the router isn't set.
o When I feel like setting the gateway to get back on the network:
Win+R > network (which turns the gateway back on)
The commands to run are simply:
o Detach from the network: route delete 0.0.0.0 %defgw%
o Connect to the network: route add 0.0.0.0 mask 0.0.0.0 %defgw%
Where "%defgw%" is your default gateway (e.g., 192.168.0.1)
See also:
o LiquidVPN free killswitch batch file
<https://www.liquidvpn.com/vpn-kill-switches/>
--
See also:
o Tutorial to add a freeware killswitch which blocks software installations
from phoning home during or after the initial install process
<https://groups.google.com/forum/#!topic/alt.comp.freeware/5VPbErk7PBQ>
Arlen Holder
Nov 8, 2020, 5:26:41 PM11/8/20
to
On Sun, 8 Nov 2020 12:47:12 -0600, Mark Lloyd wrote:
> One cause of slow booting is waiting for DHCP over an unused network
> interface. I've had that happen a few times. If it's unused you might
> want to remove the driver (or at least set it for static IP).
Hi Mark Lloyd,
Do you know if this simple trick saves that network-seek time you speak of?
o Here is a simple trick to always boot off the network (sans gateway)
<https://groups.google.com/d/msg/alt.comp.microsoft.windows/c8VPYpZAyII/GpR0hOLUCgAJ>
I know that simple trick prevents the machine from booting to the network.
But I'm not sure if that trick of deleting the gateway prevents what you
speak of from happening from taking extra time.
It "seems" to work though; but I'm not sure what goes on under the covers.
o Do you know if deleting the gateway saves network-seek time you speak of?
> One cause of slow booting is waiting for DHCP over an unused network
> interface. I've had that happen a few times. If it's unused you might
> want to remove the driver (or at least set it for static IP).
Hi Mark Lloyd,
Do you know if this simple trick saves that network-seek time you speak of?
o Here is a simple trick to always boot off the network (sans gateway)
<https://groups.google.com/d/msg/alt.comp.microsoft.windows/c8VPYpZAyII/GpR0hOLUCgAJ>
I know that simple trick prevents the machine from booting to the network.
But I'm not sure if that trick of deleting the gateway prevents what you
speak of from happening from taking extra time.
It "seems" to work though; but I'm not sure what goes on under the covers.
o Do you know if deleting the gateway saves network-seek time you speak of?
--
See also:
o Tutorial to add a freeware killswitch which blocks software installations from phoning home during or after the initial install process
<https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/c8VPYpZAyII>
See also:
o Tutorial to add a freeware killswitch which blocks software installations from phoning home during or after the initial install process
Arlen Holder
Nov 8, 2020, 8:04:12 PM11/8/20
to
On Sun, 8 Nov 2020 21:30:39 +0100, Roland Schweiger wrote:
> sorry but i was refering explicitly to a WINDOWS problem.
I don't know if anyone uses "hijackthis" anymore, but I just tried it and
it seems to list a bunch of things for the user which "might" slow down a
boot.
If needed, here's my log file, but I'm not sure it's all that useful.
HiJackThis
Installer: x:\installer\cleaner\vaccine\hijackthis.lnk
Installed: C:\app\cleaner\vaccine\hijackthis\.
MenuFoldr: C:\menu\cleaner\vaccine\hijackthis.lnk
TaskMenu: Taskbar > menu > cleaner > vaccine > hijackthis
Official (discontinued):
<https://sourceforge.net/projects/hjt/>
<https://netactuate.dl.sourceforge.net/project/hjt/2.0.5%20beta/HijackThis.exe>
Name: HijackThis.exe
Size: 388608 bytes (379 KiB)
CRC32: E1BF007A
CRC64: 0C0BA06F639D3D2D
SHA256: 9DA5A899B9D55E1D43718EC0AD6368F9E9EF0242A4E88CD5DDB2CC6D7BFA5FB3
SHA1: 2623749CDB27887F6746ACDEE7E8065475F8B541
BLAKE2sp: 5687ACB49C5CA17B93E23BD96DC9B2FB38D28ECF2C23CD7197AF5685BD2273CE
Unofficial Fork:
<https://github.com/dragokas/hijackthis/>
<https://dragokas.com/tools/HiJackThis.zip>
Name: HiJackThis.zip
Size: 2045714 bytes (1997 KiB)
CRC32: E0FBB507
CRC64: B19570065AB0DCB0
SHA256: D296107876CD781A6EE0FDEF1294951027781A8E1DF734FE3509B4D52781D10F
SHA1: E7DC59E840087684FA8E30B9B3777D14730EE672
BLAKE2sp: 5D10EA20534345B8C524523F9F630A3D9E6F7319F410EA9B40B50440D055C845
Extract to
Name: HiJackThis.exe
Size: 6875040 bytes (6713 KiB)
CRC32: 1457B35D
CRC64: 1D73526225C2F251
SHA256: 267EA49C9ECED989AD8A0481FF6D60D71FA93B18312E79F1707889EC88850739
SHA1: BC0D29BA17F4479796E1A0C6539F79D96D86569A
BLAKE2sp: 343D5553BB37211C7D7AC0BD587C5F75F12607D1E368520797DA29043B9BBB5B
C:\installer\os\hijackthis\CheckBrowsersLNK.zip
Name: CheckBrowsersLNK.zip
Size: 594365 bytes (580 KiB)
CRC32: 9326118F
CRC64: 5BEDDC93BB915C08
SHA256: 1030E3A282656D6C9EE5E7F79DB880C977A0A5679990245B0BB3F963768BEA94
SHA1: C571FF5397B07D7F87741E4358C4F5AAD3A93C9E
BLAKE2sp: 8F465296FD1E1D26DB815C48241D80F2B0B925293B9323FB4B7E910A15BD7A38
Misc tools
o Itty Bitty Process Manager v1.07
o Hosts file manager
o Delete a file on reboot
o Delete a Windows service
o ADS Spy (scan for hidden file streams)
o Uninstall Manager
o Registry Keys Unlocker
o Digital Signal Checker
o Identify infected shortcuts which cause unwanted ads in browsers
etc.
Checking 58 autostart groups
o Running processes
o Task scheduler jobs
o Exploreer.exe clones
o Browser helper objects
o IE toolbars
o On-reboot actions
o Shell commands
o Services
o Driver filters
o winlogon autostarts
o LSA packages
o Contextmenu handlers
o Registry run keys
o Users on this computer
o Winsock LSPs
o Hijack points
o Protection & disabled items
etc.
> sorry but i was refering explicitly to a WINDOWS problem.
I don't know if anyone uses "hijackthis" anymore, but I just tried it and
it seems to list a bunch of things for the user which "might" slow down a
boot.
If needed, here's my log file, but I'm not sure it's all that useful.
HiJackThis
Installer: x:\installer\cleaner\vaccine\hijackthis.lnk
Installed: C:\app\cleaner\vaccine\hijackthis\.
MenuFoldr: C:\menu\cleaner\vaccine\hijackthis.lnk
TaskMenu: Taskbar > menu > cleaner > vaccine > hijackthis
Official (discontinued):
<https://sourceforge.net/projects/hjt/>
<https://netactuate.dl.sourceforge.net/project/hjt/2.0.5%20beta/HijackThis.exe>
Name: HijackThis.exe
Size: 388608 bytes (379 KiB)
CRC32: E1BF007A
CRC64: 0C0BA06F639D3D2D
SHA256: 9DA5A899B9D55E1D43718EC0AD6368F9E9EF0242A4E88CD5DDB2CC6D7BFA5FB3
SHA1: 2623749CDB27887F6746ACDEE7E8065475F8B541
BLAKE2sp: 5687ACB49C5CA17B93E23BD96DC9B2FB38D28ECF2C23CD7197AF5685BD2273CE
Unofficial Fork:
<https://github.com/dragokas/hijackthis/>
<https://dragokas.com/tools/HiJackThis.zip>
Name: HiJackThis.zip
Size: 2045714 bytes (1997 KiB)
CRC32: E0FBB507
CRC64: B19570065AB0DCB0
SHA256: D296107876CD781A6EE0FDEF1294951027781A8E1DF734FE3509B4D52781D10F
SHA1: E7DC59E840087684FA8E30B9B3777D14730EE672
BLAKE2sp: 5D10EA20534345B8C524523F9F630A3D9E6F7319F410EA9B40B50440D055C845
Extract to
Name: HiJackThis.exe
Size: 6875040 bytes (6713 KiB)
CRC32: 1457B35D
CRC64: 1D73526225C2F251
SHA256: 267EA49C9ECED989AD8A0481FF6D60D71FA93B18312E79F1707889EC88850739
SHA1: BC0D29BA17F4479796E1A0C6539F79D96D86569A
BLAKE2sp: 343D5553BB37211C7D7AC0BD587C5F75F12607D1E368520797DA29043B9BBB5B
C:\installer\os\hijackthis\CheckBrowsersLNK.zip
Name: CheckBrowsersLNK.zip
Size: 594365 bytes (580 KiB)
CRC32: 9326118F
CRC64: 5BEDDC93BB915C08
SHA256: 1030E3A282656D6C9EE5E7F79DB880C977A0A5679990245B0BB3F963768BEA94
SHA1: C571FF5397B07D7F87741E4358C4F5AAD3A93C9E
BLAKE2sp: 8F465296FD1E1D26DB815C48241D80F2B0B925293B9323FB4B7E910A15BD7A38
Misc tools
o Itty Bitty Process Manager v1.07
o Hosts file manager
o Delete a file on reboot
o Delete a Windows service
o ADS Spy (scan for hidden file streams)
o Uninstall Manager
o Registry Keys Unlocker
o Digital Signal Checker
o Identify infected shortcuts which cause unwanted ads in browsers
etc.
Checking 58 autostart groups
o Running processes
o Task scheduler jobs
o Exploreer.exe clones
o Browser helper objects
o IE toolbars
o On-reboot actions
o Shell commands
o Services
o Driver filters
o winlogon autostarts
o LSA packages
o Contextmenu handlers
o Registry run keys
o Users on this computer
o Winsock LSPs
o Hijack points
o Protection & disabled items
etc.
Arlen Holder
Nov 9, 2020, 7:27:27 PM11/9/20
to
On Mon, 9 Nov 2020 23:10:19 +0100, Roland Schweiger wrote:
> i cannot tell when the problems started. i had also suspected video
> drivers and (re)installed the ones from ASUS (they are also Intel but
> maybe somehow modified) and then i tried remiving them and let windows
> detect ... no change at all. The video drivers seem to be ok.
Two hints on installing the _latest_ drivers (including video drivers)...
1. Windows won't, and,
<https://i.postimg.cc/2862Ztvf/driver01.jpg>
2. Dumo helps.
<https://i.postimg.cc/fWCMVXc6/driver25.jpg>
--
For gory details, please see:
o Tutorial: How to update a driver that Windows just doesn't want to update
<https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/a23fY9CM6rY>
> i cannot tell when the problems started. i had also suspected video
> drivers and (re)installed the ones from ASUS (they are also Intel but
> maybe somehow modified) and then i tried remiving them and let windows
> detect ... no change at all. The video drivers seem to be ok.
Two hints on installing the _latest_ drivers (including video drivers)...
1. Windows won't, and,
<https://i.postimg.cc/2862Ztvf/driver01.jpg>
2. Dumo helps.
<https://i.postimg.cc/fWCMVXc6/driver25.jpg>
--
For gory details, please see:
o Tutorial: How to update a driver that Windows just doesn't want to update
<https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/a23fY9CM6rY>
Arlen Holder
Nov 9, 2020, 7:31:11 PM11/9/20
to
On Tue, 10 Nov 2020 00:44:01 +0100, Roland Schweiger wrote:
> I feel so stupid - doing some programming with VisualStudio (actually
> now with AnddroidStudio and creating some little apps for Android, just
> to learn better Java) and then being UNABLE to resolve such a windows
> problem or to properly use some boot tracing :-(
Just an aside regarding your comment about Android Studio above...
I wrote up every step to the creation of your first 20 or so apps...
If you want the gory details, I wrote step-by-step tutorials here...
Please see:
o Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
<https://groups.google.com/forum/#!topic/alt.comp.freeware/qEqThtRwZAg>
> I feel so stupid - doing some programming with VisualStudio (actually
> now with AnddroidStudio and creating some little apps for Android, just
> to learn better Java) and then being UNABLE to resolve such a windows
> problem or to properly use some boot tracing :-(
Just an aside regarding your comment about Android Studio above...
I wrote up every step to the creation of your first 20 or so apps...
If you want the gory details, I wrote step-by-step tutorials here...
Please see:
o Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
<https://groups.google.com/forum/#!topic/alt.comp.freeware/qEqThtRwZAg>
Roland Schweiger
Nov 10, 2020, 9:44:51 AM11/10/20
to
Am 10.11.2020 um 01:31 schrieb Arlen Holder:
> Just an aside regarding your comment about Android Studio above...
>
> I wrote up every step to the creation of your first 20 or so apps...
>
> If you want the gory details, I wrote step-by-step tutorials here...
>
> Please see:
> o Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
> <https://groups.google.com/forum/#!topic/alt.comp.freeware/qEqThtRwZAg>
>
Thanks and i will have a look into it.
> Just an aside regarding your comment about Android Studio above...
>
> I wrote up every step to the creation of your first 20 or so apps...
>
> If you want the gory details, I wrote step-by-step tutorials here...
>
> Please see:
> o Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)
> <https://groups.google.com/forum/#!topic/alt.comp.freeware/qEqThtRwZAg>
>
Last year i just wanted to know (after having paused programming for
about 30 years ... i am a commodore64 kid) i wanted to know if i could
learn some Java and create an android app from first line to publication
in play store.
if you are interested in running and test-reporting:
https://play.google.com/store/apps/details?id=c.barohaus
It's nothing special. it displays a weather-house and checks if the
device has an atmospheric air-pressure sensor.
if it has one, it will speak out the air pressure in hektopascal when
pressing the "air pressure" button.
If there is no sensor, it will tell you. I also experimented with
internationalization. The UI + layout of the activity is in German,
English or French according to System Settings.if any other language, it
will "fall back" to English.
though so simple ... it took me a while and i still have problems with
object-orientation ... i still find myself thinking in machinelanguage
terms like in commodore time. But never the less, AndroidStudio is fun.
0 new messages