...you don't like it, so it means I hit BINGO in your characteristics Small hint: When you don't want not2nice reactions, then don't create evil blood by yourself.
Guide for mounting non-RAW VDI (VirtualBox) as logical disk I made this guide for all, who wants to repair their broken VM (VirtualBox) installation: RAW VDI begins with the partition data like: ëR.NTFS EB 52 90 4E 54 46 53 20 20 20 20 00 02 08 00 00 Non RAW VDI can contain several partitions, it begins with some custom header like: <<< Oracle VM VirtualBox Disk Image >>> 3C 3C 3C 20 4F 72 61 63 6C 65 20 56 4D 20 56 69 72 74 75 61 6C 42 6F 78 20 44 69 73 6B 20 49 6D 61 67 65 20 3E 3E 3E 0A 00 00 00 00 00 00 00 00 So for mounting partition in Non RAW VDI, you have to provide decimal offset to the mounting tool (like ImDisk): If you can run partition info program, which will provide your accurate data, the problem is solved: Partition Table: gpt Number Start End Size File system Name Flags 1 17408B 134235135B 134217728B Microsoft reserved partition msftres 2 135266304B 85898297343B 85763031040B ntfs Basic data partition If not, still it is nice to know at least partition sizes in MBs: DISKPART> list partition Partition ### Type Size Start ------------- ---------------- -------- -------- Partition 1 Reserved 128 MB 17 KB Partition 2 Primary 465 GB 129 MB DISKPART> Then you have to search with some Hex Editor (like HxD) for the correct offset by yourself. In Hex Editor you need to switch to the decimal value, in the mounting tool select "bytes" at offset parameter. For example, when you create VDI with VirtualBox v4-1-20 for Windows 8 x64 with fixed size 40GB, it will have 3 starting offsets for partitions: 00001216512MS Reserved Partition (MBR, NTFS, 350MB) 00368217600Fake Partition, maybe Extended partition envelope (MBR, NTFS, 0MB) 00368218112Primary System Drive (MBR, NTFS, 40GB)
Not trying to act like a mod, but can you guys post this uxtheme, vdi, etc. stuff in a thread meant for that kind of thing? That stuff has nothing to do with ReFS. Anyways, I have been running 6 drives on ReFS for a couple of weeks, this mod is working great in Win 8 Pro x64. I even re-installed Win 8 after hacking my previous install into a non-functional state, and once I re-did this mod, and rebooted, the drives appeared, all data was there and it worked fine.
Will do man, but, i happily use and theming on Windows 7, a test machine has been selled yesterday, but i have another desktop one with 7 at a time.... Let me have time to prepare the machine, and i will test.... But, UHM,..... wait it is working on your 8 installation? The files has to be "patched or recoded", simply copying that files do not work, already tried.... The DWM.exe in Windows 8 is slightly different connected to dll files(so simply copy dunno work and bricks the system,this is not a big problem) i have looked at theme, and in aero,aerolite.msstyle the images of the windows frames has the transparency, but are different than it looks really on the theme without transparency(In 7 it looks the same as the window one)they do not have border, as is in 7..... So i think the theme must be modified, noone knows how..... i'm just a beginner in theming, and masters of it sometimes has difficults on some codes in 7, think in 8..... Wait, wait...... some strange, Windows 7 style builder is not compatible at all with Windows 8, where in 7 you find the image for left/right border of the Window frame(with the reg tricks in metrics you make it smaller) in 8 on the left frame there's nothing, on the right is the glyph for the close window button....... no way man!!! far more confused
Well, help me , do some more research about it, install W8 Enterprise RTM and W7 Ultimate RTM to 2 VMs, compare, analyse... I've read some of your posts at reboot.pro and you are capable to do it for sure. ) MS has stated at building Windows 8, that his FileSystem framework is universal and those FS drivers and runtime DLLs like ExtFAT, NTFS, UDF, ReFS are only something like plugin modules. Yep, it has the point and I have no problem with the things you have said, but this is actually the only my thread, what the admin-guys approved. So it is all here. I've asked to change thread name to something like "W8 Mods", but... ...well nothing has happened. Just thinking what to do with it, it is quite unstable, since explorer b7989 doesn't use explorerframe.dll. So it requires some work and polishing to do yet. Key aspect for me is, that I'll not use it anyway (because it is both non-sence to do so and it is also security hole and it has another consequences, like breaking other things, what currently work.), so probably I'll just post video on YouTube prooving, that it can be done for fun, publish the files at WinUnleaked after one or two fixes what are really needed and then scrap it. Also those poisoned comments from the thread, what is currently dealing with this issue prooved, that there is no need to publish anything for those guys. Try the combination of TrueLaunchBar and SkipMetroSuite instead, if you want my oppinion, it is much more clever solution with keeping the essential EXEs of OS unmodified (it doesn't help placing it in different directory and keeping b9200 exe in system32). Well, you need the unmodified EXEs for using Windows Update, this is also the reason for which Windows isn't cracked, but the guys rather search the way to activate it. So it can stop work after any Windows Update, when MS will change anything from SHLWAPI.DLL, OLE32.DLL, NTDLL.DLL, ADVAPI32.DLL, etc. So generally it is completely wrong approach, which can't be used in real work. BTW: I love the new feature for starting apps by pressing <WinKey> and start typing, it is SO addictive.
Metro Minimal Edition ) I am SO proud for my current Metro screen, hehe: (Testing VM with few apps installed) All Metro apps are disabled by turning-off LUA, association to them removed, unpinned... ...in this configuration it even looks nice ) (I wouldn't believe, that I will say it about Metro.)
As you've probably read, I did some research on the topic. Unfortunetaly I believe it's just not as simpel as adding a module. I am sure that at a minimum you would need to patch (severely) at least more than 2 files. Moreover, you would also probably need to patch other important libraries like ulib.dll and ifsutil.dll, and also likely a bunch more including the core of Windows. Let's just say I left the idea But, I may be wrong, which is why I got curious about your hinting comment referenced in my previous post. And please do not consider my opinion as a fact. It's just an opinion, and I don't want to cause others to stop testing and researching on ReFS to Win7.
There are two different things: 1. Loading SYS driver (and this is working fine). 2. Formatting by using DLLs (and this is not working yet). I'll create 2VMs (Win8, Win7), at Win8 I'll import ReFS, create 2nd drive and format it in ReFS, at Win7 I'll only load ReFS driver and then connect already formatted ReFS volume. Maybe I'll be surprised.
hi, i found this thread as i was trying to install refs on windows 8 rtm. However i noticed that after following your procedure here and you format a drive in ReFS, you can't use long filenames. Does this mean that the refs package isn't enough to gain full use of refs?
Hello, there are no problems at all with long filenames at ReFS volumes, so the issue is connected to your configuration only. The driver enables all ReFS features. Apply for help in this thread, if you want to solve it.
Thanks for you help and quick answer. I really would like to solve it if it's possible , but I don't know where to start though. Here's (i49.tinypic.com/wjhzj9.jpg) a screenshot of the issue i'm experiencing when trying to move a file with a really long filename into a folder of similar filename. I couldn't wrap it in an IMG tag since I'm new at this forum so please bear with the copy paste I'm using Windows 8 Pro x64 (6.2, Build 9200) I'd be happy to provide you with any info you might need.
From that picture I can see, that it is working, because you already have "test-long-filename" folder stored and the text file "123456789-....txt" in it. However it looks, that the complete destination patch J:\test-long-filename\1234567890-....\1234567890-....txt you are trying to create exceeds 255 chars limit to the absolute path...