Windows 7

[fgagnon]

I ran the debug version and had no problem.
Nothing to report except the usual startup assertions to which I clicked "ignore".
But I emailed you the debug log anyway, in case there may be anything telling in it.

PS - Later, while noodling with kenny, I noted many multi-ignorable assertions whenever I move up to a folder parent -- whether by backspace or by pane headingbar or by tree. (prob of no consequence)

BUT this may be relevant to the issue - when I click on the Drive button (or do Alt-F1) I get an assertion corresponding to the following snippet from the DBG log:
______________________________________________________________________________

• 3132: Frame_110460 handling command 32940
  3132: *** TID=46c, Generating folder instance '::{20D04FE0-3AEA-1069-A2D8-08002B30309D}'
  3132: Filesystem path =
  3132: Shell attributes: (0x30000000) FILESYSANCESTOR |
  3132: DESCRIPTIONID: 1(ROOT_REGITEM) : {20D04FE0-3AEA-1069-A2D8-08002B30309D}
  3132: Assigned folder type: FITYPE_NORMAL [forced]
  3132: Folder CLSID: {20D04FE0-3AEA-1069-A2D8-08002B30309D}
  3132: Enumerated 5 objects in the folder, code=1
  3132: drive C:\ disabled through admin policy
  3132: drive D:\ disabled through admin policy
  3132: drive E:\ disabled through admin policy
  3132: drive F:\ disabled through admin policy
  3132: drive G:\ disabled through admin policy
  3132: D:\umeca74\My Documents\cpp\newkenny\MAINFRM.cpp(4062) : Assertion failed: len && len < 260
  3132: Thread 46c pump: unrecognized message 49214 ignored
  3132: Thread 46c pump: unrecognized message 49214 ignored
  3132: Thread 46c pump: unrecognized message 49214 ignored
  3132: Thread 46c pump: unrecognized message 49214 ignored
  3132: Thread 46c pump: unrecognized message 49214 ignored
  3132: Thread 46c pump: unrecognized message 49214 ignored
  3132: SPY(00000003): [9617243] Raw Event 0 = UPDATEITEM
  ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Users\fmg\ntuser.dat.LOG1 <NULL>
  3132: SPY(00000003): [9617243] Raw Event 1 = UPDATEITEM
  ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Users\fmg\NTUSER.DAT <NULL>
  3132: SPY(00000003): [9617243] Processing Disc Event = UPDATEITEM
  ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Users\fmg\ntuser.dat.LOG1 <NULL>
  3132:   VIEW_18042e: processing update notification for ntuser.dat.LOG1
  3132: SPY(00000003): [9617758] Processing Disc Event = UPDATEITEM
  ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Users\fmg\NTUSER.DAT <NULL>
  3132:   VIEW_18042e: processing update notification for NTUSER.DAT
  3132: SPY(00000003): [9627367] Raw Event 2 = UPDATEITEM
  ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Users\fmg\ntuser.dat.LOG1 <NULL>
  3132: SPY(00000003): [9627367] Raw Event 3 = UPDATEITEM
  ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Users\fmg\NTUSER.DAT <NULL>
  3132: SPY(00000003): [9627367] Processing Disc Event = UPDATEITEM
  ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Users\fmg\ntuser.dat.LOG1 <NULL>
  3132:   VIEW_18042e: processing update notification for ntuser.dat.LOG1
  3132: SPY(00000003): [9627898] Processing Disc Event = UPDATEITEM
  ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Users\fmg\NTUSER.DAT <NULL>
  3132:   VIEW_18042e: processing update notification for NTUSER.DAT

[nikos]

these lines indicate the problem: drive C:\ disabled through admin policy
somehow windows 7 won't name drives as c:\ etc under my computer
when i get hold of windows 7 i'll double check it, thanks

[johngalt]

Been a while since I have been in here....

I can state that the drive bar stopped functioning somewhere between build 7000 (The official build released) and 7048, as I moved from 7000 to 7048.

I continued to stay gone in 7057, 7068, and now 7077.

I snagged the Dev build your posted a couple of posts back, Nikos, but since I know the KB shortcuts, and since this is the only problem manifesting, is there any reason for me to even install the Dev build at all now that you know what part of the problem is?

