diff --git a/src/runtime/mapvfs.config b/src/runtime/mapvfs.config
index e0532fa4..be08c717 100644
--- a/src/runtime/mapvfs.config
+++ b/src/runtime/mapvfs.config
@@ -32,7 +32,7 @@ tclkit-win64-dyn.exe {punk8win.vfs punksys kit}
 #TCL9
 #tclsh902z.exe {project.vfs project zip}
 #2
-#tclsh90b2 {punk9win.vfs punk90b2 zip}
+#tclsh90b2 {punk9wintk90b2.vfs punk90b2 zip}
 #3
 #tclsh90b4_piperepl.exe {punk9wintk90b2.vfs punk90b4 zip}
 #tclsh901t.exe        {punk92in.vfs punk901t zip}
@@ -53,7 +53,7 @@ tclsfe-x64.exe {punk9wintk903.vfs punk91 zip}
 
 #----------------------------------------------
 #experiment - what happens when we run against a 'wish' runtime? Will we have stdin stdout problems?
-#tksfe-twapi-x64.exe {punk9win.vfs punkwish91 zip}
+#tksfe-twapi-x64.exe {punk9wintk903.vfs punkwish91 zip}
 # result so far: the kit builds - but the tk console doesn't display.
 # we can run tk apps e.g punkwish91 lib:tkhello
 # - todo - consider if we can first get the built in tk console showing for initial exploration, although it is unsuitable for a punk console as it doesn't handle any ansi.
diff --git a/src/vfs/punk9wintk90b2.vfs/main.tcl#..+_config+punk_main.tcl#@punk%3a%3aboot,merge_over#.fauxlink b/src/vfs/punk9wintk90b2.vfs/main.tcl#..+_config+punk_main.tcl#@punk%3a%3aboot,merge_over#.fauxlink
new file mode 100644
index 00000000..e69de29b