Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - MarkW

Pages: [1]
1
 :artist:
Shane, your responses were definitely worth bringing it to your attention.  lol  My first impression is that Microsoft is trying to do a fake-out to the general Windows using community and make everyone think it is an entirely different operating system than Win 8 is.  (Trying to hide their shame.)
The number 10 was a surprise to me as well.  Microsoft must still be feeling the sting from Vista.  I had read the same articles that you had about naming the next release as v8.x or 9.  They were talking about making it free, at some level, as well.  Maybe they needed to go to 10 to dispel that idea. To me it truly looks like a more viable Windows 8.x than a new version of Windows.

I know your tools can't really support the new O/S until it's final incarnation is released.  No problem.  I thought you'd enjoy the heads-up and looking through the logs from running the Windows Repair app on it.  I had nothing to lose but time.  I was glad that I was able to note a couple things for you.  Since the download and licensing for the pre-release is free, I can re-image that virtual machine at will, or with VMware just create a recovery point.

When MS were releasing Windows 8 workstation / Windows 2012 server, articles kept referring to 8 or 2012 as the server version, interchangeably.  It was annoying.  Almost as annoying as Microsoft Press 'NOT' providing self-training kit set of books.  I do far better learning a new operating system by reading and then doing exercises to experience the product more closely and become conversant with it. 
I have not read far enough yet to say that all versions of the next release will officially be known as Windows 10 or not.

I firmly believe that server administrators need a different interface than a desktop user does.  And that most home users need a simpler interface than a employee at a company does for the work they do on the computer.  A smartphone is in no way the same as a network managed domain or database server.  I don't know how much MS has come to grips with that realization for this next Windows release.  My guess is : probably not enough.  But, so far my experience with the Win10 pre-release has been better than my time with Windows 8 (or 2012).  They have done quite a few things with the interface better this time. The initial discoveries are the most challenging: what did they do with the Control Panel shortcut?  Why don't I see my loaded CD drive from explorer? How could I add a silly 'Metro' block next to the Menu and so on.  (They are easy to delete.)
Their default color-schemes are a little scary: pastels. 

Time will tell.  The article states that they don't plan to release a final version until later next year.
Let me know if there is anything you'd like your software users to keep an eye out for, with this latest version of Windows as it matures over the next year.  If any other big thing jumps out at me while using it, I will pass it on to you.

Mark

2
Hi Shane,

Other than some basic looking around, one of the first things I did on the Windows 10 pre-release was run Running Windows Repair (All in One) v2.92, for the fun of it.
I seems to have worked well, but the O/S version in the results windows of Windows Repair was listed as 6.3.9600  instead of what running 'ver' at the command prompt which showed: 6.4.9841.
I wouldn't run it on my main computer since it is a pre-release, but I did install and run it on a virtual workstation.
http://windows.microsoft.com/en-us/windows/preview-download?ocid=tp_site_downloadpage

From what I initially see Windows 10 is really just a service pack release to Windows 8, though there are some productivity improvements.  Many of the improvements were the ones we were all calling for.

I have attached the logs for that first run, in case any of it could be of value to you.

Mark

3
 :smiley:
v2.8.6 has resolved these issues on the older / slower machines.   
I even gave it a shot on an old emergency laptop: Pentium III 1.20Ghz, 785mb RAM, XP Pro Sp3, 40GB IDE ATA/100 5400 rpm hard drive.

Thank you Shane.

Mark

4
Shane,
I just ran v.2.8.5 on two machines, for confirmation after the first result was unexpected.  VirtualBox is working fine, but the infinite 'Application Data' directory has returned for All Users profile directory.  I had noticed the cmd window with the 'too long' message again, but thought it might get cleaned up at the end, like it had the other day.  (It was remained following the reboot.)
I ran Windows Repair with everything selected, but  :cry: with the 'Lock Repair List While Running Repairs' and 'Hide output To Cmd.exe Window' settings deselected.  I choose the automated system restart upon completion.

I replaced the exe with the test one from the other day, which I had set aside before installing v2.8.5 and re-ran the program using that beta exe.  That stopped me from being able to open the Application Data directory, as it should have.  I then ran it on the second box with the wrong results for the Application Data directory, so I am guessing that you had changed more than the .exe in the latest release.

Mark