[nikos]

it's a very silly problem, which i reported here
http://groups.google.com/group/microsof ... cbc7408c2a
not sure if anybody's listening or planning to fix it though!

[fgagnon]

try one of these:
http://social.technet.microsoft.com/For ... rf/threads
http://social.technet.microsoft.com/For ... at/threads

[nikos]

nice, how did you find these?

[fgagnon]

my apologies for not replying earlier, but I somehow missed seeing your question.
@ ... how did you find these? -
IIRC, the link to the top level win7 IT Pro forums was included somewhere in the February public beta release correspondence and I bookmarked it.  
When I saw that you expressed doubt that anybody was listening at MS, I just picked a couple of likely sub-forums for you to try from the list on the top level forum.  

Moving on ...
Very early today, the w7 Release Candidate was leaked on torrent sites, and some additional information about w7 (a virtual XP mode) was also OK'd for release in this blog entry on Paul Thurrott's SuperSite for Windows.

[fgagnon]

A curious observation of drive bar behavior under Windows7 RC build 7100:
In x2 the drive bar continues empty, and Alt+F1 does not display the menu of drives, ...
BUT - in the old 2xExplorer, both the drive bar and Alt+F1 work!

[tested on both 32-bit and 64-bit versions of win7 RC build 7100]

[nikos]

another guy said that in windows 7 when you click on a [-] square on the tree x2 crashes, true or false?

[fgagnon]

another guy said that in windows 7 when you click on a [-] square on the tree x2 crashes, true or false?

As I indicated in the email response to the 1st guy: I have never seen this running x2 under any build of win7 beta.  

Further, I specifically checked for the issue yesterday with the win7 RC build 7100 and could not reproduce it.    
I tried with 64-bit x2 and 32-bit x2 on 64-bit win7.
I tried with 32-bit x2 on 32-bit win7.  
I tied with tree sync'ed and without in all cases.
[My 64-bit win7 is a "clean install" and the only OS on my laptop currently]
[My 32-bit win7 is a "clean install" to a dual boot partition on my desktop computer]

Note:
For win7 anomalies, we should be careful about assigning strange behavior bugs to the app vs. w7 itself.  Besides being pre-release, there are issues with upgrade installation performance vs "clean install" performance.  Microsoft recommends a clean install for each build. Upgrade installations are easier for the user (settings and apps are retained intact) but due to forked builds they can fall victim to the odd bug. Bottom line: If an issue cannot be reproduced with a "clean install" it may not be a real issue.

So: win7 users, when reporting bugs under win7 please indicate not only the win7 build, but also whether your win7 installation is an upgrade from a previous build, or a clean install.

[fgagnon]

The x2 installer does not (yet) pin shortcuts to the win7 taskbar.

Until the installer is updated, the workaround is to r-click the icon you want to place on the taskbar and select "Pin to taskbar" from the context menu.
_______________________________________________________________________

nikos,

MS has re-engineered the taskbar and merged it with the Quick Launch bar, and renamed the folder which contains the items.

path to pinned items in win7 taskbar -
C:\Users\<username>\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar

(compare to) path to pinned items in XP Quick Launch end of taskbar -  
C:\Documents and Settings\<username>\Application Data\Microsoft\Internet Explorer\Quick Launch

[cerulean47]

I have a clean/fresh (not upgrade) install of Win7 build 7100 x64.  I can confirm that the Drive Bar remains empty in version 1.7.2.4 [Unicode] x64 of xplorer2 professional edition.

Glad to see it's a known issue and I'm not crazy.

[nikos]

can you show me a picture of the taskbar problem?

[cerulean47]

Here you go
http://drop.io/gyaiga1

[wasker]

The x2 installer does not (yet) pin shortcuts to the win7 taskbar.

I don't think this would ever be possible:

7. Newly installed programs

“Customer in control” is so strong a mantra for Windows 7 we don’t even allow programs to pin themselves to the taskbar when they are installed. This is a task expressly reserved for the customer. We’ve gotten some requests to make this goal a bit easier so now when a program is installed, it is automatically and temporarily surfaced at the bottom of the Start Menu. The customer can easily discover this new addition, launch it directly and optionally drag it to the taskbar for convenient access in the future.