5
Here is my finish until tomorrow.
Before and after pictures of the rights to the All User/Application Data.
Capturing the set parameters before and after the v2.8.4 run showed no differences.
I did notice a difference between the virtual instance I have been working from when compared to another one.  :undecided:
The one I have been working from is not blocked from seeing the rights applied to that directory, the other one is. 
I have posted 'OtherVirtual.jpg' to show the difference in directory rights.  This 2nd virtual has been around longer.  Also during the installation I used 'test' as the default login ID for it, where I used 'admin' for the main one I have been testing with.
I zipped up the log files for you, as well.

'til tomorrow,
Mark

6
Yikes! running Vista without the updates....sounds like a worst case scenario to me.  :wink:   The "too long" window continued to appear, and the directory structure for All Users/Application Data was not cleaned up.  A note on that:  Before running Windows Repair the system tells me that I do not have access to that directory.  After running the Windows Repair I do have access to that directory.  The default rights to that directory are being changed.

Virtual Box did run correctly following the run of v2.8.4. 

The 'mystery' cmd boxes and login screen did not appear with v.2.8.4.  Many of the cmd boxes came and went so quickly that I didn't catch any other new issues, if there were any.

7
The installation is standard, so it should not have any problems running the system account.  I have not had any such problems to this point.  I do not have it as part of any network domain, etc.  The account that I have auto logon is the account that was created during the O/S installation process and is part of the admin group, locally.  I did take the option of making it part of a home network during the O/s installation so that I could get to other computers on my LAN through shared-out directories.

I will revert to the clean snapshot and will attempt a clean run of v2.8.4, and let you know my results. 
I will also grab your v1.2.0 Envelope Printer.  :cheesy:

8
G-hot, the other user posting the message with 'Critical Bug' in the title got the same 'too long' command windows that I did.
I'm guessing that the non-English script in his other screen capture just had to do with the language he is running on his computer.

9
I made the manual registry changes for the full path of the oleaut32.dll.  Yes, suddenly that allowed the VirtualBox to launch again successfully.
If oleaut32.dll had been unregistered then I could understand the issue.  I am surprised that the search path would not look for that file in the system32 directory.  I wonder if the search path is being affected.

Prior to the manual change to the registry keys I tried registering of oleaut32.dll in a cmd.exe box/window, but saw no difference.  I even tried a reboot.  I know that in the past, at times, I have had to register dll's while being in the directory that they exist.  Maybe I didn't do that this time. 
Nothing has changed the directory structure under all users yet. 

Would it be good or bad or no-effect if I ran the Windows Repair again?  Would it now clean up the folder loop it left behind previously?
The other user/customer that complained about the slowness after running v2.8.3 - I experienced that as well. 
Have the videos you downloaded from me, or the log files I sent later added any value to your troubleshooting?  By this point I would expect you to be able to notice any deviations in the standard processes on the screen in your sleep.  Of course, you have adjusted the screen processes as well.

Have you had insight on the mw2.jpg screenshot to this point?  At a couple other points it showed up as a task on the TaskBar, which I pointed out in the first video.  I had opened up the task to show you what it was reporting.

Thanks for your continued efforts,
Mark

10
Folder infinite loop - to me it looked as if the process failed when it hit the wall, and so did not have the chance to clean up properly. 
I did note the other user on your blog running across similar issues with v2.83.  I don't recall if his box was virtual or not.

The videos will allow you to see the programs I have installed on the computer and, plus I had mentioned in one of the initial emails that I also had the latest version of flash, shockwave and java jre installed.

11
Yes, I can do the separate jpgs; whatever works best for you.  Word does such a great job in compressing documents with pictures in them that I usually try that first.  A word doc also allow for commenting.  These screenshots will just be a clearer augmentation to the videos….when you can access them.

I hope this helps. Their resolution has degraded following being placed in a Word document.  I can go through the process again if clearer pictures can be helpful after you get access to the videos. 

(For mw1.jpg)   Virtual computer, Win 7 ultimate x64, running on ESXi server v5.1.  Set for 2 processors 4GB of ram, 100GB hard drive space (VDI).  For the recorded session I set it for 1 processor, 4GB of ram, in hoping to slow the screens down.

(For mw2.jpg)   I ran a VMware snapshot prior to running it this time.  Uninterrupted Windows Repair (All in One) set for automatic restart when complete.  This is a new screen to me, as of v2.8.3
It then went to the Win7 lockout screen, even though I do not have it set to use it, even through a power scheme shutdown.

(For mw3.jpg)

(For mw4.jpg) I can’t see that I’ve seen this ‘too long’ message in prior versions of Windows Repair.

(For mw5.jpg)  Following reboot, then trying to launch Oracle VM Virtual Box

(For mw6.jpg)  Expanding the error – according to Internet sites the error means that it cannot find the virtualbox.exe

(For mw7.jpg)  Shortcut properties for Oracle Virtual Box

(For mw8.jpg)  The recursive directory structure has returned.

Of course, Oracle VirtualBox acted properly and the directory structure returned to normal following VMware snapshot restore, and reboot.


Mark

12
Ok, Here are some quick screenshots with some text in an attached document.
I have also slammed a webpage together for you to be able to watch and/or download video captures of the before, during and after effects of what I am running into.  I used the record function from Teamviewer.  It worked out very well after I figured out what I needed to show.  I really don't want to display the URL link here.  If there is a way for me to send the link to you privately, please let me know.

Note: At this time the webpage coding is not perfect and both videos, without any audio, begin playing immediately, so the first step will be to stop the videos, then watch the first, followed by the second video.  And let me know if that helps in getting this overcome.  This is the third box I've had the same thing happen on.  A quick test on a Win7 Ultimate only, without any programs installed seemed to work okay.  It's very, confusing.

Let me know, Mark
(Sunday will have me in and out of the house.  As mentioned in the attached document I did a snapshot of the original state of the box and can revert back to it within moments.)

13
3rd attempt at posting this.  I think one of the attachments had been too big.
I don't see my initial message about this listed on the blog, so I will try again.  As it was my first post on the blog, I'm sure that I blew it somehow.  I'll do my best to recreate it.
I ran into a problem after installing Windows Repair (All in One) on one of my virtual Win7 Ultimate x64 workstations.  Luckily it was only a temporary test instance that had been around for about 2 weeks.  Other than seeing a lot of different windows fly by on the I saw extra errors fly by.  I do not see it reflected in the partial log file I have attached.  I have attached a screenshot and a window shot in an .rtf file showing a new 'Interactive Services Detection' screen and a shot of the bogus file structure created.  In the original Win7 instance the Oracle VirtualBox shortcut stopped working.  Following an attempt to reinstall the VirtualBox software in repair mode.  It still did not work.  I ran the Windows repair programs a couple more times to see if I could note errors during the running of the program.  I saw enough to make me suspicious.

As a control, I then created a new instance of Windows 7 Ultimate x64 from scratch.  Next, I applied the Microsoft updates, then installed FireFox, Opera, Chrome, Safari, Flashplayer, Shockwave, Java JRE, Malwarebytes v1.75, SpywareBlaster, Spybot Search & Destroy, Defraggler, VLC player, PeerBlock and then Windows Repair (All in One).  I checked the directory structure in question prior to running v2.8.3 and then checked on the directory on and off throughout the process.  I stopped the process after the problem re-appeared. 

Let me know if I can supply any additional information concerning this problem.  I did also notice that when I initially got
prompted to update the v2.8.0 installation on that first instance I notified me of a new version being available.  It informed me about v2.8.2, but took me to v2.8.3.  I already had v2.8.2 on my main workstation, so which seemed to be solid.  I did read through the update information for v2.8.3. 

I will create a additional new Win7 Ultimate instance on my server to continue assisting someone with troubleshooting their assignments in their HTML course.  I don't know HTML, CSS or Javascript well, but am great with analyzing computer logic troubleshooting.  But, that's why all of the different browsers were installed on the Windows 7 instance.

Thanks, Mark
- - - - -

also : As an old-schooler, starting in the hex and octal machine code, CPM and DOS days, I cringed a little bit at the recent removal of the command window from some sections of the Windows Repair (All in One).  My face fell when reading:  "Updated multiple repairs to no longer display everything in the cmd.exe window" in v2.8.3.  I agree that most users will not want to see those screens, but I would like an option added for displaying the command line executions. 
It was a selling point to me when I first reviewed your products.  It displayed to me the thoroughness of your coding.  It is also a progression tool, as an addition to the System Monitor displays.  You've got to admit during a large, and multiple, disk file permissions or registry permissions the status screen can be static for a very long time.  Given the option, I would like the ability to pause some of the command screens to see exactly what it is doing or saying, especially on some of the really quick screens.

I've also noticed, since v2.8.2 that I can no longer use the scroll bar for the repair checklist or expand the "+" sections during an active repair.  But, the sections do expand when reached during the repair process.

Pages: [1]